Windows Update Process Suffers Another Black Eye
Over the weekend, Microsoft pulled the latest version of Windows 10 and other version 1809 operating systems, just four days after releasing them.
"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," Microsoft said in a statement on its support site. As of Monday afternoon, Microsoft had not released a new update.
Affected platforms included Windows 10, version 1809; Windows Server, version 1809; Windows IoT Core, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10 IoT Enterprise LTSC 2019; and Windows Server 2019.
Microsoft was advising customers who lost files to contact the company immediately. Meanwhile, the company warned anyone who had manually downloaded the installation media not to install it.
Despite the emphasis on the phrase "isolated reports," the decision to initiate such a major disruption by interrupting downloads indicates Microsoft has serious concerns about the code that's been released. There is always a warning to back up files before initiating an update, but a file deletion issue ranks among the most serious types of problems that an upgrade can introduce.
Pulling back the update is another black eye on the major overhaul of the update process for the Windows 10 era, which has been marked by a generally popular operating system but frustration over lack of control over updates and concerns about the speed of release cycles and testing quality issues.
The previous Windows 10 update, April 2018, ran into delays and post-release problems, and the patch release process is also taking serious criticism from patching experts, including Microsoft Most Valuable Professional (MVP) and moderator of the Patchmanagement.org listserve Susan Bradley.
Nobody is saying that quality control of a Windows operating system releases is easy. Microsoft currently claims a 700-million-user installed base for the operating system, and that OS runs on hundreds of hardware configurations and with thousands of other software applications and cloud services.
This latest incident should suggest to Microsoft that it's time to swing the pendulum back a little from the pressures in technology to "move fast and break things" toward being more deliberate, cautious and exhaustive in the pre-release process for Windows.
Posted by Scott Bekker on October 08, 2018 at 11:12 AM