After stopping the roll-out of Windows Update on October 10, 2018 over the weekend, Microsoft has once again delivered the upgrade upgrade feature to users.
The immediate re-release was restricted to Windows Insider participants, Microsoft's opt-in beta test program, John Cable, Director of Program Management in the Windows Service and Delivery Group, wrote in a post to a corporate blog. "We will carefully study the results, feedback and diagnostic data from our Insiders, before we take further steps towards re-publishing more widely."
Cable did not reach a date when Microsoft would fully restore the distribution. "Once we have confirmed that there is no further influence, we will move towards an official reload of the update to Windows October 1
This form of incremental delivery – where code is given first to a few, then to a larger number of users – is common among software developers, whether it is great for launching a major update or, as in this case, after a debacle and forced restart. In the latter situations, the few-then-more-so-many approach is practically mandatory to restore customer confidence.
In order to spur this trust, Cable claimed that Microsoft had discovered what led users to lose files after upgrading to 1809 the numerical label in the company's yummy format. He assured users that Microsoft has everything under control.
"We have fully investigated all data loss reports, identified and solved all known issues in the update, and conducted internal validation," said Cable.
He also encouraged users if the files had been deleted to contact Microsoft support by phone or visit a corporate store for assistance. Unlike reports that meant that the support technologies were equipped with special tools to recover lost files, Kabel informed customers that the deletions could be permanent.
"We can not guarantee the outcome of file recovery," he said. 19659009] Cable also suggests that the error was reported before the release of October 2 by the Insider Program participants. According to several different withdrawals, the error failed through the crack because too few had "quarried" the error – although more testers had logged data loss in the Insiders-only Feedback Hub.
The cable's comments about Microsoft's changes in Hubet are synchronized precisely with claims from outside of insider errors. "To help us better identify problems like this … we have added an opportunity that users should also provide an indication of the impact and severity of submission of user-initiated feedback," he said. "We expect this to allow us to better monitor the most efficient issues even when the feedback volume is low."
Many people took Microsoft to the forest and based the company to look at the problem. "By allowing such a buggy upgrade in nature, Microsoft has really given customers down. And a quick glance in the Insider Feedback Hub shows this to be a reported issue before," said Rod Trent, general manager of myITforum. com and a reputable expert on Microsoft's System Center Management System.
"It's time to return to the drawing board," Trent continued. "Microsoft's updating mechanisms are broken."
Cable is not surprising, not so fierce. "We are committed to learning from this experience and improving our processes and alert systems to ensure that our customers have a positive experience with our update process, "he said as he wrapped up his post.