Windows 10: HELP, i have never been able to update windows for a YEAR 0x800f0922

It always says somthing like "we couldnt complete the update undoing changes". i can follow directions pretty well. but im not advanced i dont know how to fix things like this.

:)

 

Windows update error 0x800f0922

Hi Michal,

Steps to Fix 0x800F0922 Update Error in Windows 10

[SOLVED]: Steps to Fix 0x800F0922 Update Error in Windows 10:

Some information for you, to solve your problem.

Best Regards,

.

 

Windows refuses to update - Error 0x800f0922


Windows won't update, i ran sfc as an Admin in CMD and no issues.

• Adobe is activated on Edge but still doesn't work, could this be related?

System Details
Windows 10 Home 64bit
Build Version: 10586.420

 

Windows Update KB5012170 error 0x800f0922

Well, it's my turn for the Patch Tuesday 'spin of the roulette wheel.' I had paused my August updates for a few weeks because I saw a lot on the internet about KB5012170 and the "Install error - 0x800f0922" that many have encountered. Thought I'd finally get them done and post how it goes. BTW, here's a link to Microsoft's discussion on this KB and associated error: https://answers.microsoft.com/en-us/...4-b86d91bb9cf9 Anyway, first laptop: Dell D5579, 4 years old, but Dell's Support Assist program has helped keep the BIOS updated. --Backed up all files, ran SFC and DISM to confirm no issues, made a Macrium backup and then ran Windows Updates. --Both KBs were successful, and SFC/DISM results were clean.

Laptop #2: Dell D7386, 3 years old, Dell Support Assist has updated BIOS several times. --Same steps - back up files, check for issues, make Macrium image, run Windows update --Both KBs were successful and SFC/DISM results were clean. Two down, one to go - will share results as I complete them. Laptop #3 is most likely to have a problem because it's not Dell, it's 7 years old, and I've not found a way to update the BIOS since it doesn't have any manufacturer support anymore. UPDATE: Laptop #3: ProStar, 7 years old. BIOS hasn't been updated to my knowledge since I got this computer in March 2015. Good news is that I followed all the same steps and had the same result - both KBs installed successfully and SFC/DISM results were clean. Maybe Microsoft did something to fix the issue in KB 5012170 ...