Question about Error code 0x800f0922 and system reserved partition

Topic

New Reply

[LHiggins]

Hello,

I have been havingn some issues getting several updates to successfully install, and get an error code 0x800f0922. I checked that code and according to MS:

The error code 0x800f0922 can sometimes indicate that there isn’t enough space in the system reserved partition.

I tried to see how big mu system reserved partition was, and find that I can’t see mine. Here’s what disk management shows – no system reserved partition:

I did try an over the top repair, and all seems to be running fine, but I haven’t tried to download KB5035845 again yet. Before I do and find that it doesn’t work again, is there any way to tell if the space available for the update is causing the issue before the update fails again.

Thanks for any thoughts!

 

• This topic was modified 1 year, 1 month ago by LHiggins.
• This topic was modified 1 year, 1 month ago by LHiggins.
• This topic was modified 1 year, 1 month ago by LHiggins.

Reply | Quote

Replies

System Reserved is partition 1 in your screen shot.

Open PowerShell and run Get-Volume.

Post the results.

 

1 user thanked author for this post.

LHiggins

Reply | Quote

OldGuyForum wrote:

System Reserved is partition 1 in your screen shot.

.

So there should be plenty of free space in that partition.

Will check PowerShell in the morning when I am back on my laptop.

Thanks!

Reply | Quote

OldGuyForum wrote:

System Reserved is partition 1 in your screen shot.

Correction…

I just noticed your drive appears to be set up for UEFI.

That usually requires 4 partitions…

EFI System

Reserved

Data

Recovery

You only show 3. (EFI System, Data, Recovery)

The Reserved partition is missing.

 

 

1 user thanked author for this post.

LHiggins

Reply | Quote

OldGuyForum wrote:

I just noticed your drive appears to be set up for UEFI. That usually requires 4 partitions… EFI System Reserved Data Recovery You only show 3. (EFI System, Data, Recovery) The Reserved partition is missing.

UEFI here. I have the 3 partitions showing in Windows > Computer Management:

but 4 partitions show in MiniTool Partition Wizard 12.

1 user thanked author for this post.

LHiggins

Reply | Quote

OldGuyForum wrote:

You only show 3. (EFI System, Data, Recovery)

The Reserved partition is missing.

Drive C: on my Windows 10 Pro 22H2 is UEFI and also has no reserved partition, only the same 3 partitions as @Lhiggins; although mine are Partition 1 = OS/Data, Partition 2 = EFI System and Partiton 3 = Recovery.

And KB5035845 installed on my system just fine back on March 19!

Bear in mind, 0x800f0922 is pretty much a “generic” error code meaning the update failed and, as the explanation states, it can sometimes be caused by a missing reserved partition. However, there are a lot of other things that can cause that error.

To really figure out what it was you’d need to take a look thru the %WinDir%\Logs\CBS\CBS.log to find the first error that occurred during the update attempt which then led to a series of additional failures ultimately ending with the generic 0x800f0922 error.

1 user thanked author for this post.

LHiggins

Reply | Quote

PL1 wrote:

but 4 partitions show in MiniTool Partition Wizard 12.

We’ll see what Get-Volume shows.

1 user thanked author for this post.

LHiggins

Reply | Quote

n0ads wrote:

To really figure out what it was you’d need to take a look thru the %WinDir%\Logs\CBS\CBS.log

I’d probably start with running PowerShell Get-WindowsUpdateLog.

The results are written to the text file WindowsUpdate.log, that’s automatically saved to the user’s Desktop.

1 user thanked author for this post.

LHiggins

Reply | Quote

OldGuyForum wrote:

We’ll see what Get-Volume shows.

Here’s what the Get-Volume shows:

Also – for what it’s worth – here’s how my Marcrium looks – 4 partitions:

Will read through this thread and follow up on other thoughts.

Thanks!

Reply | Quote

Just FYI, Get-Volume only displays partitions that have a “label“.

