July 6, 2021—KB5004955 (Monthly Rollup) Out-of-band
Applies To
Important:Ā Windows Server 2008 Service Pack 2 (SP2) hasĀ reached the end of mainstream support and isĀ now in extended support.Ā Starting in July 2020, there will no longer be optional, non-security releases (known asĀ "C"Ā releases) for this operating system. Operating systems in extended support haveĀ onlyĀ cumulative monthly security updates (known as the "B" or Update Tuesday release).article.Ā To view other notes andĀ messages, see the Windows Server 2008 Service Pack 2 updateĀ historyĀ home page.
Verify thatĀ you have installed the required updates listed in theĀ How to get this updateĀ sectionĀ beforeĀ installing this update.Ā For information about the various types of Windows updates, such as critical, security, driver, service packs, and so on, please see the followingĀImprovements and fixes
This security update includes improvements and fixes that were a part of updateĀ KB5003661Ā (released June 8, 2021) and addresses the following issues:
-
Addresses a remote code execution exploit in the Windows Print Spooler service, known as āPrintNightmareā, as documented in CVE-2021-34527. After installing this and later Windows updates, users who are not administrators can only install signed print drivers to a print server. By default, administrators can install signed and unsigned printer drivers to a print server. The installed root certificates in the systemās Trusted Root Certification Authorities trusts signed drivers. Microsoft recommends that you immediately install this update on all supported Windows client and server operating system, starting with devices that currently host the print server role. You also have the option to configure the RestrictDriverInstallationToAdministrators registry setting to prevent non-administrators from installing signed printer drivers on a print server. For more information, see KB5005010.
For more information about the resolved security vulnerabilities, please refer to the newĀ Security Update GuideĀ website.
Known issues in this update
Symptom |
Workaround |
After installing this update or later updates, connections to SQL Server 2005 might fail. You might receive an error, "Cannot connect to <Server name>, Additional information:Ā A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (.Net SqlClient Data Provider)" |
This is expected behavior due to a security hardening change in this update. To resolve this issue, you will need to update to aĀ supported version of SQL Server. |
After installing this update and restarting your device, you might receive the error, āFailure to configure Windows updates. Reverting Changes. Do not turn off your computerā, and the update might show asĀ FailedĀ inĀ Update History. |
This is expected in the following circumstances:
If you have purchased an ESU key and have encountered this issue, please verify you have applied all prerequisites and that your key is activated. For information on activation, please see thisĀ blogĀ post.Ā For information on the prerequisites, see the "How to get this update" section of this article. |
Certain operations, such asĀ rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, āSTATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)ā. This occurs when you perform the operation on a CSV owner node from a process that doesnāt have administrator privilege. |
Do one of the following:
Microsoft is working on a resolution and will provide an update in an upcoming release. |
How to get this update
Before installing this update
IMPORTANTĀ Customers who have purchased the Extended Security Update (ESU) for on-premises versions of these operating systems must follow the procedures inĀ KB4522133Ā to continue receiving security updates after extended support endsĀ on January 14, 2020.
For more information about ESU and which editions are supported, seeĀ KB4497181.
Prerequisite:
You must installĀ the updates listed below andĀ restart your deviceĀ before installing the latest Rollup. Installing these updates improves the reliability of the update process and mitigates potential issues while installing the Rollup and applying Microsoft security fixes.
-
TheĀ April 9, 2019 servicing stack update (SSU) (KB4493730). To get the standalone package for this SSU, search for it in theĀ Microsoft Update Catalog.Ā This update is required to install updates that are only SHA-2 signed.
-
The latest SHA-2 update (KB4474419) released October 8, 2019. If you are using Windows Update, the latest SHA-2 update will be offered to you automatically. This update is required to install updates that are only SHA-2 signed. For more information on SHA-2 updates, seeĀ 2019 SHA-2 Code Signing Support requirement for Windows and WSUS.
-
The Extended Security Updates (ESU) Licensing Preparation Package (KB4538484) or the Update for the Extended Security Updates (ESU) Licensing Preparation Package (KB4575904). The ESU licensing preparation package will be offered to you from WSUS.Ā To get the standalone package for ESU licensing preparation package, search for it in theĀ Microsoft Update Catalog.
After installing the items above, Microsoft strongly recommends that you install theĀ latestĀ SSUĀ (KB4580971). If you are using Windows Update, the latest SSUĀ will be offered to you automatically if you are an ESU customer.Ā To get the standalone package for the latestĀ SSU, search for it in theĀ Microsoft Update Catalog.Ā For general information about SSUs,Ā seeĀ Servicing stack updatesĀ andĀ Servicing Stack Updates (SSU): Frequently Asked Questions.
Install this update
Release Channel |
Available |
Next Step |
Windows Update and Microsoft Update |
Yes |
None. This update will be downloaded and installed automatically from Windows Update if you are an ESU customer. |
Microsoft Update Catalog |
Yes |
To get the standalone package for this update, go to theĀ Microsoft Update CatalogĀ website. |
Windows Server Update Services (WSUS) |
Yes |
This update will automatically syncĀ with WSUS if you configureĀ Products and ClassificationsĀ as follows: Product:Ā Ā Windows Server 2008 Service Pack 2 Classification: Security Updates |
File information
For a list of the files that are provided in this update, download theĀ file information for update 5004955.