After 45 days in the unpaid beta testing phase, Microsoft surprised most of the patching world yesterday by declaring that Windows 10 April 2018 Update is ready for deployment in the enterprise. By doing so, Microsoft simultaneously raised the ire of almost everyone in the patching industry, demonstrated how out-of-touch its metrics have become, and completely destroyed the underpinnings of “Current Branch for Business.”
Win10 version 1803 entered the unpaid beta testing phase (officially known as the “Semi-Annual Channel (Targeted) branch” or, previously, “Current Branch”) on April 30. Yesterday, Microsoft declared that Win10 1803 is ready for business deployment:
"Based on the update quality and reliability we are seeing through our AI approach, we are now expanding the release broadly to make the April 2018 Update (version 1803) fully available for all compatible devices running Windows 10 worldwide. Full availability is the final phase of our rollout process. You don’t have to do anything to get the update; it will rollout automatically to you through Windows Update."
The terminology has changed at least three times since Win10’s initial release, but to use the terms most familiar to patching people, Microsoft has reduced the full-on testing time – the interval between “Current Branch” and “Current Branch for Business” – significantly:
How long has it taken Microsoft to bestow the “ready for business” imprimatur?
- Win10 1511 (Nov. 10, 2015 to Apr. 8, 2016) = 150 days
- Win10 1607 (Aug. 2, 2016 to Nov. 29, 2016) = 119 days
- Win10 1703 (Apr. 11, 2017 to July 11, 2017) = 91 days
- Win10 1709 (Oct. 17, 2017 to Jan. 18, 2018) = 93 days
- Win10 1803 (Apr. 30, 2018 to June 14, 2018) = 45 days
That A.I. is gooooood, eh?Mind you, version 1803 is the one that shipped with multiple major flaws, including
- The inability to run on many Toshiba and Intel solid state drives, which was fixed May 23, or 22 days ago;
- Conflicts with Avast antivirus (which Microsoft hints was Avast’s fault, while Avast points the accusatory finger back at MS), also apparently fixed on May 23;
- A conflict with Intuit QuickBooks that was solved by a hotfix on June 5 and rolled into the cumulative update on June 12, or three days ago;
- The SMBv1-related problem ““An invalid argument was supplied,” which was fixed on… oh, wait a minute, Microsoft says that one’s still a problem and it will be fixed “in June;”
- The new partition bug, where installing 1803 creates new, bogus partitions that may re-assign drive letters. That one hasn’t been solved, and it isn’t clear whether it will ever be retroactively solved for those who were taken in by an earlier buggy patch.
Of course, Microsoft’s “A.I. approach” has made the world a better place, and folks who have to patch are now instructed to eat dirt. At this point, it looks like 1803 is going to be pushed onto most machines, very rapidly. Microsoft claims that 1803 is already running on 250 million machines, on a user base “approaching 700 million monthly active devices.”