Fix: Windows Update Error Code: 0x800f0922

Windows couldnt complete the requested changes - 0x800f0922
Windows couldn't complete the requested changes.

The changes couldn't be completed. Please reboot your computer and try again.

Error Code: 0x800f0922 

Reason for Error Code: 0x800f0922

    The error code "0x800f0922" is a very common error that usually occurs during updates installation for Windows 10 or 11, the reason for this error can be one of the below,

    • There is no sufficient disk space available to install the updates.
    • There could be some conflicts with 3rd party applications.
    • There could be some network-related issues.

    If we take a look at the Windows Update common errors and mitigation page, we have this information.

    Message Description Mitigation
    0x800f0922: CBS_E_INSTALLERS_FAILED The July cumulative update failed to be installed on Windows Server 2016 In the CBS.log, you may find that updates sometimes roll back when License and Product key tokens fail to be updated. This issue can be resolved by adding write permissions for the "User" and "Network Service" accounts to the C:\Windows\System32\spp\ folder.

How to fix the issue

  1. Make sure that you have enough disk space to install the updates. If not try to make some space and try again.
  2. Make sure that you have a stable network connection. Try with another Wifi connection to see if it helps.
  3. Also make sure that your Antivirus or firewall is not interfering with the software update installation. Try to turn off the firewall and check.
  4. You can try downloading the Windows Update Catalog (KB) manually from Windows Website:
  5. Make sure that you have the latest version of NET Framework installed.
  6. Make sure that you have not connected external devices such as a pen drive or an external hard disk.
  7. Make sure that the License and Product key tokens are updated. You can address this by granting write permissions to the "User" and "Network Service" accounts for the C:\Windows\System32\spp\ folder.

Below is the answer I got from Microsoft Virtual Agent:
    Try to identify the command that failed:
    • On the affected computer, go to the %Windir%\logs\CBS folder (%Windir% represents the Windows directory on the computer’s system drive).
    • Use a text editor to open the most recent CBS.log file, and search for a “, error” string.
    • When you find this string, note the timestamp of that log entry and examine the log entries that precede that time. One of those entries should identify the command that failed

Facing issues? Have Questions? Post them here! I am happy to answer!

Author Info:

Rakesh (He/Him) has over 14+ years of experience in Web and Application development. He is the author of insightful How-To articles for Code2care.

Follow him on: X

You can also reach out to him via e-mail:

Copyright © Code2care 2024 | Privacy Policy | About Us | Contact Us | Sitemap