Windows server 2012 r2 0x800f0922 — Ваш верный помощник с OS Windows

Microsoft Support & Malware Removal
Windows Update

You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.

[SOLVED] Windows Server 2012 can’t install all updates, keep failing with error 800F0922

Thread starter
Thread starter

TheJAC
Start date
Start date

May 9, 2016

Joined: May 9, 2016

Posts: 8

I have a physical server running Windows Server 2012 hosting a Hyper-V VM also with Windows Server 2012. Both servers eventually fail to install updates with error 800F0922. I have tried installing updates in groups, I have tried running SFC /SCANNOW, I have tried running DISM repair, I have tried SFCFIX, and I have tried an in-place upgrade on the VM. I thought the in-place upgrade was going to fix the problem, but I’m half-way through installing updates now and have run into the same error.

Here’s my SFCFIX log

SFCFix version 3.0.0.0 by niemiro.
Start time: 2016-05-09 16:13:59.867
Microsoft Windows Server 2012 — amd64
Not using a script file.

AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.

Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2016-05-09 16:21:11.574
———————-EOF————————

Attachments

CBS.zip

Joined: Jan 10, 2015

Posts: 5,184

Location: USA

I’d like to try something:

Is the bitlocker feature installed on the host or guest?

If not, follow the instructions to install the bitlocker feature here: BitLocker: How to deploy on Windows Server 212

You do not need to configure bitlocker, just install the feature and then try the update installation again.

Joined: May 9, 2016

Posts: 8

I saw that mentioned and I think I tried it previous, but I’ll give it a try as I might not have done it correctly. I’ll follow the guide and get back to you, thanks!

Joined: May 9, 2016

Posts: 8

I tried installing the Bitlocker feature, restarted, and tried again and still got the same error from Windows Update. I had seen the bitlocker issue in my research, and I found that they had released a patch for it and I already had the patch installed. This issue really has me stumped.

Joined: Jan 10, 2015

Posts: 5,184

Location: USA

Let’s try turning off secure boot temporarily for the Hyper-V VM and see if that allows the update to install.

First, shut down the VM. Next, open the VM settings and choose Firmware in the list of items on the left side.
Uncheck the box labeled ‘Enable Secure Boot’, then click OK.

Start the VM and attempt the update installation again.

Let me know if this works or if the Firmware item is not present.

Joined: May 9, 2016

Posts: 8

It’s a Gen1 VM so it doesn’t have the Firmware/SecureBoot option to disable, I checked that angle as well.

Joined: Jan 10, 2015

Posts: 5,184

Location: USA

Ok. Try installing one of the updates that is known to fail.
Once the update fails to install, zip and attach C:\Windows\Logs\CBS\CBS.log with your reply.

Joined: May 9, 2016

Posts: 8

This is from when I tried last night after installing Bitlocker

Attachments

CBS.log

Joined: Jan 10, 2015

Posts: 5,184

Location: USA

It appears that the log is incomplete. I don’t see any entries indicating an installation failure.

Are you using any utilities to clean up the log files?

Joined: May 9, 2016

Posts: 8

I’m not, but all the log files together are too large to upload. Do you want me to upload separate files?

EDIT: Here’s a link to the zip file with the whole folder…it’s 39MB.

Microsoft services

Joined: Jan 10, 2015

Posts: 5,184

Location: USA

I think I found what I was looking for.

Were these machines upgraded from Server 2008R2/2012?

Here is the error message:

Provider Microsoft-Windows-Win32k is already installed with GUID {e7ef96be-969f-414f-97d7-3ddb7b558ccc}
...
<provider guid="{8c416c79-d49b-4f01-a467-e56d3aa8234c}" messageFileName="%SystemRoot%\system32\win32k.sys" name="Microsoft-Windows-Win32k" resourceFileName="%SystemRoot%\system32\win32k.sys" symbol="W32kControlGuid">

The reason this is happening is because the win32k.sys provider registry entry isn’t getting properly updated during the upgrade process. The resolution to this problem is to:

Export and then delete the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{e7ef96be-969f-414f-97d7-3ddb7b558ccc}

Reboot

Reattempt Windows Update installation

These instructions were copied from this page: What to do if you experience a rollback when installing KB361 | The Windows Servicing Guy

Last edited: May 11, 2016

Joined: May 9, 2016

Posts: 8

Yes, both machines were upgraded to Server 2012 from Server 2008 R2. Awesome! I’ll try this tonight and reply back. Hopefully this does the trick, thank you so much!

Joined: May 9, 2016

Posts: 8

That worked (so far) at least on this server. Now I just have to get all the updates installed

Hopefully the host server will be fixed the same way and I can get them both updated and move on. Thank you, thank you, I greatly appreciate your help.

Joined: Jan 10, 2015

Posts: 5,184

Location: USA

Glad to hear it!

I’ll mark the thread solved. If you encounter further problems, please post back and I’ll continue to assist you.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Microsoft Support & Malware Removal
Windows Update

Источник

Home › Windows Server 2012 › Windows Server 2012 Error: 0x800f0922 installing updates from Windows Update

Situation

You’re running Windows Server 2012 R2 as a HyperV host.
You’re trying to use Windows Update for a Windows Server 2012 guest running on that host…
- …and Windows Update keeps failing to install the updates and rolls the server back…only to show that the updates failed leaving you back where you started.

Solution

