Microsoft has listed three new Windows 11 version 22H2 issues on its official page. The issues impact Direct access (Wi-Fi), Kerberos authentication and Gaming performance. The Gaming performance issue has even forced Microsoft to hold the Windows 11 version 22H2 update for affected devices.
Coming to details now, the Windows 11 22H2 Direct access issue has originated after installing the KB5019509 or later updates. The issue makes one unable to reconnect to Direct Access after temporarily losing network connectivity or transitioning between Wi-Fi networks or access points. Microsoft is using KBR to resolve the issue. Read the issue details below.
Direct Access might be unable to reconnect after your device has connectivity issues
Status Originating update History Resolved OS Build 22621.675
Resolved: 2022-11-13, 14:49 PT
Opened: 2022-11-13, 14:49 PT
After installing KB5019509 or later updates, you might be unable to reconnect to Direct Access after temporarily losing network connectivity or transitioning between Wi-Fi networks or access points. Note: This issue should not affect other remote access solutions such as VPN (sometimes called Remote Access Server or RAS) and Always On VPN (AOVPN).
Windows devices used at home by consumers or devices in organizations which are not using Direct Access to remotely access the organization’s network resources are not affected.
Workaround: If you are unable to use the resolution below, you can mitigate this issue by restarting your Windows device.
Resolution: This issue is resolved using Known Issue Rollback (KIR). Please note that it might take up to 24 hours for the resolution to propagate automatically to consumer devices and non-managed business devices. Restarting your Windows device might help the resolution apply to your device faster. For enterprise-managed devices that have installed an affected update and encountered this issue can be resolved by installing and configuring a special Group Policy. The special Group Policy can be found in Computer Configuration -> Administrative Templates -> <Group Policy name listed below>.
For information on deploying and configuring these special Group Policy, please see How to use Group Policy to deploy a Known Issue Rollback.
Group Policy downloads with Group Policy name:
- Download for Windows 11, version 22H2 – KB5018427 221029_091533 Known Issue Rollback
- Download for Windows 11, version 21H2 – KB5018483 220927_043051 Known Issue Rollback
- Download for Windows Server 2022 – KB5018485 220927_043049 Known Issue Rollback
- Download for Windows 10, version 22H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2 – KB5018482 220927_043047 Known Issue Rollback
Important: You will need to install and configure the Group Policy for your version of Windows to resolve this issue.
- Client: Windows 11, version 22H2; Windows 10, version 22H2; Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10 Enterprise LTSC 2019
- Server: Windows Server 2022; Windows Server 2019
Another Windows 11 22H2 issue that Microsoft has acknowledged impacts Kerberos authentication. This issue in fact leads to many unwanted issues that users can face. Domain user sign in and Remote Desktop connections using domain users might fail. One may face issue in accessing shared folders on workstations and file shares on servers. Even Printing that requires domain user authentication might fail. Read the issue details below.
Sign in failures and other issues related to Kerberos authentication
Status Originating update History Confirmed OS Build 22621.819
Last updated: 2022-11-13, 15:16 PT
Opened: 2022-11-13, 15:16 PT
After installing updates released on November 8, 2022 or later on Windows Servers with the Domain Controller role, you might have issues with Kerberos authentication. This issue might affect any Kerberos authentication in your environment. Some scenarios which might be affected:
- Domain user sign in might fail. This also might affect Active Directory Federation Services (AD FS) authentication.
- Group Managed Service Accounts (gMSA) used for services such as Internet Information Services (IIS Web Server) might fail to authenticate.
- Remote Desktop connections using domain users might fail to connect.
- You might be unable to access shared folders on workstations and file shares on servers.
- Printing that requires domain user authentication might fail.
When this issue is encountered you might receive a Microsoft-Windows-Kerberos-Key-Distribution-Center Event ID 14 error event in the System section of Event Log on your Domain Controller with the below text. Note: affected events will have “the missing key has an ID of 1“:While processing an AS request for target service <service>, the account <account name> did not have a suitable key for generating a Kerberos ticket (the missing key has an ID of 1). The requested etypes : 18 3. The accounts available etypes : 23 18 17. Changing or resetting the password of <account name> will generate a proper key.
Note: This issue is not an expected part of the security hardening for Netlogon and Kerberos starting with November 2022 security update. You will still need to follow the guidance in these articles even after this issue is resolved.
Windows devices used at home by consumers or devices which are not part of a on premises domain are not affected by this issue. Azure Active Directory environments that are not hybrid and do not have any on premises Active Directory servers are not affected.
Next steps: We are working on a resolution and estimate a solution will be ready in the coming weeks. This known issue will be updated with more information when it is available.
- Client: Windows 11, version 22H2; Windows 10, version 22H2; 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 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
The third issue that many users on Windows 11 22H2 are facing is related to Gaming performance. It seems that some games and apps are stuttering or not performing well on Windows 11, version 22H2. Microsoft has put Windows 11 22H2 update on hold for affected devices. Microsoft also recommends updating affected games and apps to the latest version if you are on Windows 11 version 22H2 and are already facing the issue. Read the details below.
Lower than expected performance in some games
Status Originating update History Confirmed N/A
Last updated: 2022-11-10, 18:12 PT
Opened: 2022-11-10, 17:41 PT
Some games and apps might experience lower than expected performance or stuttering on Windows 11, version 22H2. Affected games and apps are inadvertently enabling GPU performance debugging features not meant to be used by consumers.
To safeguard your upgrade experience, we have applied a compatibility hold on devices affected by this issue from being offered or installing Windows 11, version 22H2. If your organization is using Update Compliance, the safeguard IDs are 41766570 and 41990091.
Workaround: If you are already on Windows 11, version 22H2 and are experiencing this issue, you might be able to resolve it by updating your games and gaming related apps to the latest version available. If you are unsure how to update the games and apps you have installed, you will need to consult the developer of those games and apps but most will update automatically through the store they were purchased from or directly when opening them.
Next steps: We are working on a resolution and will provide an update in an upcoming release. Note: We recommend that you do not attempt to manually upgrade using the Update now button or the Media Creation Tool until this issue has been resolved and the safeguard removed.
- Client: Windows 11, version 22H2
- Server: None