A while ago when applying KB5008212* through Windows Update, I got errors. It was odd, as until now, all other upgrades had worked fine.
Often Windows update errors are because of lack of disk space (I try maintain 10 gigabytes or more free space on virtual machines, but that sometimes fails because some software – despite user files being on a different drive – sometimes insists on filling the system drive).
This time, Windows Update would show 0x80073701, of course right after reaching 100%, but actually it was a 0x800f081f in disguise.
My usual modus operandi didn’t solve it (with a retry after every step):
- Reboot
- Cleanup of the system drive using built-in
CleanMgr.exe(Disk cleanup) - Scan all corrupted system files and replace them from cache:
SFC /ScanNow(System File Checker) - Cleanup and repair the Windows image using
DISM /Online /Cleanup-image /Restorehealth(Deployment Image Servicing and Management)
All failed, but in the last step, DISM would consistently show error 0x800f081f.
Even a local DISM /Online /Cleanup-Image /RestoreHealth /Source:C:\Windows\WinSxS /LimitAccess would fail.
Each DISM run will actually log in two log files, and this is the trick to figure out what the next step would be.
Examples from my case:
I had trouble creating a Microsoft Account (so I could hand out on-line Office Licenses to users) where each time after solving the image or audio puzzle, it would shortly display a success, then loop back to the puzzle.
The Wiert Corner - irregular stream of stuff 