Windows 8.1 and Windows Server 2012 R2
Find information on known issues and the servicing status for Windows 8.1 and Windows Server 2012 R2. For immediate help with Windows update issues, click here if you are using a Windows device to open the Get Help app or go to support.microsoft.com. Follow @WindowsUpdate on X (formerly Twitter) for Windows release health updates. If you are an IT administrator and want to programmatically get information from this page, use the Windows Updates API in Microsoft Graph.
Known issues
| Summary | Originating update | Status | Last updated |
|---|---|---|---|
| Devices might boot into BitLocker recovery with the July 2024 security update This issue is more likely to affect devices that have the Device Encryption option enabled | KB5040456 2024-07-09 | Investigating | 2024-07-23 13:57 PT |
| CrowdStrike issue impacting Windows endpoints causing an error message CrowdStrike issue impacting Windows endpoints causing an error message on a blue screen. | | Mitigated External | 2024-07-22 09:09 PT |
| Certain apps or devices might be unable to create Netlogon secure channel connections Scenarios which rely on synthetic RODC machine accounts might fail if they do not have a linked KRBTGT account. | KB5009624 2022-01-11 | Investigating | 2022-02-24 17:41 PT |
| Apps that acquire or set Active Directory Forest Trust Information might have issues Apps using Microsoft .NET to acquire or set Forest Trust Information might fail, close, or you might receive an error. | KB5009624 2022-01-11 | Mitigated | 2022-02-07 15:36 PT |
| Certain operations performed on a Cluster Shared Volume may fail Operations performed on files or folders on a CSV may fail with the error: STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5). | KB4480963 2019-01-08 | Mitigated | 2020-06-11 14:06 PT |
Issue details
July 2024
Devices might boot into BitLocker recovery with the July 2024 security update
| Status | Originating update | History |
|---|---|---|
| Investigating | KB5040456 2024-07-09 | Last updated: 2024-07-23, 13:57 PT Opened: 2024-07-23, 13:57 PT |
After installing the July 2024 Windows security update, released July 9, 2024 (KB5040456), you might see a BitLocker recovery screen upon booting your device. This screen does not commonly appear after a Windows update. You are more likely to face this issue if you have the Device Encryption option enabled in Settings under Privacy & Security -> Device encryption. Resulting from this issue, you might be prompted to enter the recovery key from your Microsoft account to unlock your drive.
Workaround:
Your device should proceed to start up normally from the BitLocker recovery screen once the recovery key has been entered. You can retrieve the recovery key by logging into the BitLocker recovery screen portal with your Microsoft account. Detailed steps for finding the recovery key are listed here: Finding your BitLocker recovery key in Windows.
Next steps: We are investigating the issue and will provide an update when more information is available.
Affected platforms:
- Client: Windows 11 version 23H2, Windows 11 version 22H2, Windows 11 version 21H2, Windows 10 version 22H2, Windows 10 version 21H2.
- Server: Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2, Windows Server 2008.
CrowdStrike issue impacting Windows endpoints causing an error message
| Status | Originating update | History |
|---|---|---|
| Mitigated External | | Last updated: 2024-07-22, 09:09 PT Opened: 2024-07-19, 07:30 PT |
Microsoft has identified an issue impacting Windows endpoints which are running the CrowdStrike Falcon agent, developed by CrowdStrike Holdings. Following updates released and delivered by CrowdStrike on July 18, 2024, devices running the Falcon agent may encounter an error message on a blue screen and experience a continual restarting state.
Affected systems might restart repeatedly and require recovery operations in order to restore normal use.
Updated on July 22, 2024: Microsoft has released a third mitigation option for this issue impacting Windows clients and servers. If devices are unable to recover with the two previous options mentioned below, IT admins can use PXE to remediate. See the revised New Recovery Tool to help with CrowdStrike issue impacting Windows endpoints for detailed instructions on prerequisites and configurations to use PXE Recovery.
Updated on July 21, 2024: As a follow-up to the CrowdStrike Falcon agent issue impacting Windows clients and servers, Microsoft has released an updated recovery tool with two repair options to help IT admins expedite the repair process. Based on customer feedback, this new release includes a new option for recovery using safe boot, the option to generate ISO or USB, a fix for ADK detection when the Windows Driver Kit is installed, and a fix for the USB disk size check. See the revised New Recovery Tool to help with CrowdStrike issue impacting Windows endpoints for detailed instructions on using the signed Microsoft Recovery Tool.
Updated on July 20, 2024: Microsoft has released KB5042426, which contains step-by-step guidance for Windows Servers hosted on-premises that are running the CrowdStrike Falcon agent and encountering a 0x50 or 0x7E error message on a blue screen. We will continue to work with CrowdStrike to provide the most up-to-date information available on this issue.
A new USB Recovery Tool is available to help IT admins expedite the repair process. The new tool can be found in the Microsoft Download Center. Read more about the new recovery tool and usage instructions at New Recovery Tool to help with CrowdStrike issue impacting Windows endpoints.
Updated on July 19, 2024: A new Knowledge Base article, KB5042421, with additional step-by-step guidance for Windows 11 and Windows 10 clients is now available. We will continue to work with CrowdStrike to provide up-to-date mitigation information as it becomes available.
To mitigate this issue ahead of additional resolution options, you can follow these steps:
1. Start Windows into Safe Mode or the Windows Recovery Environment.
2. Navigate to the C:\Windows\System32\drivers\CrowdStrike directory
3. Locate the file matching “C-00000291*.sys”, and delete it.
4. Restart the device.
5. Recovery of systems requires a Bitlocker key in some cases.
For Windows Virtual Machines running on Azure follow the mitigation steps in Azure status.
Additional details from CrowdStrike are available here: Statement on Windows Sensor Update - CrowdStrike Blog.
Affected platforms:
- Client: Windows 11, version 23H2; Windows 11, version 22H2; Windows 11, version 21H2; Windows 10, version 22H2; Windows 10, version 21H2; Windows 10 Enterprise LTSC 2019
- Server: Windows Server 2022; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
February 2022
Certain apps or devices might be unable to create Netlogon secure channel connections
| Status | Originating update | History |
|---|---|---|
| Investigating | KB5009624 2022-01-11 | Last updated: 2022-02-24, 17:41 PT Opened: 2022-02-24, 17:25 PT |
After installing KB5009624 or any updates released January 11, 2022 and later on your domain controllers, scenarios which rely on Read-only domain controllers (RODCs) or synthetic RODC machine accounts might fail to establish a Netlogon secure channel. RODC accounts must have a linked and compliant KRBTGT account to successfully establish a secure channel. Affected applications or network appliances, such as Riverbed SteelHead WAN Optimizers, might have issues joining domains or limitations after joining a domain.
Next Steps: Affected apps and network appliances will need an update from their developer or manufacturer to resolve this issue. Microsoft and Riverbed are presently investigating and will provide an update when more information is available.
Affected platforms:
- Server: Windows Server 2022; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
Apps that acquire or set Active Directory Forest Trust Information might have issues
| Status | Originating update | History |
|---|---|---|
| Mitigated | KB5009624 2022-01-11 | Last updated: 2022-02-07, 15:36 PT Opened: 2022-02-04, 16:57 PT |
After installing updates released January 11, 2022 or later, 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. Note for developers: Affected apps use the System.DirectoryServices API.
Next Steps: This issue was resolved in the out-of-band update for the version of .NET Framework used by the app. Note: These out-of-band updates are not available from Windows Update and will not install automatically. To get the standalone package, search for the KB number for your version of Windows and .NET Framework in the Microsoft Update Catalog. You can manually import these updates into Windows Server Update Services (WSUS) and Microsoft Endpoint Configuration Manager. For WSUS instructions, see WSUS and the Catalog Site. For Configuration Manger instructions, see Import updates from the Microsoft Update Catalog.
For instructions on how to install this update for your operating system, see the KB articles listed below:
- Windows Server 2022:
- .NET Framework 4.8 KB5011258
- Windows Server 2019:
- Windows Server 2016:
- Windows Server 2012 R2:
- Windows Server 2012:
Affected platforms:
- Client: None
- Server: Windows Server 2022; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
January 2019
Certain operations performed on a Cluster Shared Volume may fail
| Status | Originating update | History |
|---|---|---|
| Mitigated | KB4480963 2019-01-08 | Last updated: 2020-06-11, 14:06 PT Opened: 2019-01-08, 10:00 PT |
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.
Affected platforms:
- Client: Windows 8.1; Windows 7 SP1
- Server: Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
Workaround: Do one of the following:
- Perform the operation from a process that has administrator privilege.
- Perform the operation from a node that doesn’t have CSV ownership.
Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release.
Report a problem with Windows updates
To report an issue to Microsoft at any time, use the Feedback Hub app. To learn more, see Send feedback to Microsoft with the Feedback Hub app.
Need help with Windows updates?
Search, browse, or ask a question on the Microsoft Support Community. If you are an IT pro supporting an organization, visit Windows release health on the Microsoft 365 admin center for additional details.
For direct help with your home PC, use the Get Help app in Windows or contact Microsoft Support. Organizations can request immediate support through Support for business.
View this site in your language
This site is available in 11 languages: English, Chinese Traditional, Chinese Simplified, French (France), German, Italian, Japanese, Korean, Portuguese (Brazil), Russian, and Spanish (Spain). All text will appear in English if your browser default language is not one of the 11 supported languages. To manually change the display language, scroll down to the bottom of this page, click on the current language displayed on the bottom left of the page, and select one of the 11 supported languages from the list.