As it turns out this is a very unique situation that isn’t well documented and if you’ve arrived here you’re fortunate because finding the solution to this difficult issue using Bing or Google is challenging at best.

It turns out that a single update KB2871690 from Microsoft is the root cause under these very specific circumstances, and the solution is now well documented here.

In my specific case I had a Domain Controller running Windows Server 2012 as a HyperV guest on a Windows Server 2012 R2 host, that would not take this update.

Simply put, adding the Bitlocker feature on the Domain Controller, rebooting, and then running this update singularly from Windows Update succeeded in getting this update applied. Once applied you can remove the feature.

Alternatively, if you do not want to install the Bitlocker feature, simply disable Secure Boot on the HyperV guest as shown below, then re-enable Secure Boot after the update is applied.

Источник

We had this odd issue when, after installing the ESU keys, the servers were still unable to receive updates and gave us back a failed installation.

After digging through the logs and confirming that we have kb5017220 and kb5022922 installed, we found out that the reason for that lies in the design of our PKI, where we don’t trust all the common CAs and don’t have CRLs allowed on the firewalls.

That’s the error code we’ve been getting – 800F0922 and 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]

After allowing the following list, all updates started to work like a charm. Damn!

Azure Certificate Authority details | Microsoft Learn

Источник

You may receive error code 800F0922 when trying to update Windows Server 2012 or Server 2012 R2 when you are trying to install Security Update KB2920189.

This error is caused by a conflict with Secure Boot. To make the update work you need to disable secure boot.

Reboot the machine into the BIOS, (usually by pressing F2 or DEL repeatedly as the server starts)
Once you are in BIOS, locate boot options and select DISABLE SECURE BOOT.
Save and exit the configuration changes and boot into the OS normally.
Run the update. It should be successful.
Reboot the system back into the BIOS screen.
In the BOOT options, re-enable SECURE BOOT, save configurations changes and restart machine booting into the OS as normal

This can also happen in Hyper-V VMs. To disable Secure Boot in Hyper-V go into the VM settings, click the firmware setting and untick”Enable Secure Boot”.

Источник

[English]Administrators of Windows Server 2012 R2 (Essentials) had the unpleasant experience that the security updates from February 14, 2023 could not be installed, but were aborted with the installation error 0x800F0922. As of February 28, 2023, Microsoft has now released a new Servicing Stack Update (SSU) to fix this installation error.

Error 0x800F0922 with Feb. 2023 update

Microsoft has released security update KB5022899 (Monthly Rollup for Windows 8.1 and Windows Server 2012 R2) and update KB5022894 (Security Only Quality Update for Windows 8.1 and Windows Server 2012 R2) on February 14, 2023. I had reported the details in the blog post Windows 7/Server 2008 R2; Server 2012 R2: Updates (February 14, 2023). Unfortunately, there were two major problems with the update installation as a result.

The message «Update not suitable for PC» occurred when the latest Servicing Stack Update (SSU) KB5018922 dated October 11, 2022 was missing.
On Windows Server 2012 R2 Essentials, update KB5022899 aborted installation with installation error 0x800F0922.

I had written about both errors in the blog post Windows Server 20212 R2 (Essentials): Feb. 2023 updates drops install error 0x800F0922. The 0x800F0922 installation error was not fixable by administrators. The background was that Microsoft’s AI-powered Extended Support update check incorrectly detected Windows Server 20212 R2 Essentials as unsupported.

The check returned the error Pre IMDS checks failed, Not Eligible, the machine has been classified as «not eligible for the update». For Windows Server 2012 R2 (no matter which variant) this is of course nonsense.

Fix with SSU KB5022922

Then on February 28, 2023, Microsoft released a fix update to address this issue. Chris Wieser pointed it out in this comment (thanks for that).

2023-02 Servicing Stack Update for Windows Server 2012 R2 for x64-based Systems (KB5022922) Released 2/28/2023

This SSU allowed Feb 2023 Monthly Rollup KB5022899 to install successfully on Server 2012 R2 Essentials

(You will have to unhide this update to see it if you have hidden it)

Servicing Stack Update KB5022922, dated February 28, 2023, makes improvements to the servicing stack, according to Microsoft. Specifically, Microsoft states that the SSU update fixes the following issue:

When you try to install updates released on Feb. 14, 2023, on some editions of Windows Server 2012 R2, the update may not install and you may receive error 0x800F0922 or the error message «The update is not applicable.»

So both update installation errors described above are addressed in the SSU. The update is deployed through Windows Update as well as WSUS, but is also available for download from the Microsoft Update Catalog for Windows Server 2012 R2, Windows Embedded 8.1 Industry Enterprise, Windows Embedded 8.1 Industry Pro.

There are no prerequisites for applying this update. The server does not need to restart after the update installation. Service stack updates (SSUs) correct the way updates are installed, but can no longer be uninstalled from the device.

Similar articles:
Microsoft Security Update Summary (February 14, 2023)
Patchday: Windows 10 Updates (February 14, 2023)
Patchday: Windows 11/Server 2022 Updates (February 14, 2023)
Windows 7/Server 2008 R2; Server 2012 R2: Updates (February 14, 2023)
Patchday: Microsoft Office Updates (February 14, 2023)
Exchange Server Security Updates (February 14, 2023)

Windows: Update installation errors (Feb. 2023)
Windows Server 20212 R2 (Essentials): Feb. 2023 updates drops install error 0x800F0922

Источник