{"id":17869,"date":"2020-08-13T16:05:51","date_gmt":"2020-08-13T10:35:51","guid":{"rendered":"http:\/\/198.58.113.91\/blog\/?p=17869"},"modified":"2025-11-01T20:02:40","modified_gmt":"2025-11-01T14:32:40","slug":"error-0x800f0922-windows-update","status":"publish","type":"post","link":"https:\/\/www.winhelponline.com\/blog\/error-0x800f0922-windows-update\/","title":{"rendered":"Fix for Windows Update Error 0x800F0922 in Windows 10\/11"},"content":{"rendered":"

When installing an update, especially a Cumulative Update or .NET Framework package in your Windows 10 or 11 computer, the update installation may fail with an error code 0x800F0922<\/code> (“CBS_E_INSTALLERS_FAILED<\/code>“) or 0xc1900104<\/code> or the error message “Something didn’t go as planned”.<\/p>\n

\"quality<\/p>\n

\"windows<\/p>\n

In some cases, you may receive the following error:<\/p>\n

\r\nSomething didn't go as planned. Undoing changes.<\/strong>\r\n<\/pre>\n
(or)<\/p>\n
\r\nWindows couldn't be installed.<\/strong>\r\n\r\nWe couldn't update the system reserved partition.\r\n<\/pre>\n
The update process will continue normally, and during the restart phase, you’ll see the following message:<\/p>\n
\r\nWe couldn't complete the updates.<\/strong>\r\n\r\nUndoing changes. Don't turn off your computer.\r\n<\/pre>\n
\"windows<\/p>\n
The computer would restart three times<\/strong> as if it were going on a restart loop<\/strong>. It’s not a restart loop, actually. During the third reboot, you’ll see the Windows Update files getting cleaned up and the system rolled back to the previous configuration.<\/p>\n
\"windows<\/p>\n
\n
Cleaning up<\/strong><\/p>\n
Don’t turn off your computer.<\/div>\n<\/div>\n
After which, the computer will boot the Welcome screen.<\/p>\n
The Windows Update history page would show up the list of failed updates.<\/p>\n
\"windows<\/p>\n
The result will be the same if you try downloading the Cumulative Update<\/a> .msu package<\/a> from the Microsoft Update Catalog<\/a> and installing it.<\/p>\n
The most common cause for the error 0x800f0922 is the lack of free space in the System Reserved Partition. But that’s not the only reason. For a proper diagnosis, inspect the CBS.log thoroughly.<\/h4>\n
Now, let’s see how to fix the Windows Update errors 0x800F0922<\/code> and We couldn't update the system reserved partition<\/code>.<\/p>\n
Cause<\/h2>\n
The Windows Update error 0x800F0922<\/code> can occur due to one of the following reasons.<\/p>\n
    \n
  1. App Readiness service is disabled.<\/li>\n
  2. The EFI or System Reserved partition has less than 15 MB of free space.<\/li>\n
  3. The EFI boot partition is missing or has a wrong identifier.<\/li>\n
  4. Windows Sandbox or Hyper-V is installed.<\/li>\n
  5. Microsoft Edge has been uninstalled.<\/li>\n
  6. Third-party Antivirus or Malwarebytes Anti-malware blocking the installation.<\/li>\n
  7. Performance counters are damaged.<\/li>\n<\/ol>\n
    \n
    \n
    October 2025 cumulative updates fail with the error 0x800f0922.<\/h4>\n
    Please see the following article for the fix.<\/p>\n
    October 2025 LCUs Rolls back with Error 0x800F0922<\/a>\n<\/div>\n
    \n
    Fix: Windows Update error 0x800F0922<\/h2>\n
    Step 1: Start the App Readiness service<\/h3>\n
    To fix the error 0x800F0922, enable the App Readiness Service using the following steps:<\/p>\n
      \n
    1. Right-click Start, and click Run.<\/li>\n
    2. Type services.msc<\/code> and click OK.<\/li>\n
    3. Double-click App Readiness<\/strong>\u00a0and set its start type to Manual<\/strong>.\n
      RELATED:<\/strong> Windows 10 Default Services Configuration<\/a><\/div>\n<\/li>\n
    4. Click OK, and close the Services console.<\/li>\n
    5. Restart Windows.<\/li>\n
    6. Attempt to install the Windows Update(s) now.<\/li>\n<\/ol>\n
      Additional note:<\/strong> If App Readiness service is the issue, the CBS log would have the following entries — especially the error “0x80070422” (decimal equivalent is “1058”) (“ERROR_SERVICE_DISABLED”):<\/p>\n
      Info CSI 00000560 The queue has completed running, and AI failures have occured.\r\nInfo CSI 00000561 ==Error Summary Start==\r\nError CSI 00000562 (F) Installer: AppX Registration Installer Binary Name: appxreg.dll ErrorCode: 80070422 Phase: 38 Mode: Install (upgrade) Component: Microsoft-Windows-MicrosoftEdge.appxmanifestcustomized, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS[gle=0x80004005]\r\nError CSI 00000563 (F) Installer: AppX Registration Installer Binary Name: appxreg.dll ErrorCode: 80070422 Phase: 38 Mode: Install (upgrade) Component: UserExperience-Desktop, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS[gle=0x80004005]\r\nInfo CSI 00000564 ==Error Summary End==\r\nError CBS Startup: Failed to process advanced operation queue, startupPhase: 0. A rollback transaction will be created. [HRESULT = 0x800f0922 - CBS_E_INSTALLERS_FAILED]\r\nInfo CBS Setting ExecuteState key to: CbsExecuteStateInitiateRollback | CbsExecuteStateFlagAdvancedInstallersFailed<\/pre>\n
      or<\/p>\n
      CSI    000006fe@2023\/1\/16:15:17:18.460 (F) onecore\\base\\appmodel\\inboxappinstallerai\\appxreg.cpp(124): Error HRESULT_FROM_WIN32(1058) originated in function Windows::WCP::AppXRegistration::BasicInstaller::Install expression: RDSAppXOnlineNotifyPackageChanges(APPCHANGETYPE_INBOX)\r\n[0x018051] CSI    000006ff (F) Failed execution of queue item Installer: AppX Registration Installer ({f1aab1ba-6ee0-4d94-baeb-c9fd61f365cf}) with HRESULT HRESULT_FROM_WIN32(1058<\/strong>).  Failure will be ignored: The failure was encountered during rollback; installer is reliable[gle=0x80004005]<\/pre>\n
      \n
      “App Readiness” keeps getting disabled after a restart?<\/h4>\n
      If the App Readiness service gets disabled after every restart, a third-party service may be the culprit. To resolve the issue, disable all third-party services and reboot Windows.<\/p>\n
        \n
      1. Launch msconfig.exe<\/li>\n
      2. Select the Services tab.<\/li>\n
      3. Enable “Hide all Microsoft services”
        \n\"msconfig<\/li>\n
      4. Click Disable all.<\/li>\n
      5. Reboot the computer.<\/li>\n
      6. Re-enable “App Readiness” and “Storage service” (set them to “Manual”)<\/li>\n
      7. Reboot the computer.<\/li>\n
      8. Check the status of the App Readiness service. Install the cumulative update only if the App Readiness service startup setting is retained (“Manual”).<\/li>\n<\/ol>\n<\/div>\n
        The above should fix the problem in most cases. If it doesn’t help, proceed to Step 2.<\/p>\n
        \n
        Step 2: Free up disk space in the System Reserved partition<\/h3>\n
        The errors 0x800F0922<\/code> and We couldn't update system reserved partition<\/code> can occur if the System Reserved Partition (SRP) is full. The System Reserved Partition<\/a> is a small partition on your hard drive that stores boot information for Windows.<\/p>\n
        \"system<\/p>\n
        Some third-party anti-virus and security apps write to the SRP and can fill it up. Also, there are many unused font (*.ttf) files inside the SRP that you can remove to free up disk space.<\/p>\n
        \"We<\/p>\n
        The System Reserved partition doesn’t have a drive letter assigned by default. If you have an MBR partition, you can use Disk Management to assign a drive letter for the System Reserved partition and browse the contents with File Explorer. For GPT disks, you need to use the mountvol<\/code> command to assign a drive letter.<\/p>\n
        Let’s now access the SRP and delete the unused font files from the Boot\\Fonts<\/code> directory inside SRP.<\/p>\n
        Find if the disk is MBR or GPT<\/h4>\n
          \n
        1. Right-click Start, and click Disk Management.<\/li>\n
        2. Right-click on the Disk (such as Disk 0) that contains the System Reserved Partition, and select Properties.\n
          \"tipsNote that you’ll need to right-click on the Disk # on the left. Instead, if you right-click on the SRP partition itself, you won’t see the Properties option.<\/em><\/div>\n<\/li>\n
        3. In the Volumes tab, you can determine the Partition Style. It may either be GUID Partition Table (GPT) or Master Boot Record.
          \n\"find<\/li>\n<\/ol>\n
          Instructions for GPT disk:<\/h4>\n
            \n
          1. For UEFI\/GPT disks, you’ll need to open an admin Command Prompt<\/a> window and mount the System Reserved partition to a drive letter using mountvol<\/code> command.\n
            mountvol y: \/s<\/pre>\n
            The above command mounts the System Reserved partition to Y:\\ drive letter. You can’t explore the drive using File Explorer, though.<\/em><\/li>\n
          2. Switch to the Y drive by typing the following, and press Enter<\/kbd>.\n
            Y:<\/pre>\n<\/li>\n
          3. Then, navigate to the Fonts folder by typing:\n
            cd EFI\\Microsoft\\Boot\\Fonts<\/pre>\n<\/li>\n
          4. Once there, type the following to delete font files.\n
            del *.ttf<\/pre>\n
            or<\/p>\n
            del *.*<\/pre>\n
            \"delete<\/p>\n
            (when the system asks you for confirmation, press Y and then Enter to continue.)<\/em><\/p>\n
            The above command deletes all the files from the Fonts folder and frees up disk space to the tune of 13 MB approximately.<\/div>\n<\/li>\n<\/ol>\n
            Instructions for MBR disk:<\/strong><\/p>\n
              \n
            1. Right-click Start, and click Disk Management.<\/li>\n
            2. Select the partition marked System Reserved.
              \n\"system<\/li>\n
            3. Right-click on it and select Change Drive Letter and Paths<\/strong>.<\/li>\n
            4. Choose Add.<\/li>\n
            5. Enter Y<\/strong> for the drive letter.<\/li>\n
            6. Click OK.<\/li>\n
            7. Open a Command Prompt window under TrustedInstaller<\/code><\/strong> rights. To see how to open Command Prompt under Ti<\/strong> rights, see the article How to Run Programs as TrustedInstaller<\/a>.\n
              Note that the files inside the System Reserved partition are owned by TrustedInstaller.<\/em><\/div>\n<\/li>\n
            8. In the command prompt, type Y:<\/strong><\/code> and hit enter to switch to that drive.<\/li>\n
            9. Then, navigate to the Fonts folder by typing:\n
              cd Boot\\Fonts<\/pre>\n<\/li>\n
            10. Make sure you are located in Fonts<\/code> location (Y:\\Boot\\Fonts<\/code>). Then, type the following command to delete font files.\n
              del *.*<\/pre>\n
              (The system would ask you if you are sure to continue, press Y<\/kbd> and then Enter<\/kbd> to continue.)<\/em><\/li>\n
            11. Go back to Disk Management and Refresh the data to confirm if the SRP now has a greater percentage of free space. If so, the drive letter can be removed at this point.<\/li>\n
            12. Right-click the System Reserved Partition.<\/li>\n
            13. Select Change Drive Letter and Paths.<\/li>\n
            14. Choose the Y:<\/code> drive.<\/li>\n
            15. Select Remove.<\/li>\n
            16. Click OK.<\/li>\n<\/ol>\n
              Additional Information<\/h4>\n
              Other than the font files, some applications may have placed some troubleshooting tools into the System Reserved or EFI partition. Also, Dell BIOS update installers place the BIOS update files in the EFI\/System Reserved partition.<\/p>\n
              It’s advisable to remove those extra files from the EFI\/System Reserved partition or move the files somewhere else.<\/p>\n
              The CBS.log contents are from a system that encountered the error 0x800F0922 when installing the Cumulative Update KB5017389 on a Windows 11 computer. The installation reached 98%, then it encountered a problem and rolled back. At the end, the error 0x800f0922<\/code> was displayed. An archived copy of CBS.log<\/code> (CbsPersist_nnnnnnnn.log) contained the following events:<\/p>\n
              Info                  CSI    00000df5 BFSVC: 'BfspCopyFile(C:\\WINDOWS\\boot\\EFI\\fr-CA\\bootmgfw.efi.mui, \\\\?\\GLOBALROOT\\Device\\HarddiskVolume2\\EFI\\Microsoft\\Boot\\fr-CA\\bootmgfw.efi.mui) failed! (Attempt 1 of 60) Last Error = 0x70'\r\n\r\nInfo                  CSI    00000df6 BFSVC: 'BfspCopyFile(C:\\WINDOWS\\boot\\EFI\\fr-CA\\bootmgfw.efi.mui, \\\\?\\GLOBALROOT\\Device\\HarddiskVolume2\\EFI\\Microsoft\\Boot\\fr-CA\\bootmgfw.efi.mui) failed! (Attempt 2 of 60) Last Error = 0x70'\r\n\r\nInfo                  CSI    00000df7 BFSVC: 'BfspCopyFile(C:\\WINDOWS\\boot\\EFI\\fr-CA\\bootmgfw.efi.mui, \\\\?\\GLOBALROOT\\Device\\HarddiskVolume2\\EFI\\Microsoft\\Boot\\fr-CA\\bootmgfw.efi.mui) failed! (Attempt 3 of 60) Last Error = 0x70'\r\n\r\nInfo                  CSI    00000df8 BFSVC: 'BfspCopyFile(C:\\WINDOWS\\boot\\EFI\\fr-CA\\bootmgfw.efi.mui, \\\\?\\GLOBALROOT\\Device\\HarddiskVolume2\\EFI\\Microsoft\\Boot\\fr-CA\\bootmgfw.efi.mui) failed! (Attempt 4 of 60) Last Error = 0x70'\r\n\r\nInfo                  CSI    00000df9 BFSVC: 'BfspCopyFile(C:\\WINDOWS\\boot\\EFI\\fr-CA\\bootmgfw.efi.mui, \\\\?\\GLOBALROOT\\Device\\HarddiskVolume2\\EFI\\Microsoft\\Boot\\fr-CA\\bootmgfw.efi.mui) failed! (Attempt 5 of 60) Last Error = 0x70'\r\n\r\nInfo                  CSI    00000e31 BFSVC: 'Error copying boot files from C:\\WINDOWS\\boot\\EFI to \\\\?\\GLOBALROOT\\Device\\HarddiskVolume2\\EFI\\Microsoft\\Boot! Last Error = 0x70'\r\n\r\nInfo                  CSI    00000e32 BFSVC: 'ServicingBootFiles failed. Error = 0x70'\r\n\r\nError      [0x018049] CSI    00000e36 (F) Failed execution of queue item Installer: Boot File Servicing (BFSVC) Installer ({c5f0e9d7-e844-4507-89e4-701b5a747221}) with HRESULT HRESULT_FROM_WIN32(ERROR_DISK_FULL).  Failure will not be ignored: A rollback will be initiated after all the operations in the installer queue are completed; installer is reliable[gle=0x80004005]\r\n<\/pre>\n
              From another section of the log:<\/strong><\/p>\n
              Error                 CSI    000014e3 (F) Installer: Boot File Servicing (BFSVC) Installer Binary Name: bfsvc.dll  ErrorCode: 80070070 Phase: 31   Mode: Delta Component: NONE[gle=0x80004005]\r\nInfo                  CSI    000014e4 ==Error Summary End==\r\nError                 CBS    Startup: Failed to process advanced operation queue, startupPhase: 0.  A rollback transaction will be created. [HRESULT = 0x800f0922 - CBS_E_INSTALLERS_FAILED]\r\n<\/pre>\n
              It’s evident that the setup encountered the error 0x80070070<\/strong> (ERROR_DISK_FULL) when copying the .mui files for various locales to the EFI System Reserved Partition. As the System Reserved Partition had 0 bytes of free space, ERROR_DISK_FULL was encountered, and then the error 0x800f0922<\/code>.<\/p>\n
              \"efi<\/p>\n
              Deleting the unneeded font files freed up approximately 15 MB of disk space. The issue was immediately resolved as the .mui files use only ~6 MB of space.<\/h4>\n
              \nNote:<\/strong> The permanent solution<\/strong> is to resize<\/strong> the EFI System Reserved Partition to 200 MB or so. You can do that using free apps like AOMEI Partition Assistant (free).<\/p>\n
              RELATED: How to Resize the EFI System Partition using AOMEI Partition Assistant<\/a><\/em>\n<\/div>\n
              You should be able to install the Windows Update or .NET Framework update now. If not, proceed to Step 3.<\/p>\n
              \n
              Step 3: Fix the EFI System partition’s Identifier<\/h3>\n
              On UEFI\/GPT-based systems, ensure that the EFI partition exists and is identifier is set correctly. If Disk Management shows the EFI partition as the “Data partition”, it may be the root cause for the Windows Update rollback error 0x800F0922<\/code>.<\/p>\n
              For example, in the following screenshot, the EFI partition shows up as “Basic Data Partition,” and it needs to be fixed.<\/p>\n
              \"efi<\/p>\n
              To fix the identifier for the EFI system partition, open admin Command Prompt<\/strong> and run these commands:<\/p>\n
              diskpart<\/pre>\n
              list volume<\/pre>\n
              Note the volume number for the FAT32 partition, which is your EFI boot partition. The partition size typically ranges from 100 MB to 500 MB.<\/p>\n
              \"efi<\/p>\n
              In this example<\/strong>, the EFI boot partition (FAT32) is “Volume 1”.<\/p>\n
              So, run the next command:<\/p>\n
              select volume 1<\/pre>\n
              And then, set the correct identifier by running the following command:<\/p>\n
              set id=c12a7328-f81f-11d2-ba4b-00a0c93ec93b<\/pre>\n
              You should see the message “DiskPart successfully set the partition ID.” as the output.<\/em><\/p>\n
              \nSometimes (e.g., if Disk Management is open), you receive the following error when running the above command.<\/p>\n
              \r\nVirtual Disk Service error:\r\nThe device is in use.\r\n\r\nThe selected volume or partition is in use.\r\nTo continue with the operation use the OVERRIDE parameter.\r\n<\/pre>\n
              If closing Disk Management and rerunning the command doesn’t help, run the following command instead:<\/p>\n
              set id=c12a7328-f81f-11d2-ba4b-00a0c93ec93b override<\/pre>\n<\/div>\n
              Type exit<\/strong> to quit the DiskPart environment.<\/p>\n
              Type exit<\/strong> again to quit the Command Prompt window.<\/p>\n
              Close Disk Management and re-launch it. It should show the EFI partition as “EFI System Partition” underneath the “Status” column.<\/p>\n
              \"efi<\/p>\n
              See if you can install Windows Updates now.<\/p>\n
              RELATED:<\/strong> How to Rebuild the EFI Boot Partition, BCD and Boot Files<\/a><\/em><\/p>\n
              Additional Info:<\/strong> If the Windows Update rollback is due to the EFI partition issue, the CBS logs may mention the error code 80073bc3 or 0xc0000452.<\/p>\n
              \r\nError                 CSI    000011c0 (F) Installer: Boot File Servicing (BFSVC) Installer  Binary Name: bfsvc.dll  ErrorCode: 80073bc3 Phase: 31   Mode: Delta Component: NONE[gle=0x80004005]\r\nError                 CBS    Startup: Failed to process advanced operation queue, startupPhase: 0.  A rollback transaction will be created. [HRESULT = 0x800f0922 - CBS_E_INSTALLERS_FAILED]\r\n<\/pre>\n
              \n
              Step 4: Uninstall Windows Sandbox and Hyper-V<\/h3>\n
              If Hyper-V or Windows Sandbox is installed, uninstall it.<\/p>\n
              You can uninstall them by launching optionalfeatures.exe<\/strong>.<\/p>\n
              \"Hyper-V<\/p>\n
              Restart Windows when prompted.<\/p>\n
              Attempt to install the updates now.<\/p>\n
              \n
              Step 5: Reinstall Microsoft Edge (or) Delete the Edge folder<\/h3>\n
              The error 0x800F0922 can occur if Microsoft Edge has been removed from the system. To fix the issue, do one of the following:<\/p>\n
              a) Reinstall Microsoft Edge. Visit https:\/\/www.microsoft.com\/en-us\/edge\/launch\/try-edge-cle?form=MA13M0<\/a> to download Edge.<\/p>\n
              (or)<\/p>\n
              b) If you don’t want to reinstall Edge, delete the “C:\\Program Files (x86)\\Microsoft\\Edge” folder completely (if you’ve earlier uninstalled Edge.)<\/p>\n
              \n
              Step 6: Third-party AV blocking the installation.<\/h3>\n
              If you’re using a third-party antivirus solution, completely uninstall it and install the Windows update.<\/p>\n
              If you have Malwarebytes installed, please uninstall it. Additionally, use the Malwarebytes Support Tool<\/a> to remove it cleanly.<\/p>\n
              \"Malwarebytes<\/p>\n
              After a reboot, attempt to install the Windows update(s).<\/p>\n
              \n
              Step 7: Repair\/rebuild the rebuilt performance counter setting<\/h3>\n
              This step ought to fix the issue, especially if the CBS log file has one or more entries containing the line PerfCounterInstaller Error: Counter database is corrupted<\/code>. Follow these steps to fix the problem.<\/p>\n
                \n
              1. Open an admin Command Prompt<\/a> window.<\/li>\n
              2. Type the following commands and press Enter<\/kbd> after each command:\n
                cd c:\\windows\\system32\r\nlodctr \/R\r\ncd c:\\windows\\sysWOW64\r\nlodctr \/R<\/pre>\n
                \"0x800f0922<\/p>\n
                The above commands manually rebuild the Performance Counter Library values stored in the Perfh009.dat<\/code> file, and in the PerfLib<\/code> registry key.<\/p>\n
                Note:<\/strong> The parameter \/R<\/code> is case-sensitive. If the command was successful, you should see the message Info: Successfully rebuilt performance counter setting from system backup store<\/code> in the output.<\/li>\n
              3. Then, run the following command to resync the counters with WMI:\n
                WINMGMT.EXE \/RESYNCPERF<\/pre>\n<\/li>\n
              4. Exit the Command Prompt window.<\/li>\n<\/ol>\n
                Additional Information<\/h4>\n
                Your CBS.log might show something like the following:<\/p>\n
                Info  CSI    00000331 hvhostsvcstats (uninstall): CntrtextUnloadV2Provider() returns 0.\r\nError CSI    00000332 (F) PerfCounterInstaller Error: LastCounter and LastHelp are inconsistent (9380,9847).\r\n[gle=0x80004005]\r\nError CSI    00000333 (F) PerfCounterInstaller Error: Counter database is corrupted, run 'lodctr \/R' to fix it.\r\n[gle=0x80004005]<\/strong>\r\nError CSI    00000334 (F) PerfCounterInstaller Error: PERFLIB V2 CounterSet \"{9ff69334-839c-41fe-96e0-c5189ac431f2}\" counter number mismatch, initial 9847, current 9848.\r\n[gle=0x80004005]\r\nError CSI    00000335 (F) hvhostsvcstats (install): CntrtextLoadV2Provider() returns ERROR_INVALID_DATA.\r\n[gle=0x80004005]\r\nInfo  CSI    00000336\r\nCSI Advanced installer perf trace:\r\nCSIPERF:AIDONE;{b1498a21-0405-4959-adaa-7e78686acfbe};(null);168505us\r\nInfo  CSI    00000337 End executing advanced installer (sequence 0)\r\nCompletion status: HRESULT_FROM_WIN32(ERROR_INVALID_DATA)\r\nError [0x018017] CSI    00000338 (F) Failed execution of queue item Installer: Counters Installer ({b1498a21-0405-4959-adaa-7e78686acfbe}) with HRESULT HRESULT_FROM_WIN32(ERROR_INVALID_DATA).  Failure will not be ignored: A rollback will be initiated after all the operations in the installer queue are completed; installer is reliable.\r\n<\/pre>\n
                CBS.log (Another section)<\/strong><\/p>\n
                CBS.log under C:\\WINDOWS\\Logs\\CBS<\/strong>\r\n\r\nError CBS Startup: Failed to process advanced operation queue, startupPhase: 0. A rollback transaction will be created. [HRESULT = 0x800f0922 - CBS_E_INSTALLERS_FAILED]\r\nInfo CBS Setting ExecuteState key to: CbsExecuteStateInitiateRollback | CbsExecuteStateFlagAdvancedInstallersFailed\r\nInfo CBS SetProgressMessage: progressMessageStage: -1, ExecuteState: CbsExecuteStateInitiateRollback | CbsExecuteStateFlagAdvancedInstallersFailed, SubStage: 0\r\nInfo CBS Progress: UI message updated. Operation type: Update. Stage: 1 out of 1. Rollback.\r\nInfo CBS Setting original failure status: 0x800f0922, last forward execute state: CbsExecuteStateResolvePending\r\n<\/pre>\n
                I hope one of the above procedures has helped you install Windows Updates without getting the error 0x800F0922<\/code> (“CBS_E_INSTALLERS_FAILED<\/code>“).<\/p>\n
                \"windows<\/p>\n
                That’s it!<\/p>\n","protected":false},"excerpt":{"rendered":"
                When installing an update, especially a Cumulative Update or .NET Framework package in your Windows 10 or 11 computer, the update installation may fail with an error code 0x800F0922 (“CBS_E_INSTALLERS_FAILED“) or 0xc1900104 or the error message “Something didn’t go as planned”.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":true,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[8,869],"tags":[106,865,191,951,781,688],"class_list":["post-17869","post","type-post","status-publish","format-standard","hentry","category-windows-10","category-windows-11","tag-command-prompt","tag-diskpart","tag-error-messages","tag-logs","tag-windows-setup","tag-windows-update"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":71894,"url":"https:\/\/www.winhelponline.com\/blog\/kb5034204-fails-error-0x800f0922\/","url_meta":{"origin":17869,"position":0},"title":"KB5035853, KB5034765, KB5034204 fail with the error 0x800f0922","author":"Ramesh","date":"February 4, 2024","format":false,"excerpt":"The KB5034204 (2014-01), KB5034765 (2014-02), and KB5035853 (2024-03) Cumulative updates may fail with the error code 0x800f0922, which indicates a rollback has occurred. The update fails due to a version mismatch error. The CBS.log file may show the following entry: Error 0x80070519 in WinREAgent::WinREServicingManager::InternalLoad (base\\diagnosis\\srt\\winreagent\\dll\\winreservicingmanager.cpp:1044): Version mismatch, saved Servicing manager\u2026","rel":"","context":"In "Windows 11"","block_context":{"text":"Windows 11","link":"https:\/\/www.winhelponline.com\/blog\/category\/microsoft\/windows\/windows-11\/"},"img":{"alt_text":"windows 10 0x800f0922 undoing changes reboot loop","src":"https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2020\/08\/wu-undo-ing-changes-1.jpg?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2020\/08\/wu-undo-ing-changes-1.jpg?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2020\/08\/wu-undo-ing-changes-1.jpg?resize=525%2C300&ssl=1 1.5x"},"classes":[]},{"id":79689,"url":"https:\/\/www.winhelponline.com\/blog\/kb5066136-rollback-error-0x800f0922\/","url_meta":{"origin":17869,"position":1},"title":"October and November 2025 LCUs Roll back with Error 0x800F0922","author":"Ramesh","date":"October 23, 2025","format":false,"excerpt":"If the October and November 2025 updates roll back with the error 0x800F0922, this post has the solution. The same issue occurs when installing the Windows 11 updates KB5066835, KB5070773, KB5067036, KB5067036, KB5068861, Windows 10 update KB5066836, and KB5066836 (OS Build 14393.8519) update for Server 2016. The following fix can\u2026","rel":"","context":"In "Windows"","block_context":{"text":"Windows","link":"https:\/\/www.winhelponline.com\/blog\/category\/microsoft\/windows\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":78572,"url":"https:\/\/www.winhelponline.com\/blog\/build-26100-4061-ms-print-to-pdf-0x800f0922\/","url_meta":{"origin":17869,"position":2},"title":"(26100.4061) Microsoft Print to PDF Error 0x800F0922","author":"Ramesh","date":"May 15, 2025","format":false,"excerpt":"When you try to install the Microsoft Print to PDF feature on a system running Windows 11 24H2 OS build 26100.4061 or 26100.3915, the feature doesn't install. It fails with the error 0x800F0922. Internally, the FOD installation process encounters the error 800F024B. 0x800F024B SPAPI_E_FILE_HASH_NOT_IN_CATALOG The hash for the file is\u2026","rel":"","context":"In "Windows 11"","block_context":{"text":"Windows 11","link":"https:\/\/www.winhelponline.com\/blog\/category\/microsoft\/windows\/windows-11\/"},"img":{"alt_text":"print to pdf 0x800f0922 bug in May 2025 Windows 11 quality update.","src":"https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2025\/05\/ms-print-pdf-may-2025-lcu-bug.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2025\/05\/ms-print-pdf-may-2025-lcu-bug.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2025\/05\/ms-print-pdf-may-2025-lcu-bug.png?resize=525%2C300&ssl=1 1.5x, https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2025\/05\/ms-print-pdf-may-2025-lcu-bug.png?resize=700%2C400&ssl=1 2x"},"classes":[]},{"id":79729,"url":"https:\/\/www.winhelponline.com\/blog\/netfx3-update-error-0x800f0922\/","url_meta":{"origin":17869,"position":3},"title":"[Fix] .NET Framework 3.5 Installation Error 0x800F0922","author":"Ramesh","date":"October 30, 2025","format":false,"excerpt":"When you install the latest cumulative update or the .NET Framework 3.5 using OptionalFeatures.exe, the installation may rollback with the error code 0x800F0922. When the latest cumulative update fails, the CBS log may contain the following entry: Error CSI 000001f9 (F) Done with generic command 2; CreateProcess returned 0, CPAW\u2026","rel":"","context":"In "Windows 10"","block_context":{"text":"Windows 10","link":"https:\/\/www.winhelponline.com\/blog\/category\/microsoft\/windows\/windows-10\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":26807,"url":"https:\/\/www.winhelponline.com\/blog\/error-0x800f0922-print-pdf-xps-writer\/","url_meta":{"origin":17869,"position":4},"title":"(Solved) Microsoft Print to PDF Error 0x800f0922","author":"Ramesh","date":"July 6, 2022","format":false,"excerpt":"We saw in detail how to reinstall the Microsoft Print to PDF printer in Windows 10 or 11. During the process, some users have encountered the error 0x800f0922 no matter which method they used (DISM, PowerShell, the \"Add a Printer\" wizard, or the Windows Features GUI) to install the driver.\u2026","rel":"","context":"In "Windows 10"","block_context":{"text":"Windows 10","link":"https:\/\/www.winhelponline.com\/blog\/category\/microsoft\/windows\/windows-10\/"},"img":{"alt_text":"add printer - pdf error - file not found","src":"https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2022\/07\/add-printer-pdf-error.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2022\/07\/add-printer-pdf-error.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2022\/07\/add-printer-pdf-error.png?resize=525%2C300&ssl=1 1.5x"},"classes":[]},{"id":17918,"url":"https:\/\/www.winhelponline.com\/blog\/we-couldnt-update-system-reserved-partition-error-windows-10\/","url_meta":{"origin":17869,"position":5},"title":"[Fix] \u201cWe couldn\u2019t update system reserved partition\u201d Error updating Windows","author":"Ramesh","date":"August 16, 2020","format":false,"excerpt":"When upgrading to Windows 10 or 11 from Windows 7, 8, or 8.1, or updating Windows 10 or 11, you might encounter the error We couldn\u2019t update system reserved partition, or error 0xc1900104, or error code 0x800f0922. Update: If you're receiving the \"We couldn\u2019t update system reserved partition\u201d error or\u2026","rel":"","context":"In "Windows"","block_context":{"text":"Windows","link":"https:\/\/www.winhelponline.com\/blog\/category\/microsoft\/windows\/"},"img":{"alt_text":"We couldn\u2019t update system reserved partition","src":"https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2020\/08\/system-reserved-partition-error-upgrade.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2020\/08\/system-reserved-partition-error-upgrade.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2020\/08\/system-reserved-partition-error-upgrade.png?resize=525%2C300&ssl=1 1.5x, https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2020\/08\/system-reserved-partition-error-upgrade.png?resize=700%2C400&ssl=1 2x"},"classes":[]}],"_links":{"self":[{"href":"https:\/\/www.winhelponline.com\/blog\/wp-json\/wp\/v2\/posts\/17869","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.winhelponline.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.winhelponline.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.winhelponline.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.winhelponline.com\/blog\/wp-json\/wp\/v2\/comments?post=17869"}],"version-history":[{"count":0,"href":"https:\/\/www.winhelponline.com\/blog\/wp-json\/wp\/v2\/posts\/17869\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.winhelponline.com\/blog\/wp-json\/wp\/v2\/media?parent=17869"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.winhelponline.com\/blog\/wp-json\/wp\/v2\/categories?post=17869"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.winhelponline.com\/blog\/wp-json\/wp\/v2\/tags?post=17869"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}