Error when updating

Wayne Wehrspann 20 Reputation points
2026-11-02T11:08:56.5633333+00:00

I tried everything you suggested...

Microsoft Windows [Version 10.0.26300.9457]

(c) Microsoft Corporation. All rights reserved.

C:\Windows\System32>DISM.exe /Online /Cleanup-image /Scanhealth

Deployment Image Servicing and Management tool

Version: 10.0.26100.8972

Image Version: 10.0.26300.9457

[==========================100.0%==========================] The component store is repairable.

The operation completed successfully.

C:\Windows\System32>DISM.exe /Online /Cleanup-image /Restorehealth

Deployment Image Servicing and Management tool

Version: 10.0.26100.8972

Image Version: 10.0.26300.9457

[==========================100.0%==========================] The restore operation completed successfully.

The operation completed successfully.

C:\Windows\System32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.

Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

still get same error

Windows for business | Windows Client for IT Pros | Performance | Other
0 comments No comments

Answer accepted by question author
James Gamble 255 Reputation points
2026-11-02T16:03:47.44+00:00

Hola Wayne,

Thanks for sharing the results! I can see that DISM initially found a repairable component store, completed the repair, and that SFC subsequently reported no integrity violations. That's encouraging, though I understand it's frustrating to go through those steps only to encounter the same update error.

Windows Update error 0x800f0922 corresponds to CBS_E_INSTALLERS_FAILED, which means Windows encountered a problem while processing an installation operation. Unfortunately, several different issues can produce this error, so knowing which component actually failed is important.

Microsoft documents cases where this error results from problems with scheduled tasks or other Windows servicing components. Other possible causes include insufficient space on the EFI System Partition or failures related to optional Windows features. However, we shouldn't assume any of those are responsible without additional evidence. Microsoft's documentation explains one of these scenarios here.

One detail I noticed is that your system reports Windows build 26300.9457, which corresponds to Windows 11 version 26H2. That helps narrow down the operating system, but we still need to identify the specific update that's failing.

Rather than having you repeat repairs or make additional system changes, I'd like to review the Windows Servicing Log. This should help us identify exactly what Windows was attempting to do when the installation failed.

Could you open PowerShell as an administrator and run the following command?

Select-String -Path "C:\Windows\Logs\CBS\CBS.log" -Pattern "0x800f0922","Failed execution","advanced installer" -Context 15,5 | Select-Object -Last 100

This searches the Component-Based Servicing log for the error and related installation failures, including some surrounding lines that might explain what went wrong. It only reads the log and doesn't change anything on your computer.

Could you share the relevant output? Please review it for any personal or machine-specific information before posting it publicly.

I'd also like to know which update is failing. You can find that information under Settings > Windows Update > Update history. Look under failed updates for the KB number.

Finally, does the update fail while Windows is running, or does it attempt to install during a restart and then roll back?

With the specific KB number and the servicing log details, we should be able to narrow down the failure considerably. I'd rather identify the actual problem before recommending changes to Windows services, partitions, or update components.

Thanks,

James

Was this answer helpful?

1 person found this answer helpful.

Answer accepted by question author
MUCYO Emmanuel 80 Reputation points Independent Advisor
2026-11-02T12:37:40.5466667+00:00

Hello Wayne Wehrspann,

Thank you for sharing the command results.

Seeing "The restore operation completed successfully" from DISM and "Windows Resource Protection did not find any integrity violations" from SFC indicates that Windows was able to repair the component store and that no operating system file corruption is currently being detected.

Because of that, the 0x800f0922 error is likely being caused by something outside of core OS file corruption. This error typically occurs due to Windows Update cache issues, network/VPN interference, .NET Framework feature installation problems, or insufficient space in the System Reserved/EFI partition.

Before proceeding, it would also be helpful to know which specific update (KB number) is failing, as that can often narrow down the cause significantly.

In the meantime, I recommend trying the following troubleshooting steps: 

Step 1: Clear the Windows Update Cache

A previous failed installation may have left corrupted update files behind in the cache.

  1. Open Command Prompt as Administrator.
  2. Stop the Windows Update services by running:
   net stop wuauserv
   net stop cryptSvc
   net stop bits
   net stop msiserver
  1. Open File Explorer, navigate to C:\Windows\SoftwareDistribution, and delete the entire contents of the folder.
  2. Restart the update services:
net start wuauserv
net start cryptSvc
net start bits
net start msiserver
  1. Restart your PC and try the update again.

Step 2: Verify .NET Framework Features

Error 0x800f0922 is frequently associated with failures involving .NET Framework feature installation during updates.

  1. Press Win + R, type optionalfeatures.exe, and press Enter.
  2. Verify that .NET Framework 3.5 and .NET Framework 4.x Advanced Services are enabled (checked).
  3. If you had to make any changes, reboot the machine before retrying the update.

Step 3: Temporarily Disable VPN or Proxy Connections

If you are connected through a VPN, proxy, or restrictive corporate network security software, temporarily disconnect or disable it and retry the update, as it can block the Microsoft update handshake.

Step 4: Check the System Reserved / EFI Partition

If the update continues to fail and roll back, check your partition layout. Historically, 0x800f0922 is closely associated with insufficient free space in the System Reserved or EFI partition, which prevents Windows from writing temporary boot files required for the upgrade.

  • Open Disk Management (diskmgmt.msc) and verify that your small boot partition is not critically low on available space.

If the issue persists after these steps, please reply with:

  • The exact KB update number that is failing.
  • Whether the failure happens during download, installation, or reboot.

That information will help narrow down the next steps immediately!

If these steps resolve your issue, please consider clicking "Accept Answer" so it remains visible to help other community members facing the same error.

Best regards.

 

 

Was this answer helpful?

1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
  1. Wayne Wehrspann 20 Reputation points
    2026-11-02T20:12:08.7466667+00:00

    file that failed update was 2026-10 Security Update (KB5127648) (26300.9711)

    I used a 3rd party app to increase the size of the EFI system partition and that cleared the problem.

    Thanks for your reply.

    Was this answer helpful?


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.