Microsoft deems Windows 10 October 2018 Update safe for deployment
Months after releasing the first iteration of the botched October 2018 update to Windows 10, Microsoft has designated version 1809 safe enough to release to businesses through its servicing channel.
This major upgrade to the firm's flagship operating system, Windows 10 version 1809, was initially made public in early October last year. But it was recalled and re-released several times over the following months due to a swathe of critical errors.
These include reports of incompatibility with drives, reduced battery life, and a severe file-deletion bug. Further glitches were detected after Microsoft pulled the release and made it available to just Windows Insiders, including a second file-deletion bug that affected compressed ZIP folders.
"Based on the data and the feedback we've received from consumers, OEMs, ISVs, partners, and commercial customers, Windows 10, version 1809 has transitioned to broad deployment," the company said.
"With this, the Windows 10 release information page will now reflect Semi-Annual Channel (SAC) for version 1809. We will continue to communicate for future releases the transition from targeted to broad deployment status."
Although version 1809 was made publicly available again in November, users could only upgrade to the latest version of Windows 10 by manually checking for updates, or via external media.
The company said at the time it would learn from its mistakes in the way it rushed the April 2018 update, and take a phased approach to releasing the October upgrade. And only now has version 1809 been finally declared safe enough for broad deployment across its consumer and business user base.
This decision has incidentally been made just weeks before Microsoft is set to release its next massive upgrade, known as the April 2019 Update, or version 1903.
In the wake of its recent string of upgrade disasters, Microsoft has also begun early testing elements due to be released in a major 2020 upgrade. This was despite testing for the October 2019 update having yet to be commenced at the time of writing.