[1703, cu] We couldn't complete the updates, Undoing changes

All of my PCs are currently experiencing this problem. I haven't fully completed configuring WSUS at the moment, so I've left Windows 10 to manage the updates. However, I've noticed that all of my PCs are failing on installing KB4041676 (2017-10 Cumulative Update for Windows 10 Version 1703 for x64-based Systems.

The PC tries to install the update, then fails and says "We couldn’t complete the updates, Undoing changes" and then reboots twice before booting back in to Windows.

Any ideas as to why it might be failing? I can't see anything in the Event Viewer that could be causing the update to fail.

It's a fubared patch It's been breaking hundreds of systems across ze world!

Ironically those that can install it it's often nuking their machines into a BSOD loop if they have USB C on it

There's a post about using the script to basically delete the update for now until it's patched.

Steve

It's a fubared patch It's been breaking hundreds of systems across ze world!

There's a post about using the script to basically delete the update for now until it's patched.

Thanks for that. Any idea where I can find this script?

Interestingly, I've found a Microsoft article saying this:

Microsoft is aware of a publishing issue with the October 10th, 2017 monthly security updates for Windows 10 version 1703 (KB4041676) and version 1607 (KB4041691), and Windows Server 2016 (KB4041691) for WSUS/SCCM managed devices. Customers that download updates directly from Windows Update (Home and consumer devices) or Windows Update for Business are not impacted.

 

We have corrected the publishing issue as of the afternoon of October 10th and have validated the cumulative security updates. We recommend all customers take these cumulative security updates.

 

We have reports of the following symptoms impacting Windows Server Update Services (WSUS) and System Center Configuration Manager (SCCM) customers. Mitigation plans for the following user reported scenarios can be found below.

 

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.

 

Source = https://support.microsoft.com/en-us/help/4049094/windows-devices-may-fail-to-boot-after-installing-october-10-version-o

Ironically, seeing as I haven't fully set up WSUS yet, I shouldn't be having this issue as my PCs are downloading the update directly from Windows Update