In addition to fixing things on its end, Microsoft has outlined some workarounds for specific scenarios in which systems administrators have encountered the issue (via Neowin).
According to Microsoft (opens in new tab), a "publishing issue" is what caused machines to encounter boot errors with the release of the latest Windows 10 Patch Tuesday updates on October 10. Fortunately, the issue was only affected WSUS-managed devices on Windows 10 version 1703, version 1607, and Windows Server 2016, so home and consumer devices remained unaffected. Microsoft is mum on specific details of the problem, but the company says that it was corrected and validated as of October 10.
Still, Microsoft outlined three specific scenarios in which machines may still be affected, along with workarounds:
- WSUS/SCCM Administrators that synced the October 10th update (KB4041676 or KB4041691) before 4pm PDT October 10 may still have these KBs cached.
- WSUS/SCCM managed devices that downloaded the October 10 KB4041676 or KB4041691 update with publishing issues and have devices in a pending reboot state.
- WSUS/SCCM managed devices that installed the October 10 KB4041676 or KB4041691 update and are unable to boot and/or may land on a recovery screen.
The first scenario can be corrected by simply rescanning for updates. The second and third scenarios, however are a bit more complex. Scenario two requires systems administrators to remove pending updates by running a long string of commands. Similarly, scenario three requires a system restore or a specific set of commands to work around the issue. If you're encountering either scenario one or two, you can find Microsoft's full instructions on its support site. (opens in new tab)
Dan Thorp-Lancaster is the Editor in Chief for Windows Central. He began working with Windows Central as a news writer in 2014 and is obsessed with tech of all sorts. You can follow Dan on Twitter @DthorpL and Instagram @heyitsdtl. Got a hot tip? Send it to firstname.lastname@example.org.
Fortunately, it was mostly Servers and productive environment that were affected. Phew!
I am quite sure a bunch of sys admins will not think so :) Luckily is being fixed, or actually seems to be fixed already.
I can not make sarcasm more obvious.
/s works ;)
Get the best of Windows Central in in your inbox, every day!
Thank you for signing up to Windows Central. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.