This last Tuesday, Microsoft released a major update to all Windows 10 versions dubbed ‘May 8, 2018—KB4103727 (OS Build 16299.431)’.
Now anyone with even a modicum of experience with Windows client operating systems knows that installing these updates comes with a risk, especially on older computers. Since these types of updates are installed without the user being able to cancel them (the exception here is Windows 10 Professional and Enterprise editions support advanced policy settings), users should exercise caution when blindly restarting and updating their computers,
I’ve had no issues with recent updates, however this update crashed one of my HP Stream laptops running Windows 10 Home (x64).This was a fully patches and functional laptop. That is until I clicked ‘Update and Restart’. Upon restart, the laptop would no longer boot; it simply hung at the spinning orbs.
Now, being intimately familiar with Windows 10, with decades in enterprise Microsoft deployments, and holding an MCSE+ credential, it still took me an enormously long time to be able to back out this update and restore the machine to a previous state, and the steps required to do so could easily render a computer completely useless with data loss.
Having worked extensively with the product teams at Microsoft, I know the level of control and telemetry they put into each update they release. But with millions and millions of computers of varying power, hardware, software, and drivers, they cannot isolate every potential issue.
There were already similar issues being reported across the internet, however Microsoft allegedly stated they were unaware of an install failures.
Let’s hope their telemetry shows the reality and they can isolate the cause and release an update. Otherwise, on Home editions like my Stream, all we can do is defer updates several days out.
It should be noted that this update installed on my Lenovo T420 (Windows Enterprise x64), and the equivalent version on my Windows 2016 Datacenter Server without issues
Caveat emptor. Always make sure you have a verified backup handy and at the very least, create a valid restore point prior to install.