This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(96, 52%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
We have Windows Server Essentials 2012 R2 that refuses to install the KB5022899 (2023-02 Security Monthly Quality Rollup). The installation process runs fine before rebooting, and after rebooting it gets to about 90% and fails with a status of "Reverting changes".
Whether I install using Windows Update or a separate installation package downloaded from the Microsoft Update Catalog site, the result is always the same.
I looked in the CBS.log file and I think I found the cause of the failure. Below is the relevant section from the CBS.log file:
2023-02-16 18:08:01, Info CSI 0000005b Begin executing advanced installer phase 38 (0x00000026) index 56 (0x0000000000000038) (sequence 95)
Old component: [l:0]""
New component: [ml:364{182},l:362{181}]"Microsoft-Windows-SLC-Component-ExtendedSecurityUpdatesAI, Culture=neutral, Version=6.3.9600.20821, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
Install mode: install
Installer ID: {4e9a75dd-0792-460c-a238-3f4130c39369}
Installer name: [38]"Extended Security Updates AI installer"
2023-02-16 18:08:01, Info CSI 0000005c Performing 1 operations; 1 are not lock/unlock and follow:
(0) LockComponentPath (10): flags: 0 comp: {l:16 b:3b97b0392942d9013400000050001801} pathid: {l:16 b:d5bcb0392942d9013500000050001801} path: [l:238{119}]"\SystemRoot\WinSxS\amd64_microsoft-windows-s..edsecurityupdatesai_31bf3856ad364e35_6.3.9600.20821_none_59d19e7ff626dfcd" pid: 50 starttime: 133210407566792062 (0x01d94228ef67557e)
2023-02-16 18:08:01, Info CSI 00000001 ESU: Product = 50 (0x00000032).
2023-02-16 18:08:01, Info CSI 00000002 ESU: Pre IMDS checks failed, Not Eligible:HRESULT_FROM_WIN32(1605)
2023-02-16 18:08:01, Info CSI 0000005d Performing 1 operations; 1 are not lock/unlock and follow:
(0) LockComponentPath (10): flags: 0 comp: {l:16 b:8ae1b2392942d9013600000050001801} pathid: {l:16 b:8ae1b2392942d9013700000050001801} path: [l:234{117}]"\SystemRoot\WinSxS\x86_microsoft.windows.s..ation.badcomponents_31bf3856ad364e35_6.3.9600.16384_none_cd3183f2deb856d2" pid: 50 starttime: 133210407566792062 (0x01d94228ef67557e)
2023-02-16 18:08:01, Error [0x01805c] CSI 0000005e (F) Failed execution of queue item Installer: Extended Security Updates AI installer ({4e9a75dd-0792-460c-a238-3f4130c39369}) with HRESULT HRESULT_FROM_WIN32(1605). Failure will not be ignored: A rollback will be initiated after all the operations in the installer queue are completed; installer is reliable (2)[gle=0x80004005]
2023-02-16 18:08:01, Info CBS Added C:\Windows\Logs\CBS\CBS.log to WER report.
2023-02-16 18:08:02, Info CBS Startup: Changing logon timeout to a static timeout: 10800000
2023-02-16 18:08:02, Info CBS Progress: UI message updated. Operation type: Update. Stage: 1 out of 1. Percent progress: 90.
2023-02-16 18:08:02, Info CBS Winlogon: TiCoreOnCreateSession has been called
2023-02-16 18:08:02, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20230216051202.log to WER report.
2023-02-16 18:08:02, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20230215202801.log to WER report.
2023-02-16 18:08:02, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20230215113825.log to WER report.
2023-02-16 18:08:03, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20230215040633.log to WER report.
2023-02-16 18:08:03, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20230215001018.log to WER report.
2023-02-16 18:08:03, Info CBS Could not get active session for current session file logging [HRESULT = 0x80004003 - E_POINTER]
2023-02-16 18:08:03, Info CBS Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2023-02-16 18:08:03, Info CSI 0000005f Creating NT transaction (seq 2), objectname [6]"(null)"
2023-02-16 18:08:03, Info CSI 00000060 Created NT transaction (seq 2) result 0x00000000, handle @0x390
2023-02-16 18:08:03, Info CSI 00000061@2023/2/16:17:08:03.270 Beginning NT transaction commit...
2023-02-16 18:08:03, Info CSI 00000062@2023/2/16:17:08:03.491 CSI perf trace:
CSIPERF:TXCOMMIT;236776
2023-02-16 18:08:03, Info CSI 00000063@2023/2/16:17:08:03.491 CSI Advanced installer perf trace:
CSIPERF:AIDONE;{4e9a75dd-0792-460c-a238-3f4130c39369};Microsoft-Windows-SLC-Component-ExtendedSecurityUpdatesAI, Version = 6.3.9600.20821, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral;2383985us
2023-02-16 18:08:03, Info CSI 00000064 End executing advanced installer (sequence 95)
Completion status: HRESULT_FROM_WIN32(ERROR_ADVANCED_INSTALLER_FAILED)
I would like to single out these lines:
So does this mean that the installation process is treating the system as if an ESU is required to install the update? Or have I misinterpreted the information in the CBS.log file? As far as I know, Windows Server 2012 R2 should not require an ESU until after October 10, 2023.
I should add that I have had problems installing the 2023-01 Security Monthly Quality Rollup before, but of a different kind. The installation package was not downloaded correctly via Windows Update, and the installation failed in the first stage before rebooting (or didn't start at all, I can't remember). Anyway, I was able to successfully install the January update using a standalone installer package downloaded from the Microsoft Update Catalog website.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(38.4, 50%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMC%3C/text%3E%3C/svg%3E)
Tried Feb 2023 on 2 servers which failed very similar to the initial post by strasmar
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(265.6, 45%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPM%3C/text%3E%3C/svg%3E)
same error on Windows Server Essentials 2012 R2
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(192, 56.00000000000001%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EL%3C/text%3E%3C/svg%3E)
+1
Same error on Windows Server Essentials 2012 R2.
The error status code is: 0x800F0922 - just to help people find this topic through search engines.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(182.40000000000003, 47%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJW%3C/text%3E%3C/svg%3E)
I can confirm that I have the exact same issue, down to the logging details.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(51.2, 79%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGN%3C/text%3E%3C/svg%3E)
Had a couple of similar reports - it seems, that MS forgot to add the activation IDs for Windows Server 2012 R2 Essentials before they added the Extended Support Update check - see Windows Server 20212 R2: Feb. 2023 updates drops install error 0x800F0922
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(310.4, 38%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECW%3C/text%3E%3C/svg%3E)
Installed correctly to Windows Server 2012 R2 64bit Essentials O/S and one of two VM's.
Persistently failing to complete install to second VM and rolling back to pre-install as per initial post by strasmar.
Extended availability of ESU option to ensure support beyond October 2023 would be helpful.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(163.2, 79%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELY%3C/text%3E%3C/svg%3E)
Having the same issue on a large number of 2012 R2 Standard edition machines.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(134.4, 5%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EIF%3C/text%3E%3C/svg%3E)
I'm having the same issue with 1x Server Essentials 2012 R2.
Disapproving the Windows updates in WSUS, and just trying the IE/.Net Framework security updates resulted in the same outcome.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(275.2, 63%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESB%3C/text%3E%3C/svg%3E)
to Lui, Yeung you indicate this is occuring on standard 2012 r2? Are you seeing the same things in the log files? I have a standard 2012 R2 and can't report it. I reported the Essentials sku problem to someone at Microsoft.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(51.2, 83%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Can anyone with Essentials check if new "2023-02 Servicing Stack Update (KB5022922)" fix the issue?
https://www.catalog.update.microsoft.com/Search.aspx?q=kb5022922
I just checked and the issue has indeed been solved. At least for the Server Essentials 2012 R2 machine from the original post.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(140.8, 43%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EI%3C/text%3E%3C/svg%3E)
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 26%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EWM%3C/text%3E%3C/svg%3E)
I just downloaded and installed the Servicing Stack Update on Server 2012R2 Essentials. It then successfully installed KB5022899. I had to manually download and install the Servicing Stack update. Windows Update won't show it as long as KB5022899 is still showing as an item to be installed. On my non Essentials server, KB5022899 installed without problems. After it was installed, doing a search for new updates in Windows Update retrieved the Servicing Stack. So, as stated above, it only appears to not show the Servicing Stack if the Roll-up patch is still listed. Just manually download and install the Servicing Stack first and you should be good to go.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(307.2, 92%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EOB%3C/text%3E%3C/svg%3E)
Yes, confirmed KB5022922 updated SSU fixes the problem with 2012R2 Essentials. Have installed SSU first, no reboot required, then normal Windows Update on test server successfully and will roll out on remainder tomorrow
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(304, 77%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELG%3C/text%3E%3C/svg%3E)
yes I was wasting a lot of time troubleshooting until I see the logs that another service stack packing is required once install the KB5022922 that you mentioned, now all Feb updates are successfully installed it
They added ESU component to block Windows 8.1 Client, apparently they missed adding ServerSolution as supported edition, lol.
no fix other than re-releasing new version of 2023-02 updates with corrected ESU component
This is not strictly true. While the ESU mechanism seems to be what triggers the failure, there are systems where the update installs, so there is some other factor at play. But I agree that the problem is this, and the solution is a fixed update without ESU check for Server 2012 R2.
Using the script in a test environment helped ;)
You can open windows8.1-kb5022899-x64.cab (full or express) with 7-zip and extract or open this file (it's xml file)
amd64_microsoft-windows-s..edsecurityupdatesai_31bf3856ad364e35_6.3.9600.20821_none_59d19e7ff626dfcd.manifest
you would see that ServerSolution = 0x32 is not added with other Server SKUs (3rd & 4th column)
i agree that the mechanism is not precise, as it should currently skip any ESU verification for all Servers (NT ProductType 2 or 3)
Same. This Server 2012 R2 Essentials issue is widespread.
deleted