How to fix error 0x800f0922 in Windows 11
- Windows 11
- Supported versions of Windows
Daniel Okafor4 min readQuick answer
Error 0x800f0922 (CBS_E_INSTALLERS_FAILED) occurs when Windows Update fails to complete an advanced installation task, often due to corrupted scheduled tasks or blocked staged update packages. You can fix this by running the built-in Windows Update troubleshooter, removing staged packages using DISM, or clearing corrupted Task Scheduler registry keys. Follow the ordered methods below to safely restore your system's update capability.
Error 0x800f0922 (also known as CBS_E_INSTALLERS_FAILED) occurs when the Windows Update process fails during an installer phase, forcing the operating system to abort the process and perform a rollback. In simple terms, this error means that Windows attempted to apply an update, but a underlying service or task—such as the Task Scheduler loading the SecureBootEncodeUEFI task—failed to complete, causing the entire installation queue to stop.
This issue affects Windows users who are trying to install cumulative updates or quality patches. When the error triggers, the screen usually displays a message stating that updates could not be completed and that changes are being undone. If left unaddressed, the update will repeatedly attempt to install and fail every time Windows Update runs. Below are the step-by-step methods to clear out corrupted installation files and broken tasks so your computer can update normally.
Method 1: Run the Windows Update troubleshooter
When to use this method: Use this as your first step whenever an update fails. It is completely safe, requires no advanced command line knowledge, and automatically resets temporary update components.
- Click the Start menu button on your taskbar and select Settings (represented by the gear icon).
- In the System tab on the left navigation panel, scroll down on the right side and click Troubleshoot.
- Click Other troubleshooters to view the list of automated diagnostic tools.
- Locate Windows Update near the top of the list and click the Run button next to it.
- Wait for the troubleshooter to scan your system. If it identifies any issues with pending updates or service states, click Apply this fix if prompted.
- Close the Troubleshooter window once the scan completes.
What to expect afterwards: The troubleshooter will report whether it found and resolved any problems. You should restart your computer and attempt to check for updates again in Settings.
Method 2: Remove staged update packages using DISM
When to use this method: If the automated troubleshooter does not resolve error 0x800f0922, lingering staged update packages may be blocking the installer from applying new updates. This method uses the Deployment Image Servicing and Management (DISM) tool to identify and delete corrupted staged packages.
- Right-click the Start menu button on your taskbar and select Terminal (Admin) or Command Prompt (Admin) from the power user menu.
- When the User Account Control window appears asking if you want to allow the app to make changes to your device, click Yes.
- Type or paste the following command into the command window to display all staged packages, then press Enter: Dism /english /online /get-packages /format:table | findstr /i "Staged"
- The screen will list any packages currently in a Staged state, showing their exact package names.
- To remove a staged package, enter the following command (replace the example package name with the specific package name shown in your command window results):
Dism /online /remove-package /PackageName:Package_for_RollupFix
31bf3856ad364e35amd64~~14393XXXX - Press Enter and wait for DISM to complete the removal process.
What to expect afterwards: The command prompt screen will indicate that the operation completed successfully. Removing broken staged packages allows Windows Update to download fresh copies of the necessary update files.
Method 3: Clean up the corrupted SecureBootEncodeUEFI scheduled task
Warning: This method involves modifying the Windows Registry. Incorrect modifications to registry keys can cause system instability. Follow these instructions carefully and ensure you enter the commands exactly as written.
When to use this method: If update logs indicate that the installation failed due to the SecureBootEncodeUEFI task failing to register (often generating an error such as 0x80070002 or ERROR_FILE_NOT_FOUND in Task Scheduler), deleting the corrupted task entries in the registry allows Windows to recreate clean task structures.
- Right-click the Start menu button and select Terminal (Admin) or Command Prompt (Admin).
- Click Yes on the User Account Control prompt.
- Query the registry to find the specific ID associated with the SecureBootEncodeUEFI task by running this command: reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree\Microsoft\Windows\PI\SecureBootEncodeUEFI" /v ID
- Look at the output displayed on screen. Locate the string of characters inside the curly braces listed next to ID REG_SZ (this is your task's {GUID}).
- Delete the corresponding registry entries by running the following four commands one by one, replacing {GUID} with the actual identifier key retrieved in the previous step: reg delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Maintenance{GUID}" /f reg delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Plain{GUID}" /f reg delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tasks{GUID}" /f reg delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree\Microsoft\Windows\PI\SecureBootEncodeUEFI" /f
- Close the command window after each command displays a message confirming successful deletion.
What to expect afterwards: The corrupted scheduled task references will be removed from your registry. Restart your computer so the system can initialize clean scheduled task caches, then check for updates again.
If nothing worked
If error 0x800f0922 persists after attempting these methods, your Windows installation may have deeper system file corruption that prevents update installers from executing properly. As a next step, perform a general system repair by running standard System File Checker commands in an elevated command prompt. If updates continue to trigger rollbacks, you may need to pause updates temporarily or perform an in-place repair upgrade to refresh Windows system files without losing your personal data.
Sources
Frequently asked questions
What does error 0x800f0922 mean in Windows 11?
Error 0x800f0922 indicates that an installer task failed during a Windows update phase, leading to a system rollback. It is commonly triggered by corrupted scheduled tasks or broken staged package files.
Is it safe to delete staged packages with DISM?
Yes, removing staged update packages using official DISM commands is safe. It clears incomplete or corrupted update files so Windows Update can redownload clean versions.
Why does Windows Update keep rolling back after reaching a high percentage?
When an advanced installer item fails late in the installation process, Windows initiates a rollback to protect system integrity and restore your computer to its previous working state.
Verified: pending — this guide is awaiting a hands-on check on a current build.
Writes Thea's error-code and app-breakage guides. Each fix is checked against Microsoft's documentation and community reports, and updated when a new Windows 11 build changes the steps.
More from Daniel Okafor