Windows 10 October 2018 Update rollout now paused  

FireSky said:

Thanks man. Worked like a charm.

Chris77 said:

Operating System: Win 10 pro
Ver: 1803
Installed: 2018-10-04
OS Build: 17134.320

Took about 8 hours at 2mb/s download, but not 1809-?

1809 has been pulled.

Just catching up with this latest fiasco... seems each MS "roll-out" ends up as "roll-eyes"... not funny for many, I know, but just trying to find some humour in it...

Was this ever a known issue in Insiders builds?...Albeit it only affects a few, it should still have been addressed, surely... losing data is a mission critical bug.

I can't recall any of this kind of stuff prior to Win 10's rolling releases... it's a shame, really, as theoretically it was an excellent idea (vis-a-vis Debian.)

RingTailCoon said:

Not even waiting what the CU brings this week? Isn't that kinda rushed?

I don't think a cumulative update is the solution, RingTail. The reason I say this is that not everyone actually got the update to 1809, so a mere CU won't update them. For instance, I've seen numerous reports from those who have several machines that they stopped the updates once the "bug" was discovered.

Right now, the way things look to me, we have:

1. Joe Public started updating his five machines, but before he got through with all of them, the **** hit the fan and he stopped. Now he has "three" updated machines and "two" that are not.

2. Jane Public, being the cautious person she is, waited to see if anyone had problems. When it hit the fan, she blocked the update on her computer(s).

3. And then you have the numerous reports of, I didn't lose any files, but . . . this, that, or the other, is happening on my machine(s).

4. Last, but not least, you have the vast majority who didn't lose any files. Further, for them, 1809 seems to be working fine so they've chosen to "sit tight" and wait for the next step by Microsoft.

So, with all these different scenarios, logic tells me there will have to be a new "Build" of 1809 released at the very least. That said, there are many who already have 1809 working properly and have chosen to wait, so . . .

The end question is . . . Will Microsoft be able to send a new Build out to those who don't have 1809 installed, yet only send out a cumulative update to those who do have 1809 installed. Or . . . Is it possible that Microsoft will send out a Build that can discern whether 1809 is installed, remove it if it is, and then proceed with the latest and greatest . . .

Mooly said:

I used to use file history and found it generally OK although it hadn't a clue what happened if you made a disk image and then restored that image with the master index losing all its data for any time period that went missing due to the restore. Browsing the files manually was always an option although a simple copy and paste back to their location throws up problems in file permissions if you subsequently want to alter a restored file. Not a big problem but an annoyance.

My main reason for ditching it was the continuous warnings of it being removed from future W10 builds... so I looked elsewhere and found that AOMEI backup program offers something similar to file history. And the reason I ditched W10 backup and restore... because of similar warnings about it being removed. So AOMEI covered all bases and in practice works better than the Windows versions it replaces.

I'm still using File History (in 1803) and it works fine.
I'm never likely to image the disk it's on, because THAT disk is my Data disk so file copies are as good as an image.

For the system disk I DO image it, as do many people here, with Macrium Reflect (Free)

Oh, and as well as File History, for my data, I manually run FreeFileSync https://freefilesync.org/ whenever I've done any significant work - I have 2 lots of synch set up - 1 to an internal drive (NOT my Data Drive!) and 1 to an External drive.

Ditto to a Cumilative Update not being a solution. Patching your install after the files are gone isn't going to do it. I'm with @Wynona, I think a new ISO is going to be released at some point. Once they actually figure out what went wrong for some, and make the necessary changes to the install media.