As shown above, partitions 2 & 3 on my Drive C: have no labels so they aren’t displayed.

To display all the partitions on a disk, regardless of whether they have a label or not, you need to use Get-Partition -DiskNumber #

As shown above, all 3 partitions on my Disk 0 (drive C:) are displayed.

Also, as to the whole reserved partition thing…

BIOS/MBR disks don’t use a reserved partition.

UEFI/GPT disk “normally” do.

However, if you use Windows built-in MBR2GPT conversion tool to convert a BIOS/MBR disk to UEFI/GPT like I did, it doesn’t create a new reserved partition (which is how I wound up with only 3 partitions on a UEFI disk.)

For further info, see Microsoft’s BIOS/MBR-based hard drive partitions and UEFI/GPT-based hard drive partitions.

2 users thanked author for this post.

lmacri, LHiggins

Reply | Quote

The System Reserved partition is on MBR disks, so that bit probably isn’t relevant in your case. A 260 MB EFI System Partition should be fine for most cases (Pop_OS! Linux being the only exception I can think of).

1 user thanked author for this post.

LHiggins

Reply | Quote

LHiggins wrote:

I have been havingn some issues getting several updates to successfully install, and get an error code 0x800f0922. I checked that code and according to MS:The error code 0x800f0922 can sometimes indicate that there isn’t enough space in the system reserved partition…. … I did try an over the top repair, and all seems to be running fine, but I haven’t tried to download KB5035845 again yet.

Hi LHiggins:

According to your 01-Apr-2024 post # 2655786 in your topic KB5035845 Fails to Install you were able to successfully install the KB5034685 (Cumulative Update for .NET Framework 3.5, 4.8 and 4.8.1 for Windows 10 Version 22H2, released 13-Feb-2024) after performing an in-place repair install of your Win 10 v22H2 OS. Do you have any reason to believe that KB5035845 (Win 10 v22H2 Cumulative Quality Update / OS Build 19045.4170, released 12-Mar-2024) will continue to fail with a 0x800f0922 error after your in-place repair?

I’d suggest you unhide your KB5035845 update in WUMgr and try another installation.  It’s a waste of time if trying to speculate what might have caused these 0x800f0922 errors if the in-place repair of your OS has already fixed the problem.

If KB5035845 continues to throw an 0x800f0922 error then note that a lack of space in the system reserved partition isn’t the only cause.  I know of a few instances where Windows Update will throw this error code on a Win 10 v222 machine if the UEFI / BIOS needs to be updated – see my comments about KB5012170 (Security Update for Secure Boot DBX, released August 9, 2022) in my 20-Aug-2022 post in Susan Bradley’s It’s Time For Those August Updates to be Deferred for one example.

If you suspect your BIOS needs to be updated let us know your computer make / model and  current BIOS version. To find your current BIOS version open a Run dialog box (Windows key + R), enter msinfo32 to view your System Information, and look for the field named “BIOS Version / Date”.
————
Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.4170 * Firefox v124.0.1 * Microsoft Defender v4.18.24020.7-1.1.24020.9 * Malwarebytes Premium v4.6.11.320-1.0.2302 * Macrium Reflect Free v8.0.7783 * Dell Inspiron 5583/5584 BIOS v1.22.1

Reply | Quote

lmacri wrote:

I’d suggest you unhide your KB5035845 update in WUMgr and try another installation.  It’s a waste of time if trying to speculate what might have caused these 0x800f0922 errors if the in-place repair of your OS has already fixed the problem.

Indeed! So – I FINALLY got KB5035845 to install just now. I didn’t try it right after the repair since I wanted to let Windows Update find it and install it from there – not WuMgr (it wasn’t hidden there, but I decided not to try using that this time).

I also uninstalled the free 0Patch that I had just in case something there was causing the issue. That uninstalled all of the patches that 0Patch had applied, so between the OS repair and removing 0Patch – all seems to be working well. And 0Patch never affected my other laptop, so I really don’t think that was the issue.

