Registry Fix for Error 0x800f0922 and Update Rollback Issues
Summary: If your Windows Server 2016 cumulative updates are failing to install—reaching 100% then rolling back with error 0x800f0922—this article explains the fix. The issue is particularly common on servers that were upgraded from Windows Server 2012 R2.
The Problem
Since late 2025, many Windows Server 2016 administrators have been experiencing a frustrating issue: cumulative security updates appear to install successfully, reaching 100%, but then roll back during the restart with the message:
“We couldn’t complete the updates. Undoing changes.”
The error code associated with this failure is typically 0x800f0922. This has affected multiple cumulative updates including KB5066836, KB5066136, KB5070882, KB5071543, and others.
Who’s Affected?
This issue primarily affects Windows Server 2016 systems that were upgraded from Windows Server 2012 R2, rather than clean installations. The upgrade process leaves behind a legacy registry entry that conflicts with the Windows Store event log provider in newer updates.
If you have multiple Server 2016 machines and only some are experiencing this issue, check whether the affected servers were originally 2012 R2 upgrades—you’ll likely find they were.
The Cause
The update fails because of a conflict with an existing registry key for the Microsoft-Windows-Store event log provider. When the cumulative update tries to register a new event log channel, it finds that a provider with GUID {53e3d721-2aa0-4743-b2db-299d872b8e3d} already exists, causing the update to fail and roll back.
If you check the CBS.log file (located in C:\Windows\Logs\CBS\), you’ll see an error message like:
Channel Microsoft-Windows-Store/Operational is declared by an existing provider Microsoft-Windows-Store-Client-UI{{53e3d721-2aa0-4743-b2db-299d872b8e3d}}
The Fix
The solution is to delete the conflicting registry key before attempting to install the update. Here’s how:
Step 1: Back Up the Registry Key
Before deleting anything, export a backup of the key:
- Press Windows + R, type regedit, and press Enter
- Navigate to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Publishers
- Right-click on the {53e3d721-2aa0-4743-b2db-299d872b8e3d} subkey
- Select Export and save the .reg file somewhere safe
Step 2: Delete the Registry Key
You can delete the key using either the Registry Editor GUI or the command line.
Option A: Using Registry Editor
Right-click the {53e3d721-2aa0-4743-b2db-299d872b8e3d} key and select Delete
Option B: Using Command Prompt (Run as Administrator)
reg delete “HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{53e3d721-2aa0-4743-b2db-299d872b8e3d}” /f
Step 3: Install the Update
After deleting the registry key, retry the Windows Update. It should now install successfully without rolling back.
If It Still Fails
In some cases, you may also need to delete a second related registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\Microsoft-Windows-Store/Operational
Export this key first (as a backup), then delete it and retry the update.
Applying to Multiple Servers
If you have multiple Windows Server 2016 machines experiencing this issue, you can check whether they have the problematic registry key and apply the same fix. The pattern we’ve observed is consistent: servers upgraded from 2012 R2 have the issue, clean installations don’t.
You can check the CBS.log on each affected server to confirm the same error message appears before applying the fix.
Looking Ahead
This issue highlights one of the challenges with in-place upgrades—legacy registry entries can cause unexpected problems years later. As Windows Server 2016 approaches end of extended support (January 2027), it may be worth planning migrations to Server 2019 or 2022 rather than continuing to troubleshoot aging upgraded systems.
In the meantime, this registry fix should resolve the update failures and allow you to keep your Server 2016 systems patched and secure.
Need help with Windows Server updates?
Get in touch—we’re happy to help.
Give our friendly experts a call on 020 3327 0310.