Over the weekend, Microsoft was forced to halt the roll out of the Windows 10 October 2018 Update. Launched last week, the updated landed with several problems. However, it was a bug in the manual update that deleted user files that prompted Microsoft to act.
Reports last week pointed to an issue with the manual update for Windows 10 October 2018 Update. Specifically, the update was deleting personal user files such as images and document.
While the company acted swiftly to save anymore users from the issues of the October 2018 Update, what about those already affected? Well, Microsoft says it is ready to help affected early adopters.
Windows Insider Program head Dona Sarkar took to Twitter to say affected users should contact Microsoft directly. When contact is made, the company will help them recover their files.
“If you’ve run into the ‘missing files after update’ issue for 1809/October 2018 Fall update, please call our support line. They have the tools to get you back to a good state.” More information on how to contact Microsoft can be found on Microsoft’s support page.
#WindowsInsiders If you've run into the "missing files after update" issue for 1809/October 2018 Fall update, please call our support line. They have the tools to get you back to a good state. This build is no longer available to download manually: //t.co/Ce9WVILknp pic.twitter.com/fvisQi1c8g
— Dona Sarkar (@donasarkar) October 6, 2018
It is worth remembering the issue was only found when downloading the Windows 10 October 2018 Update manually. The October 2018 Update confused interactions with the Windows.old folder. This is where an update sometimes moves a previous installation backup.
Microsoft has not said when it will resume the roll out of the update. We guess Patch Tuesday tomorrow may have some answers and updates will resume sometime this month. That’s speculation through as the problem may be deep enough to warrant more time to fix.
Last week, we also reported on a known issue with the Task Manager in the Windows 10 October 2018 Update. For that issues, Microsoft said it already know the Task Manager was reporting incorrect information to the CPU. In deed the company said it was a know issue from Windows 10 preview build 17763.