KB5010392 for Windows Server 2012 – Monthly Rollup Update for February

by
This content has been archived. But, the content is true and relevant to the underlying technology products or infrastructure services.

The monthly rollup update for Windows Server 2012 for the month of February has been released. KB5010392 is the monthly rollup update that supersedes the January monthly rollup update KB5009586. Monthly rollup updates are different than security updates. A monthly rollup update will include the security updates for the month and other improvements or non-security updates. If you are looking for the security only update for Windows Server 2012, please consider reading the full details and instructions for February month’s security update KB5010412.

Salient points about KB5010392

  • This is a monthly rollup update for Windows Server 2012 for February.
  • Security update is a different update –KB5010412.
  • KB5010392 is cumulative. It replaces KB5009586.
  • The update file is a little under 400 MB in size.

In this note, we will study more about the KB5010392 update for Windows Server 2012.

Can I install KB5010392 without installing January update KB5009586?

Yes, the monthly rollup update is of a cumulative nature. If you did not install KB5009586 monthly rollup update on Windows Server 2012, you can skip it. KB5010392 contains all the changes that were a part of the January monthly rollup update KB5009586. KB5010392 contains security and non-security updates for Windows Server 2012.

Upon patching the Windows Server 2012 with KB5009586, quite a few issues were reported by the system administrators. Some of the more significant issues were:

  • boot loop on the domain controllers.
  • failed LDAP bindings on the servers.
  • failure of the virtualization layer and virtual machines.

These issues were subsequently fixed through the release of out of band updates that were released on 17th January 2022. The out of band update that fixed the issues for the KB5009586 monthly rollup update is the KB5010797 update for Windows Server 2012. You can read more about the KB5009586 update and the issues on this page.

  • If you have already installed KB5010797, you can proceed with the deployment of current month’s monthly rollup update KB5010392. If you
  • If you did not install KB5009586, you can skip and install KB5010392 directly.

Monthly rollup KB5010392 has a size of 396.8 MB for the x64 based systems.

What vulnerabilities are resolved in KB5010392 for Windows Server 2012?

For the month of February, there have been discussions around 2 major vulnerabilities.

CVE-2022-21984 is a CVSS 8.8 vulnerability that is tagged as a zero-day attack vulnerability. This vulnerability affects Microsoft DNS Server and could lead to remote code execution attacks. Windows Server 2012 is not affected by this vulnerability. CVE-2022-21984 affects Windows Server 2019, Windows Server 20H2, Windows Server 2022, Windows 10, and Windows 11 operating systems.

CVE-2022-21907 is a vulnerability that affects the HTTP Protocol Stack or http.sys and allows remote code execution attacks. This vulnerability has a critical CVSS score of 9.8. Windows Server 2012 is not impacted by this vulnerability.

Therefore, in terms of security vulnerabilities, the February updates do not have any critical vulnerabilities for Windows Server 2012.

How can I install Windows Server 2012 KB5010392 update?

KB5010392 is a monthly rollup update that can be installed through regular ways:

  • KB5010392 can be installed automatically through the Windows Update program on your server.
  • KB5010392 can be patched automatically using the Windows Server Update Service or WSUS. You will import the updates for the configured server Windows Server 2012.
  • If you wish to deploy the KB5010392 manually, you can so from the Microsoft Update catalog. The update file weighs 396.8 MB for the Windows Server 2012 x64 edition. KB5010392 can be downloaded from this page.

Early adopters of the latest monthly rollup updates have indicated that there are no post-deployment issues for KB5010392 on the Windows Server 2012. You may have to take a maintenance window to deploy KB5010392.

If you run into any issues with the deployment of KB5010392, you can uninstall the monthly rollup update.

What issues have been resolved in KB5010392?

Quite a few issues have been resolved in the KB5010392 monthly rollup update. We mentioned these bug fixes and improvements in brief. KB5010392 resolves the following issues:

  • failed LDAP bindings issue gets resolved.
  • Jordan’s DST or Daylight Saving Time includes the month of Feburary from hereon.
  • the issue with failed virtual machines on Windows Server 2012 is resolved.
  • a new audit event has been added to mark or identify RFC-4456 incompatible systems for the Active Directory domain controllers.

There is also an issue that has affected the .NET framework on Windows Server 2012 after the deployment of January update KB5009586. Apps using Microsoft .NET Framework to acquire or set Active Directory Forest Trust Information might fail, close, or you might receive an error from the app or Windows. You might also receive an access violation (0xc0000005) error. The resolution lies in patching the .NET framework with the corresponding software update.

  • .NET framework 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1 and 4.7.2 needs to be patched with KB5011262 .NET update. You will need to download this manually from the catalog page. The update is of 375 KB.
  • .NET frameork 4.8 needs to be patched with KB5011265. This .NET patch is of 362 KB size. You can download KB5011265 manually.
  • .NET framework 4.5.2 can be patched with KB5011260 .NET update. For the x64 Windows Server 2012, KB5011260 is of 54.3 MB size. You can download KB5011260 from this page.

These updates need to be carefully drafted and deployed on Windows Server 2012.

Summary

KB5010392 superseded KB5009586. You can deploy it on Windows Server 2012 without much ado. There have been no post-installation issues on Windows Server 2012. This update takes care of all the issues that took place after January updates were rolled out on the Windows Server 2012.

You may also like to read more content related to Windows Servers in the following pages:

How useful was this post?

Click on a star to rate it!

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?

Rajesh Dhawan

Rajesh Dhawan is a technology professional who loves to blog about smart wearables, Cloud computing and Microsoft technologies. He loves to break complex problems into manageable chunks of meaningful information.