In an official Blog Post, Microsoft has revealed the reasons behind the issue of “Data loss” that forced them to pull Windows 10 October 2018 update. Microsoft also claims that very few 1809 installs are affected by this Data loss issue.
At just two days into the rollout when we paused, the number of customers taking the October 2018 Update was limited. While the reports of actual data loss are few (one one-hundredth of one percent of version 1809 installs), any data loss is serious.
Microsoft has also investigated and fixed all known issues in the update. You can read more here.
We have fully investigated all reports of data loss, identified and fixed all known issues in the update, and conducted internal validation. Also, Microsoft Support and our retail stores customer service personnel are available at no charge to help customers. More details are available below.
Yesterday, Microsoft released Build 17763.17 with Data loss and other fixes to insiders in Slow and Release Preview Rings.
We have released the Windows 10 October 2018 Update Build 17763.17 (KB4467228) to the Slow and Release Preview rings. For more information on this update – see this blog post from John Cable: https://t.co/rC8AYi87Gd
— Windows Insider Program (@windowsinsider) October 9, 2018
They have also released Build 17763.55 with these fixes to those already on the now pulled official Version 1809 update.
Insiders who received 17763.55 have same fixes from 17763.17. 17763.17 is for people coming from previous version of Win10 updating to Oct. 2018 Update. If you’ve already been impacted by the issues these updates address, please call MSFT Support as directed in John’s blog post.
— Windows Insider Program (@windowsinsider) October 9, 2018
Microsoft has also made some changes in the way feedback is provided in Feedback hub to capture the real impact of issues even when the feedback volume is low.
To help us better detect issues like this, today we have enabled a new feature in the Windows Insider Feedback Hub. We have added an ability for users to also provide an indication of impact and severity when filing User Initiated Feedback. We expect this will allow us to better monitor the most impactful issues even when feedback volume is low.
