Windows Update Error 0x800f0922

My issue had nothing to do with drive partition sizes etc. my PC is a MICROSOFT SURFACE BOOK 2 so it is their own hardware running their own OS! 

There is something weird and definitely unhelpful with this issue when you get hit by it but it seems one persons "Windows Update Error 0x800f0922" is not the same as another persons....

the only obvious fix is to re-install\in-situ update your Windows install, if you are replacing your HDD and your Win10 installation is legitimate (upgrade from Win7) you don't need to buy it again, install and let it authenticate via the Web as you will have a digital license.

What about if you have a system reserved partition of only 100 MB after upgrading from windows 7 pro 64bit to windows 10 home 64bit then to windows 10 pro 64bit (to force the OS to recognize a multi-core CPU which didn't work by the way), hmm?

No joke I'm getting that error code and it's not even funny. 0x800f0922

None of you thought about making allowances to increase the size of the system reserved partition, did you. Instead you tell us to look up a third party software to do that for us. You have got to be seriously pulling our legs.

You've cost me too much money already, you pirates.

What's really ironic is I keep seeing the same "probable solution" posted repeatedly as if it was done by some AI software. Do you really think we're that stupid?

Add insult to injury, you send us on wild goose chases to fix an issue which you  created! Dot Net, Firewall, etc, etc ... DSM and more.

Now I've ordered a new 1tb SSD and a new full retail version of windows 10 pro just to get around an issue that should have NEVER existed in the first place if you developers would have had the foresight to see this coming. Really ... you SHOULD have.

No kidding, this last update keeps failing (1909) 13 with that error code for a very obvious reason. Don't think I haven't tried other suggestions. I've wasted my time to fix an issue you created and it is occurring consistently on two of my computers. The third one (a lame Lenovo) came with W10 installed and it finally updated after some fixes. You should see the C drive now .. it's fragmented in at least 5 partitions ... WHEN THERE SHOULD BE ONLY 3 AT MOST.

For more than 20 years, I've supported MS and it's products to end up being treated like some idiot by people who don't seem to know what they are doing.

If I find a better OS than this, you can bet your last red cent that I'll be dumping this dirt.

Agree totally with your comments (and mine is still not fixed) , only worry is even if you get the new W10 Pro and new SSD, what's the guarantee that Microsoft won't mess up again on the new software update?

I was banging my head against the wall with this for ever, too. I tried all the steps online to no avail, and I was finally giving up, ready to reinstall Windows 10 from scratch.

To go about this, I once again used the Media Creation Tool and created a USB Drive to boot from, attempting to install from there. During the installation, it asked me to choose which drive I wanted to install on. When I selected my Samsung SSD, which has always been the system drive before, it complained that the drive was not valid. Windows refused to install there, because I booted in UEFI mode and the drive used MBR instead of GPT (I am running a UEFI enabled board). Scratching my head and doing some googling later, I gave this a try:

https://www.partitionwizard.com/partitionmagic/mbr2gpt.html

Basically, it converts an MBR based partition to GPT, which is what Windows 10 was asking for. I went throught the process, successfully converting my Samsung drive to GPT. Next I wanted to start the windows re-installation again, but something irked me enough to think "Meh... what if...?" So on a hunch I just rebooted to my old system one more time.

I attempted the update again, now that my system drive was GPT based. And lo and behold, it RAN FINE! O.o

I am a bit lost for words, but I guess I can start painting that blank spot on the wall where my head used to go for the last few weeks...

Maybe that little nugget of info helps someone stuck in the same place.

Hi Rob,

Error 0x800f0922 occurs when downloading the newest update of Windows 10. It also means that you have less than 500 MB in system reserved partition. You may follow the methods provided below and check if you'll be able to update your device.

Method 1. Check your Internet connection

You need to make sure that you have an internet connection and if possible, you are using wired connections

Method 2. Check .NET Framework

Make sure you have the latest version of NET Framework installed. You may enable it in Windows features. Here's how:

1. Type Windows Features on the search bar and press Enter.
2. Select Turn Windows Features on or off.
3. Check any boxes related to DotNet Framework and save selection.
4. Restart your PC.

Method 3. Turn off your Firewall

We know that this is strange doing, but even Firewall can prevent updates occasionally. Here's how you can turn it off:

1. Type Firewall on the search bar and press Enter.
2. Open Turn Windows Firewall on or off.
3. Turn off Firewall for both private and public networks.
4. Save your selection.
5. After saving your selection, you may try updating your device.

Let us know if you find this helpful. We will be glad to assist you further. 

Help