Windows 10: Cumulative Update for Win10 Version 21H1 (KB5005033) fails in BSOD

Typical Microsoft 2 things that are always guaranteed: adding new bugs and failures. Cumulative Update for Windows 10 Version 21H1 (KB5005033) Failed to Install resulting on reboot in a BSoD. The next reboot attempts to system repair which fortunately succeeds (!!!) Updates in Settings thereafter shows: Installation Failure: Windows failed to install the following update with error 0x800F0845: 2021-08 Cumulative Update for Windows 10 Version 21H1 for x64-based Systems (KB5005033).

:)

 

KB5005033 Windows 10 2004 19041.1165, 20H2 19042.1165, 21H1 19043.1165 Win Update

could you please post a link to the article AND to the KB5005033 update?

did you also update the KB5003791?

thanks

 

KB5005033 Windows 10 2004 19041.1165, 20H2 19042.1165, 21H1 19043.1165 Win Update

KB5005033 fails repeatably, stalling on reboot with black screen with "Making changes 100%" that never changes. Rebooting gets the light blue screen and the uninstallation of KB5005033. I've tried renaming the WU files/directory, downloading and installing KB5005033 locally twice, updating my video driver (NVIDIA Geforce 660), etc. My system drive has a 529 MB system recovery partition that Disk Manager says is 100% free, as is reported for the 100 MB UEFI partition. The remaining 1862.39 GB NTFS partition is 50% available.

The first time KB5005033 failed, an on-motherboard USB 3 controller failed to restart, dropping my two 4 TB RAIDs offline. Powering down and rebooting fixed that. SFE and DISM don't find a problem. Error is usually 0x800f0922 but once got an error that indicated WU files were corrupted, and fixed that.

Anyone with suggestions on how I can get 0x800f0922 to take?

EDIT 08/13/21: I manually updated from 21H1 to 21H2 using the jar file named in KB5005033, linked from the Microsoft article on KB5003791. It adds very little, principally WPA3 H2E standard, hooks to use GPU processing from WSL and a business deployment/connectivity/logon improvement, none of which apply to my home Windows workstation. In the hopes that either the WU file or my system was different and would avoid the 0x800f0922, I re-enabled WU. It now declared the update as updating from 21H2, and it ran without a glitch. Nothing else was changed between a failure and a success, so getting WU KB5005033 worked for me from 21H2.

 

Win10: windows update stuck at never ending loop ?

When in win10:

• Update&security -> Windows update -> Finding update... .... .... ....

Planning to download the latest Win10.ISO (vers.1803) and manually update:
- Then wait that my ordered new SSD arrives and clone the old HDD to it.