Windows and the future of hybrid work
Explore what's next in security, productivity, and management.
Windows 8.1 and Windows Server 2012 R2
Find information on known issues for Windows 8.1 and Windows Server 2012 R2. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s). Want the latest Windows release health updates? Follow @WindowsUpdate on Twitter.
- How to get Windows 11
Explore the upgrade experience.
Known issues
This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.
| Summary | Originating update | Status | Last updated |
|---|---|---|---|
| RRAS Servers can lose connectivity if NAT is enabled on the public interface Devices which connect to the server can also fail to connect to the internet | KB5014738 2022-06-14 | Resolved KB5015874 | 2022-07-12 10:00 PT |
| Unable to connect to internet when using Wi-Fi hotspot feature After installing updates released June 14, 2022, you might have issues using Wi-Fi hotspot on Windows device. | KB5014738 2022-06-14 | Resolved KB5015874 | 2022-07-12 10:00 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
June 2022
RRAS Servers can lose connectivity if NAT is enabled on the public interface
| Status | Originating update | History | Resolved KB5015874 | KB5014738 2022-06-14 | Resolved: 2022-07-12, 10:00 PT Opened: 2022-06-24, 16:48 PT |
|---|
After installing KB5014738, Windows Servers which are using the Routing and Remote Access Service (RRAS) might be unable to correctly direct internet traffic. Devices which connect to the server might fail to connect to the internet, and servers can lose connection to the internet after a client device connects.
Workaround: This issue can be avoided by temporarily disabling the NAT feature on the RRAS server. For steps and guidance on this, note the ability to uncheck the 'Enable NAT on this interface' option described on step 7 of the article Enable and Configure NAT.
Resolution: This issue was resolved in KB5015874, and updates released July 12, 2022 or later. We recommend you install the latest security update for your device.
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
Unable to connect to internet when using Wi-Fi hotspot feature
| Status | Originating update | History | Resolved KB5015874 | KB5014738 2022-06-14 | Resolved: 2022-07-12, 10:00 PT Opened: 2022-06-16, 14:12 PT |
|---|
After installing KB5014738, Windows devices might be unable to use the Wi-Fi hotspot feature. When attempting to use the hotspot feature, the host device might lose the connection to the internet after a client device connects.
Workaround: To mitigate the issue and restore internet access on the host device, you can disable the Wi-Fi hotspot feature. For instructions, please see Use your Windows PC as a mobile hotspot.
Resolution: This issue was resolved in KB5015874.
Affected platforms:
- Client: Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1
- Server: Windows Server 2022; Windows Server, version 20H2; Windows Server 2019; 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:
- .NET Framework 4.8 KB5011266
- .NET Framework 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1 or 4.7.2 KB5011263
- .NET Framework 4.5.2 KB5011261
- 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.