Monday, October 8th 2018
Microsoft Pulls Windows 10 October 2018 Update
Over the weekend Microsoft has stopped delivery of their latest Windows 10 October 2018 Update (Build 1809). Many user reported serious issues with the new version, with the biggest problem being the deletion of files in "My Documents". Some users have reportedly lost hundreds of Gigabytes of data, containing decades of their life's work. Another scary experience was that in an enterprise environment, where "My Documents" was mounted from a server, with shared subfolders, the update erased all the documents on the network server. Let's hope the affected people have backups. Reportedly copies on OneDrive aren't affected.
Other users are having issues with drivers not installing properly, or the system crashing during a driver install. Another Microsoft bulletin goes into detail that using an Intel Audio Device with the new update "may result in excessive processor demand and reduced battery lifemay result in excessive processor demand and reduced battery life".
Microsoft has issued the following statement:
"We have paused the rollout of the Windows 10 October 2018 Update (version 1809)* for all users as we investigate isolated reports of users missing some files after updating.
If you have manually checked for updates and believe you have an issue with missing files after an update, please minimize your use of the affected device and contact us directly at +1-800-MICROSOFT, or find a local number in your area https://support.microsoft.com/en-us/help/4051701/global-customer-service-phone-numbers. Alternatively use a different device to contact us at https://support.microsoft.com/en-us/contactus/ (link will vary according to country of origin).
If you have manually downloaded the Windows 10 October 2018 Update installation media, please don't install it and wait until new media is available.
We will provide an update when we resume rolling out the Windows 10 October 2018 Update to customers."
Update 08:33 UTC:
Apparently Microsoft support is able to help with file recovery, and urges you to contact them via phone.
Microsoft's 1st level support will just tell you to run System Restore which relies on a restore point being created prior to the upgrade. Creating a restore point before upgrade is the default behavior, so it looks like if you have a restore point, you're good to go.
If that doesn't work out, then 2nd level support will request to remotely login to your system, where they can run some sort of file recovery tool (similar to GetDataBack NTFS). The underlying reason why this can work is that when a file is deleted, only its entry in the filesystem directory is deleted, not the actual file data itself. So, as long as the data blocks haven't been overwritten by some new data, it's possible to recover the files. That's exactly the reason why Microsoft recommends to stop using affected systems.
Sources:
Microsoft, User who lost 220 GB, Intel Audio issue with Update, Reddit user on MS Recovery Procedure
Other users are having issues with drivers not installing properly, or the system crashing during a driver install. Another Microsoft bulletin goes into detail that using an Intel Audio Device with the new update "may result in excessive processor demand and reduced battery lifemay result in excessive processor demand and reduced battery life".
"We have paused the rollout of the Windows 10 October 2018 Update (version 1809)* for all users as we investigate isolated reports of users missing some files after updating.
If you have manually checked for updates and believe you have an issue with missing files after an update, please minimize your use of the affected device and contact us directly at +1-800-MICROSOFT, or find a local number in your area https://support.microsoft.com/en-us/help/4051701/global-customer-service-phone-numbers. Alternatively use a different device to contact us at https://support.microsoft.com/en-us/contactus/ (link will vary according to country of origin).
If you have manually downloaded the Windows 10 October 2018 Update installation media, please don't install it and wait until new media is available.
We will provide an update when we resume rolling out the Windows 10 October 2018 Update to customers."
Update 08:33 UTC:
Apparently Microsoft support is able to help with file recovery, and urges you to contact them via phone.
Microsoft's 1st level support will just tell you to run System Restore which relies on a restore point being created prior to the upgrade. Creating a restore point before upgrade is the default behavior, so it looks like if you have a restore point, you're good to go.
If that doesn't work out, then 2nd level support will request to remotely login to your system, where they can run some sort of file recovery tool (similar to GetDataBack NTFS). The underlying reason why this can work is that when a file is deleted, only its entry in the filesystem directory is deleted, not the actual file data itself. So, as long as the data blocks haven't been overwritten by some new data, it's possible to recover the files. That's exactly the reason why Microsoft recommends to stop using affected systems.
97 Comments on Microsoft Pulls Windows 10 October 2018 Update
Surely MS will realize too that not a single of these big updates has been flawless yet and that the users don't give a rat's behind about the marketing surrounding each update. MS is acting like we want features they push into the OS when in fact the vast majority just wants it to work. They want to be a poor man's Apple... well they're doing quite well in that regard - emphasis on poor.
I'm at least glad I put the maximum delay on each update, my 10 experience has been mostly hassle free as a result.
I don't really remember... did service packs (XP, Vista, 7) usually have these problems?
Until some meaningful alternative comes along it is best to set aside the tissues and screaming pillows. It is ok to voice level-headed reasonable comments with a sense of perspective.
The fact is that Windows updates have caused problems for users in so many different ways, not least crashing systems and installing updates at the most inconvenient of times.
I may do this kind of thing for a living (fixing PCs) but the vast majority of PC users simply want their machines to do the things they want to do and not mess around with endlessly fixing Windows Updates problems.
If temporarily stopping Windows Updates fixes my brother's problem, bearing in mind his appalling Internet speed, then so be it.
@Splinterdog sounds like he may have to rely on using the Media Creation Tool or something similar every time a big update like this happens...
Further, most Windows updates happen in the background with no prior warning. I've yet to see a notice from Windows that says 'Back up your data before this update!', but I may be wrong.
Pulling up the ladder and saying I'm alright Jack, isn't helpful in the least.
To me, that was the last straw. So, sorry if I have a sour attitude but, remember that it's completely due to upgrades having exploded in my face at the most inconvenient times.
So, tl;dr: My problem isn't with Windows, it's with how they upgrade it.
What I figure they're doing is this...
1. Move all data that's in C:\Users to C:\Windows.old\Users.
2. Do the upgrade.
3. Move the data back from C:\Windows.old\Users back to C:\Users and update the files in the process.
This is absolutely insane!!! This kind of process, especially when dealing with a whole lot of files, can lead to things going wrong if you don't do a thorough check to see if all data files are there after you do the file move.
What the really should be doing is...
1. Find the files in C:\Users that they need to change, make copies of them in the same place where they are but name them with a .winupg at the end of the file name.
2. Do the upgrade.
3. If the upgrade is successful, scan the directory tree for all files with a .winupg at the end of it and delete them. If the upgrade process doesn't work, find all the files with .winupg at the of it, find the version of the file that doesn't have a .winupg at the end, delete it, and then chop the .winupg off of it and there you go, all data is restored.
This process here is a lot less prone to things going wrong compared to the mass wholesale copy/move process that I think Microsoft is doing.
In fact, due to the amount of times WU has screwed his PC, he keeps the Rufus pendrive handy in case of further WU incidents, which is a pretty sorry state of affairs. Barring the fact that his Windows updates have now been disabled.
I do agree the methods Microsoft is using and frequency of these updates are unnecessary. I would rather see these updates coming incrementally with the user fully in control of when. Right now they do let you pause for 35 days or auto defer for a long time, but I still think auto updates should be optional and the timing of updates optional by default. The in-place upgrade-style updates are cumbersome - it is stubborn policy getting in the way of friendly consideration.
Quit fanboying.The old build remains fully supported for almost a year or more following release of a build. Please familiarize yourself with 10s update model. This was a "feature upgrade"Not a bad policy. Basically Current Branch For Business does this.