Of course, I really can’t tell which thing may have been the culprit, but glad that it is all OK now – till the next time LOL!

As to a BIOS update – I will look at the links you sent and keep an eye on that if there is any further issue. My laptop is a Lenovo and it does get BIOS updates through Lenovo – last one was on Dec 30, 2023.

Thanks to everyone for all of the help with this issue. I think I am going to compile a handbook of sorts with all of the suggestions and advice to refer to if this ever happens again!

ETA: Just looked back at the notes I took while the repair was progressing and at one point in the restart process, the screen said “BIOS Self Healing backup” – so maybe it did some BIOS update then, possibly?

1 user thanked author for this post.

lmacri

Reply | Quote

LHiggins wrote:

ETA: Just looked back at the notes I took while the repair was progressing and at one point in the restart process, the screen said “BIOS Self Healing backup” – so maybe it did some BIOS update then, possibly?

Hi LHiggins:

Did you select the default “Download updates, drivers and optional features (recommended)” during the setup of your repair install?  See the image in Step # 9 of Brink’s TenForums tutorial How to Do a Repair Install of Windows 10 with an In-place Upgrade, and note that Brink recommends that users choose “Not right now” for that option to avoid possible update issues.

A few years ago I followed the instructions in Brink’s TenForums tutorial Enable or Disable Driver Updates in Windows Update to prevent Windows Update from offering driver updates (I have a Win 10 Pro OS so I used my Local Group Policy Editor), but before I made that configuration change I do recall one instance where Windows Update unexpectedly pushed out a firmware update for my Dell BIOS.
————
Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.4170 * Firefox v124.0.2 * Microsoft Defender v4.18.24020.7-1.1.24030.4 * Malwarebytes Premium v4.6.11.320-1.0.2302 * Macrium Reflect Free v8.0.7783 * Dell Inspiron 5583/5584 BIOS v1.22.1

2 users thanked author for this post.

PL1, LHiggins

Reply | Quote

Hi Imacri,

lmacri wrote:

Did you select the default “Download updates, drivers and optional features (recommended)” during the setup of your repair install?

I don’t recall seeing that screen or having that choice. I followed Susan’s directions and video for doing the repair, and it seemed to work well – and fairly quickly. I don’t remember having the choice for updates etc. I just figured that the notice about the BIOS was something to do with Lenovo’s set up.

In any case – it seems fine and I am not having any issues – and I did get KB5035845 installed without any problems.

And – just to clarify –

lmacri wrote:

…you were able to successfully install the KB5034685 (Cumulative Update for .NET Framework 3.5, 4.8 and 4.8.1 for Windows 10 Version 22H2, released 13-Feb-2024) after performing an in-place repair install of your Win 10 v22H2 OS.

Yes – but in the whole process of trying various things before the repair, I did get KB5034685 to install when the other would not. So I don’t think it had anything to do with the repair itself – just something that my laptop didn’t like about KB5035845.

Thanks again for all of your help though this whole saga!

Have a great day!

Reply | Quote

n0ads wrote:

Just FYI, Get-Volume only displays partitions that have a “label“.

Yep.

One of the reasons I label drives…and partitions.

 

 

 

1 user thanked author for this post.

LHiggins

Reply | Quote

LHiggins wrote:

ETA: Just looked back at the notes I took while the repair was progressing and at one point in the restart process, the screen said “BIOS Self Healing backup” – so maybe it did some BIOS update then, possibly?

Sounds like it based on Lenovo support:

Hi Jordan! Thanks for reaching out. The “self healing BIOS” message is normal for that generation machine. It indicates that a BIOS backup is being saved. That will happen with any BIOS update and does not indicate a problem. Hope this helps. Chx_Lenovo

2 users thanked author for this post.

LHiggins, lmacri

Reply | Quote

PL1 wrote:

That will happen with any BIOS update and does not indicate a problem.

Repair/install doesn’t touch nor update BIOS.

1 user thanked author for this post.

LHiggins

Reply | Quote