How to fix error 0x800f0922 in Windows 11
- Windows 11
- Supported versions of Windows Server
Quick answer
Error 0x800f0922 occurs when Windows Update fails to register required components due to staged update packages or a corrupted SecureBootEncodeUEFI scheduled task. You can resolve it by using DISM to remove staged update packages and clearing the corrupted task entries from the Windows Registry. Once these corruptions are cleared, restart your device and run Windows Update again.
Error 0x800f0922 (also logged as CBS_E_INSTALLERS_FAILED) is a Windows update error that happens when the system fails to execute advanced installer queue items during update installation. As a help-desk technician, I often see this error when Windows Update attempts to apply a cumulative update or system patch, but an underlying component fails to register. Behind the scenes, the CBS log file reveals that the installer engine encountered an underlying file-not-found error (0x80070002) while trying to register a specific task called Microsoft-OneCore-SecureBootEncodeUEFI-Task. This failure prevents the update operation from finishing and forces Windows to initiate a rollback.
This issue affects Windows 11 users and supported versions of Windows Server. When the error strikes, your screen displays a message indicating that updates could not be completed, and changes are being undone. In the system's Task Scheduler operational log, you will typically find Event ID 146 indicating that Task Scheduler failed to load task \Microsoft\Windows\PI\SecureBootEncodeUEFI at service startup with error value 2147942402. Fortunately, you can fix this problem by manually clearing staged update packages and removing the corrupted task cache keys from your registry.
Method 1: Remove staged update packages using DISM
Illustration: the Windows Update page in Windows 11 Settings
When to use: Use this method first when an update installation fails midway and leaves behind staged package files that interfere with subsequent Windows Update attempts.
- Click the Start button on your taskbar, type cmd into the search box, right-click on Command Prompt in the search results, and choose Run as administrator.
- Click Yes on the User Account Control prompt to grant administrative rights to the command line tool.
- In the command prompt window, type the following command to scan for staged packages on your system and press Enter: Dism /english /online /get-packages /format:table | findstr /i "Staged"
- Look at the output screen for table entries showing package names in a Staged state, such as Package_for_RollupFix
31bf3856ad364e35amd64~~14393XXXX. - Type the package removal command using the exact package name displayed on your screen, for example: Dism /online /remove-package /PackageName:Package_for_RollupFix
31bf3856ad364e35amd64~~14393XXXX - Press Enter and wait for the tool to finish processing until you see a success message on the screen.
What to expect afterwards: Removing lingering staged packages cleans out incomplete setup files from the update queue, allowing Windows Update to download and apply updates fresh without hitting previous file conflicts.
Method 2: Identify the corrupted task GUID in the registry
When to use: Use this method if removing staged packages alone does not solve the error and your logs show that the SecureBootEncodeUEFI task failed to register.
- Right-click the Start menu icon on your taskbar and select Command Prompt (Admin) or Terminal (Admin).
- Select Yes on the User Account Control prompt to open the elevated command window.
- Type the following registry query command to find the specific identifier (GUID) associated with the corrupted task: reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree\Microsoft\Windows\PI\SecureBootEncodeUEFI" /v ID
- Press Enter to execute the query.
- Observe the console output text on your screen. You will see a line displaying ID REG_SZ followed by a unique GUID string inside curly braces, formatted like {
<GUID>}. - Copy or carefully write down this exact GUID string, including the surrounding curly brackets, because you will need it to target the corrupted registry locations in the next step.
What to expect afterwards: Retrieving this unique identifier ensures you can precisely locate and delete only the corrupted task cache folders without disturbing any valid Windows system tasks.
Method 3: Clean up corrupted Task Scheduler registry keys
Illustration: the Windows Update page in Windows 11 Settings
When to use: Use this method after obtaining the task GUID to delete the damaged registry keys that block Task Scheduler and cause update rollbacks.
Warning: Modifying system registry keys alters core Windows operational settings. Ensure you have accurately identified the GUID from Method 2 before executing these deletion commands.
- Open an elevated Command Prompt window by searching for cmd in the Start menu, right-clicking Command Prompt, and selecting Run as administrator.
- In the console window, type the command to delete the Maintenance task cache entry (replace {GUID} with the actual GUID string obtained in Method 2): reg delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Maintenance{GUID}" /f
- Press Enter and verify that the screen shows The operation completed successfully.
- Type the second command to delete the Plain task cache entry, substituting your GUID: reg delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Plain{GUID}" /f
- Press Enter and check for the success confirmation on screen.
- Type the third command to remove the main Tasks cache entry: reg delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tasks{GUID}" /f
- Press Enter and confirm the operation completed successfully.
- Finally, type the command to remove the task tree structure key: reg delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree\Microsoft\Windows\PI\SecureBootEncodeUEFI" /f
- Press Enter, confirm all operations completed successfully, and restart your computer.
What to expect afterwards: Deleting these corrupted registry keys removes the broken task definition so Task Scheduler no longer triggers error 0x80070002, enabling Windows Update to finish installer queue tasks without rolling back.
If nothing worked
If error 0x800f0922 persists after deleting the staged update packages and clearing the corrupted task registry keys, run the Windows Update troubleshooter from your system settings to check for remaining service glitches. You can also inspect system files to verify that all installation components are healthy. Ensure your device maintains a stable internet connection and remains powered on while retrying the update process.
Sources
Frequently asked questions
What causes error 0x800f0922 in Windows 11?
Error 0x800f0922 (CBS_E_INSTALLERS_FAILED) is caused by corrupted staged update packages or a damaged SecureBootEncodeUEFI scheduled task in the system registry. When Task Scheduler fails to load this task, Windows Update cannot complete installer queue operations and triggers an automatic rollback.
Is it safe to delete the SecureBootEncodeUEFI registry keys?
Yes, deleting the corrupted registry keys associated with the SecureBootEncodeUEFI task removes broken task definitions that prevent updates from installing. Ensure you target the exact GUID returned by your registry query.
What does error 0x80070002 mean inside the CBS log?
Error 0x80070002 corresponds to a file-not-found error during installer operations. In CBS log files, it indicates that the installer phase failed because Task Scheduler could not locate the necessary files to register the scheduled task.
Checked against Microsoft's release notes on ; re-checked when a new build ships.
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