Windows 11 22H2 and 23H2 Resolved or Fixed Issues – April 28, 2024

Windows 11 operating system has received 2 major feature updates: 2022 Update (22H2) and 2023 Update (23H2). These feature updates come with lots of new features, improvements and fixes. Apart from the new features and changes, there are also some known issues present in these updates which can cause problems to users.

Whenever a new known issue is discovered in Windows 11, Microsoft officially acknowledges the known issue and we update the known issue details in our following exclusive article:

Windows 11 22H2 and 23H2 Known Issues and Workarounds

In this article, we are going to list all known issues present in Windows 11 22H2 and 23H2 which have been resolved or fixed and no longer exist.

Following known issues have been resolved in Windows 11 22H2 and 23H2 feature updates:

ISSUE: BitLocker might Incorrectly Receive a 65000 Error in MDMs

Date: April 26, 2024

Details: Using the FixedDrivesEncryptionType or SystemDrivesEncryptionType policy settings in the BitLocker configuration service provider (CSP) node in mobile device management (MDM) apps might incorrectly show a 65000 error in the “Require Device Encryption” setting for some devices in your environment. Affected environments are those with the “Enforce drive encryption type on operating system drives” or “Enforce drive encryption on fixed drives” policies set to enabled and selecting either “full encryption” or “used space only”. Microsoft Intune is affected by this issue but third-party MDMs might also be affected. Important: This issue is a reporting issue only and does not affect drive encryption or the reporting of other issues on the device, including other BitLocker issues.

Status: Resolved

Workaround or Fix: To mitigate this issue in Microsoft Intune, you can set the “Enforce drive encryption type on operating system drives” or “Enforce drive encryption on fixed drives” policies to not configured.

Resolution: This issue was resolved by Windows updates released January 23, 2024 (KB5034203), and later. It contains important improvements and issue resolutions, including this one.

ISSUE: Compatibility Issues with Intel Smart Sound Technology Drivers and Windows 11

Date: April 12, 2024

Details: Intel and Microsoft have found incompatibility issues with certain versions of drivers for Intel Smart Sound Technology (Intel SST) on Intel 11th Gen Core processors and Windows 11. Windows 11 devices with the affected Intel SST driver might receive an error with a blue screen. The affected driver is named Intel Smart Sound Technology (Intel SST) Audio Controller under System Devices in Device Manager and is found with the file name ‘IntcAudioBus.sys’. If this file is version 10.29.0.5152 or 10.30.0.5152, this issue can occur. Only devices with both an Intel 11th Gen Core processors and an Intel SST driver version of 10.29.0.5152 or 10.30.0.5152 are affected by this issue.

To safeguard your upgrade experience, Microsoft has applied a compatibility hold on Windows 10 devices which have Intel SST driver versions 10.29.0.5152 or 10.30.0.5152. This will prevent those devices from being offered any version of Windows 11. If your organization is using Update Compliance, the safeguard IDs are:

• Windows 11, version 21H2: 36899911
• Windows 11, version 22H2: 41291788
• Windows 11, version 23H2: 49561482

Status: Resolved External

Resolution: Devices which are encountering this issue will need to install newer versions of the Intel SST Audio Controller drivers prior to updating to Windows 11. The issue is resolved by updating the Intel Smart Sound Technology drivers to version 10.30.00.5714 and later, or 10.29.00.5714 and later. Please note that later versions of this driver might refer to only the last part of the version number. For the purpose of addressing this issue, 10.30.x versions are not newer than 10.29.x versions.

For most users, updated drivers can be installed via Windows update by checking for Windows updates on your device. This is the preferred method of installing these and other drivers. If your device still encounters this safeguard hold 48 hours after updating your drivers, it’s possible drivers for this Audio Controller haven’t been developed for your specific device hardware configuration. In this case, you will need to contact your device manufacturer (OEM) for more information on the necessary drivers. Microsoft works to make the latest compatible drivers available under Windows Update whenever developers have released them.

Once you have updated to a compatible version of the Intel Smart Sound Technology drivers, you should be able to upgrade to Windows 11. Please note, if there are no other safeguards that affect your device, it can take up to 48 hours before the upgrade to Windows 11 is offered. Microsoft recommends that you do not attempt to manually upgrade using the ‘Update now’ button or the Media Creation Tool until you have performed the necessary driver updates.

ISSUE: The February 2024 Security Update might Fail to Install

Date: March 12, 2024

Details: Windows 11 devices attempting to install the February 2024 security update, released February 13, 2024 (KB5034765) and the non-security preview update, released February 29, 2024 (KB5034848) might face installation failures and the system might stop responding at 96%. Resulting from this error, the following message might be displayed:

This issue might be reflected in the Windows Event Viewer with error code 0x800F0922.

Status: Resolved

Workaround or Fix: This issue can be prevented by deleting the hidden folder C:\$WinREAgent. A restart might be required. After following these steps, installing the February 2024 security update should succeed. Users can delete the folder using File Explorer or using rd /s /q "C:\$WinREAgent" command in Command Prompt as Administrator.

Resolution: This issue was resolved in updates released March 12, 2024 (KB5035853) and later.

ISSUE: Desktop Icons might Move Unexpectedly between Monitors

Date: February 07, 2024

Details: Windows devices using more than one (1) monitor might experience issues with desktop icons moving unexpectedly between monitors or other icon alignment issues when attempting to use Copilot in Windows (in preview). To prevent users from encountering this issue, Copilot in Windows might not be available on devices that have been used or are currently being used in a multi-monitor configuration. You might also not be able to update to Windows 11, version 23H2 as Microsoft has applied a compatibility hold on devices encountering this issue. If your organization is using Windows Update for Business reports, the safeguard ID is 47615939.

Microsoft recommends that you do not attempt to manually update to Windows 11, version 23H2 using the Update now button or the Media Creation Tool until this issue has been resolved and the safeguard removed.

Status: Resolved

Resolution: This issue was resolved on the service-side for Windows 11, version 23H2 on devices with updates released January 9, 2024 or later. Non-managed consumer Windows devices with no other compatibility hold should now have Copilot for Windows available. The safeguard hold has been removed as of February 7, 2024. Eligible Windows 10 and Windows 11 devices with no other safeguards should now be able to upgrade to Windows 11, version 23H2. Please note, it can take up to 48 hours before the update to Windows 11, version 23H2 is offered. Restarting your device might help it offer faster. Note: Managed devices in your environment that have been used or are currently being used in a multimonitor configuration will not yet have Copilot for Windows available.

ISSUE: Microsoft Received Reports about Issues Connecting to Wi-Fi Networks

Date: January 09, 2024

Details: Microsoft has received reports of an issue in which some Wi-Fi adapters might not connect to some networks after installing KB5032288. Microsoft has confirmed this issue was caused by KB5032288 and KB5033375. As reported, users are more likely to be affected by this issue if they are attempting to connect to an enterprise, education, or public Wi-Fi network using 802.1x authentication. This issue is not likely to occur on home networks.

Status: Resolved

Resolution: This issue was resolved in updates released January 9, 2024 (KB5034123) and later. If you install the update, you do not need to use a Known Issue Rollback (KIR) or a special Group Policy to resolve this issue. If you are using an update released before January 9, 2024, and have this issue, you can resolve it by installing and configuring the special Group Policy. The special Group Policy can be found in Computer Configuration -> Administrative Templates -> Windows 11 22H2 KB5032288 231029_032011 Known Issue Rollback. Users can download the required group policy from this link.

ISSUE: Narrator might not Start if Installing Windows 11, Version 23H2 via ISO or Media

Date: December 22, 2023

Details: When using physical media or disc images (ISO) to install Windows 11, version 23H2 (also referred to as the Windows 11 2023 Update) on a device, Microsoft Narrator may not start. Narrator is commonly initialized using keyboard commands, such as Ctrl + Windows key + Enter. Although Narrator is present in Windows when the installation process begins, it might open in an unresponsive state when initialized using any method. Please note this issue does not occur when Windows 11, version 23H2 is installed using Windows Update on a device which is already running Windows 10 or Windows 11. This issue only occurs when physical media or ISOs are used for this installation and Narrator is only affected while the installation process is taking place. It should continue to work as expected once the installation is completed.

Status: Resolved

Workaround or Fix: Starting December 19, 2023, a new file is available to create an installation media to update to Windows 11, version 23H2. The new media does not encounter this issue and contains the December 2023 security update. It is available for download at the Software Download page for Windows 11 in the section “Download Windows 11 Disk Image (ISO) for x64 devices”.

IT administrators and users also have the option to sign in to their subscription on the Visual Studio Subscriptions portal to download the new media. You can also access the new media on the Volume Licensing Service Center (VLSC) starting December 21, 2023.

ISSUE: Printer Names and Icons might be Changed and HP Smart App Automatically Installs

Date: December 22, 2023

Details: Some issues related to printer configurations are being observed on Windows devices which have access to the Microsoft Store. Microsoft is investigating this issue and coordinating with partners on a solution. Symptoms can include the following:

• Some Windows 10 and Windows 11 devices are installing the HP Smart App.
• Printers are renamed as HP printers regardless of their manufacturer. Most are being named as the HP LaserJet M101-M106 model. Printer icons might also be changed.
• Double clicking on a printer displays the on-screen error “No tasks are available for this page”.

According to Microsoft’s investigation, this issue is not caused by an HP update. In most cases, it should be possible to use the printer as expected, including queueing printing jobs, as well as other features such as copy, scan, or fax. Printers on the device will continue to use the expected drivers for printer operations. However, this issue might affect associations with other manufacturer-supplied printer apps used to extend basic printer capabilities. If this is the case, some or all of those extended functions might not work.

Status: Resolved

Resolution: You can resolve this issue by downloading and executing one of the files listed in the article KB5034510 Printer Metadata Remediation Tool. In addition to this tool, a critical troubleshooter is being gradually rolled out to all affected Home and non-managed business devices. Critical troubleshooting happens automatically in the background and won’t get in the way of using your device.

ISSUE: Devices with Locale Set to Croatia might not Utilize the Expected Currency

Date: October 26, 2023

Details: The correct default currency might not display or be used in Windows devices which have locale set to Croatia. This can affect applications which retrieve the device’s currency for purchases or other transactions. Earlier this year, Croatia joined the Eurozone, changing its currency from the Kuna to Euro. Windows Locale data for Croatia will be updated for this change in the short term.

Status: Resolved

Workaround or Fix: Users can change the currency manually using the Windows Control Panel or directly using intl.cpl command.

Resolution: This issue was resolved in updates released on October 26, 2023 (KB5031455) and later.

ISSUE: Microsoft Received Reports about an UNSUPPORTED_PROCESSOR Error

Date: September 07, 2023

Details: Microsoft has received reports of an issue in which users are receiving an “UNSUPPORTED_PROCESSOR” error message on a blue screen after installing updates released on August 22, 2023 (KB5029351) and then restarting their device. KB5029351 might automatically uninstall to allow Windows to start up as expected.

Status: Resolved external

Resolution: After investigating these reports, it was found that the “UNSUPPORTED_PROCESSOR” error was not caused by issues in KB5029351 and is limited to a specific subset of processors. This issue will not affect future monthly updates released for Windows. KB5029351 will not be offered to Windows devices that might be affected by this issue and it is recommended that you do not attempt to manually install it on affected devices.

ISSUE: Third-Party UI Customization Apps might Prevent the Start Menu from Opening

Date: August 17, 2023

Details: After installing KB5028254 or later updates, the Start menu might not open on Windows devices with some third-party UI customization apps installed. The known affected third-party UI customization app is ExplorerPatcher but others might also be affected. These types of apps often use unsupported methods to achieve their customization and as a result can have unintended results on your Windows device.

Status: Resolved external

Workaround or Fix: Microsoft recommends uninstalling any third-party UI customization app before installing KB5028254 to prevent this issue. If your Windows device is already experiencing this issue, you might need to contact customer support for the developer of the app you are using.

Resolution: ExplorerPatcher has released a version which lists this issue as resolved. Note: If you are using any third-party UI customization app and encounter this or any other issues, you will need to contact customer support for the developer of the app you are using.

ISSUE: You might Receive an Error with apphelp.dll from Apps Using DirectX

Date: August 09, 2023

Details: After installing KB5019980 or later updates, you might receive an error with apphelp.dll on Windows devices using Intel graphics drivers with versions 26.20.100.7463 up to 30.0.101.1190. This issue might happen intermittently and affects a small number of enterprise apps which use DirectX or Direct3D to render part or all of their content. Windows devices using updated Intel graphics drivers with a version later than 30.0.101.1190 are not affected by this issue and already have the Intel resolution for this issue installed.

Status: Resolved

Workaround or Fix: To mitigate this issue, you can install an Intel graphics driver with a later version than 30.0.101.1190. It is recommended to check your Windows device manufacturer’s support for the latest version of the Intel graphics driver for your device. If they do not offer a driver later than 30.0.101.1190, you can check List of Drivers for Intel Graphics for information on how to download and install the latest Intel graphics driver available from Intel directly.

Resolution: This issue was resolved in KB5025305 update.

ISSUE: KB5012170 might Fail to Install and You might Receive a 0x800f0922 Error

Date: July 29, 2023

Details: When attempting to install KB5012170, it might fail to install, and you might receive an error 0x800f0922. This issue only affects the Security update for Secure Boot DBX (KB5012170) and does not affect the latest cumulative security updates, monthly rollups, or security only updates.

Status: Resolved

Workaround or Fix: This issue can be mitigated on some devices by updating the UEFI bios to the latest version before attempting to install KB5012170.

Resolution: This issue was resolved in KB5022913 or later updates.

ISSUE: WSUS might not Offer Updates to Windows 11, version 22H2

Date: July 28, 2023

Details: Updates released February 14, 2023 or later might not be offered from some Windows Server Update Services (WSUS) servers to Windows 11, version 22H2. The updates will download to the WSUS server but might not propagate further to client devices. Affected WSUS servers are only those running Windows Server 2022 which have been upgraded from Windows Server 2016 or Windows Server 2019. This issue is caused by the accidental removal of required Unified Update Platform (UUP) MIME types during the upgrade to Windows Server 2022 from a previous version of Windows Server. This issue might affect security updates or feature updates for Windows 11, version 22H2. Microsoft Configuration Manager is not affected by this issue.

Status: Resolved

Workaround or Fix: To mitigate this issue, Microsoft advises to see Adding file types for Unified Update Platform on premises.

Resolution: This issue was resolved in KB5023705 for Windows Server 2022.

ISSUE: Some Apps might Fail to Playback, Record, or Capture Video

Date: July 25, 2023

Details: After installing KB5027303 or later updates, some apps might fail to playback, record, or capture video when using the WVC1 codec (VC-1). Certain cameras or webcams might also fail to work if they use the WVC1 codec by default.

Status: Resolved

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.

ISSUE: When Using Outlook, Opening Links in Emails might Display an Error

Date: July 25, 2023

Details: When clicking on links in emails in Microsoft Outlook, you might receive an error message with the text “Something unexpected went wrong with this URL”. Opening links in emails on Microsoft Outlook may also display an error stating “Microsoft Office has identified a potential security concern. This location may be unsafe.”. As a result of Microsoft Office security hardening changes, hyperlinks which contain fully-qualified domain name (FQDN) or IP address will display this message. This is due to protections released July 11, 2023. Please note: This behavior is caused by a protection update in Outlook released July 11, 2023. It is not caused by Windows Updates.

Status: Resolved

Resolution: In order to ensure continued access to files on FQDN or IP address paths, add those URLs to the Trusted Sites zone in accordance with Windows guidance.

ISSUE: Integrated Camera might not Work as Expected on Some ARM-based Devices

Date: July 10, 2023

Details: Windows devices using certain Arm-based processors might have issues using integrated cameras starting on May 23, 2023. When encountering this issue, you might receive an “0xA00F4271 (0x80004005)” error when attempting to use the Camera app. Affected devices use these processors: Qualcomm 8cx Gen 1, Qualcomm 8cx Gen 2, Microsoft SQ1, and Microsoft SQ2. Note: This issue does not affect USB cameras or webcams, even when attached to an affected Windows devices.

Status: Resolved external

Workaround or Fix: Microsoft is deploying a critical troubleshooter to mitigate this issue on most affected Windows devices. Troubleshooters are applied automatically and can’t be run manually.

To mitigate this issue on managed devices where troubleshooters are disabled by your organization or if you want the mitigation before the troubleshooter has run automatically, use the following steps to disable the affected feature of the camera driver:

1. Open Command Prompt as Administrator using any method mentioned here.

2. Run following command:

reg add "HKLM\SYSTEM\CurrentControlSet\Control\Qualcomm\Camera" /v EnableQCOMFD /t REG_DWORD /d 0 /f

3. Restart any app which uses the camera or restart your computer.

The integrated camera should now function as expected.

Note: This workaround might disable some features of the camera or lower the image quality but should allow the camera to function until the issue is resolved by the device manufacturer with an updated camera driver. An updated driver should restore full camera functionality and the workaround should not need to be undone.

Resolution: This issue was resolved with the release of updated camera drivers. The updated drivers should offer and install automatically from Windows Update in the coming weeks. If you would like to check if updated drivers are available for your device, you can manually check for updates. If updated camera drivers are not already installed and not offered when manually checking Windows Update, they might not be available yet for affected devices from your Windows device manufacturer (OEM).

ISSUE: Local Security Authority Protection is Off Error Message with Persistent Restart

Date: July 05, 2023

Details: After installing “Update for Microsoft Defender Antivirus antimalware platform – KB5007651 (Version 1.0.2302.21002)”, you might receive a security notification or warning stating that “Local Security protection is off. Your device may be vulnerable.” and once protections are enabled, your Windows device might persistently prompt that a restart is required. Important: This issue affects only “Update for Microsoft Defender Antivirus antimalware platform – KB5007651 (Version 1.0.2302.21002)”. All other Windows updates released on March 14, 2023 for affected platforms (KB5023706 and KB5023698), do not cause this issue.

Status: Resolved

Workaround or Fix: If you have enabled Local Security Authority (LSA) protection and have restarted your device at least once, you can dismiss warning notifications and ignore any additional notifications prompting for a restart. You can verify that LSA protection is enabled by looking in Event Viewer.

Resolution: This issue was resolved in an update for Windows Security platform antimalware platform KB5007651 (Version 1.0.2306.10002). If you would like to install the update before it is installed automatically, you will need to check for updates.

ISSUE: Microsoft Outlook and some apps might not open

Date: June 28, 2023

Details: After installing KB5027231 or later updates on Windows devices with certain antivirus, antimalware or security software installed, you might not be able to open Microsoft or third-party apps. Some known affected apps are Microsoft Outlook and other Microsoft Office apps. This issue only occurs with 32-bit apps running on 64-bit Windows with Trellix Endpoint Security version earlier than 35.31.25. When attempting to open an affected app, Event Log indicates an access violation with the error “module is unknown”. This issue is not likely to be encountered by consumers using Windows devices in their home.

Status: Resolved external

Resolution: This issue has been resolved by Trellix in Endpoint Security Agent (HX) 35.31.25 and later. If you are experiencing this issue with other security software installed or after installing the latest version of Trellix Endpoint Security Agent, please contact customer support of the security software you are using.

ISSUE: Start Menu, Windows Search and UWP Apps might have Issues Opening

Date: June 27, 2023

Details: The Start menu, Windows search, and Universal Windows Platform (UWP) apps might not work as expected or might have issues opening. Affected Windows devices might have damaged registry keys or data which might affect apps using Microsoft Office APIs to integrate with Windows, Microsoft Office, or Microsoft Outlook or Outlook Calendar. An example of an app affected by this issue is ClickShare. The underlying Issue is not caused by the installation of an update to Windows and might be exposed by an update to an affected app.

Status: Resolved

Workaround or Fix: To mitigate this issue, you can uninstall apps which integrate with Windows, Microsoft Office, Microsoft Outlook or Outlook Calendar. Updates to affected apps or guidance from the developer of the app might also be available.

Resolution: This issue was resolved in KB5027303.

ISSUE: Computing Effective Access might not Show Results

Date: June 27, 2023

Details: After installing updates released on May 9, 2023 or later updates, you might be unable to view Effective Access in the “Advanced Security Settings” dialog for shared files or folders. On affected devices, when the “View effective access” button is selected, you will receive the message “Computing effective access” but the results of the query might not be displayed and explorer.exe might continue to use CPU after the Advanced Security settings dialog is closed. This issue is unlikely to be experienced by consumers using Windows devices in their home.

Status: Resolved

Workaround or Fix: If you have attempted to view effective access, you can mitigate the CPU usage issue by restarting your device or by signing out for the affected user. Note: Locking Windows will not mitigate this issue, you must sign out.

Resolution: This issue has been addressed for devices running Windows 11, version 22H2 in updates released on June 27, 2023 (KB5027303) and later. This issue will be resolved on other affected Windows versions in updates that will be released in the near term.

ISSUE: Saving or Copying Files Might Intermittently Fail

Date: June 13, 2023

Details: You might have intermittent issues saving, or copying, or attaching files using 32-bit apps which are large address aware and using the CopyFile API. Windows devices are more likely to be affected by this issue when using some commercial/enterprise security software which uses extended file attributes. Microsoft is not receiving reports that copying files using File Explorer is affected, but CopyFile API used within apps might be affected. Microsoft Office apps such as Microsoft Word or Microsoft Excel are only affected when using 32-bit versions and you might receive the error, “Document not saved.” This issue is unlikely to be experienced by consumers using Windows devices in their home or on non-managed commercial device. Note: Apps are not affected by this issue if they are 64-bit or 32-bit and NOT large address aware.

Status: Resolved

Workaround or Fix: To mitigate the issue, you can attempt to save or copy again. Since the issue is intermittent, it is likely to succeed on a subsequent try.

Resolution: This issue was resolved in updates released June 13, 2023 (KB5027231) and later.

ISSUE: Domain Join Processes may Fail with Error 0xaac (2732)

Date: March 14, 2023

Details: Domain join operations might intentionally fail with error “0xaac (2732): NERR_AccountReuseBlockedByPolicy” and text “An account with the same name exists in Active Directory. Re-using the account was blocked by security policy.” This issue originates with the October 2022 security updates (KB5018427) which introduced some hardening changes enabled by default for domain join. Affected scenarios include some domain join or re-imaging operations where a computer account was created or pre-staged by a different identity than the identity used to join or re-join the computer to the domain. Home users of Windows are unlikely to experience this issue.

Status: Resolved

Resolution: This issue was resolved in updates released March 14, 2023 (KB5023706) or later. Please see KB5020276 to understand the newly re-designed behavior. Microsoft has added information about a new Allowlist policy for trusted computer account creators to this KB.

ISSUE: Intermittent Issues with Speech Recognition When Using Chinese or Japanese

Date: May 24, 2023

Details: After installing KB5022913 or later updates, some apps might have intermittent issues with speech recognition, expressive input, and handwriting when using Chinese or Japanese languages. Affected apps might sometimes fail to recognize certain words or might be unable to receive any input from speech recognition or affected input types. This issue is more likely to occur when apps are using offline speech recognition. Note for app developers: This issue only affects speech recognition using Speech Recognition Grammar Specification (SRGS) in Windows.Media.SpeechRecognition. Other implementations of speech recognition are not affected.

Status: Resolved

Workaround or Fix: To mitigate this issue, you will need to do the following once every time you restart your device:

• ​Close the app which is having issues.
• ​Open Task Manager, go to “Processes” tab, click on ctfrmon.exe and select the “End Task” button.
• ​Confirm a new instance of ctfmon.exe is started automatically.
• ​You should now be able to open the affected app and use speech recognition and other input types.

Resolution: This issue was resolved in KB5026446.

ISSUE: Third-party UI Customization Apps might Cause Windows to not Start Up

Date: March 17, 2023

Details: After installing KB5022913 or later updates, Windows devices with some third-party UI customization apps might not start up. These third-party apps might cause errors with explorer.exe that might repeat multiple times in a loop. The known affected third-party UI customization apps are ExplorerPatcher and StartAllBack. These types of apps often use unsupported methods to achieve their customization and as a result can have unintended results on your Windows device.

Status: Resolved external

Workaround or Fix: Microsoft recommends uninstalling any third-party UI customization app before installing KB5022913 to prevent this issue. If your Windows device is already experiencing this issue, you might need to contact customer support for the developer of the app you are using. If you are using StartAllBack, you might be able to prevent this issue by updating to the latest version (v3.5.6 or later).

Resolution: ExplorerPatcher has released a version which lists this issue as resolved. Note: If you are using any third-party UI customization app and encounter this or any other issues, you will need to contact customer support for the developer of the app you are using.

ISSUE: Connections may Fail When Using Remote Desktop Connection Brokers

Date: January 26, 2023

Details: After installing Windows 11, version 22H2, the Windows Remote Desktop application might stop responding when connecting via a Remote Desktop gateway or Remote Desktop Connection Broker. This issue can be observed when the client is at the “Loading virtual machine” or “Configuring remote connection” steps, and might occur regardless of the OS version installed on the remote computer. In some cases, the error message “Your Remote Desktop Services session has ended” can appear. If the application becomes unresponsive, it might need to be terminated using Windows Task Manager.

Status: Resolved

Workaround or Fix: If the Remote Desktop application becomes unresponsive, you can use Task Manager to terminate/end task the mstsc.exe process.

Devices that have encountered this issue can resolve it by configuring a special Group Policy. Open gpedit.msc, go to “Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Connection Client” and set “Turn Off UDP On Client” to Enabled. Restart your device to apply the policy setting.

Resolution: This issue was resolved in KB5022360.

ISSUE: Application Shortcuts might not Work from the Start Menu or Other Locations

Date: January 13, 2023

Details: After installing security intelligence update build 1.381.2140.0 for Microsoft Defender, application shortcuts in the Start menu, pinned to the taskbar, and on the Desktop might be missing or deleted. Additionally, errors might be observed when trying to run executable (.exe) files which have dependencies on shortcut files. Affected devices have the Attack Surface Reduction (ASR) rule “Block Win32 API calls from Office macro” enabled. After installing security intelligence build 1.381.2140.0, detections resulted in the deletion of certain Windows shortcut (.lnk) files that matched the incorrect detection pattern.

Status: Resolved

Workaround or Fix: Changes to Microsoft Defender can mitigate this issue. The Attack Surface Reduction (ASR) rules in Microsoft Defender are used to regulate software behavior as part of security measures. Changing ASR rules to Audit Mode can help prevent this issue. This can be done using Intune or group policy. Microsoft Office applications can be launched through the Microsoft 365 app launcher.

Resolution: This issue is resolved in security intelligence update build 1.381.2164.0. Installing security intelligence update build 1.381.2164.0 or later should prevent the issue, but it will not restore previously deleted shortcuts. You will need to recreate or restore these shortcuts through other methods.

ISSUE: Database Connections Using Microsoft ODBC SQL Server Driver might Fail

Date: January 10, 2023

Details: After installing KB5019980, apps which use ODBC connections utilizing the Microsoft ODBC SQL Server Driver (sqlsrv32.dll) to access databases might fail to connect. You might receive an error within the app or you might receive an error from SQL Server, such as “The EMS System encountered a problem” with “Message: [Microsoft][ODBC SQL Server Driver] Protocol error in TDS Stream” or “Message: [Microsoft][ODBC SQL Server Driver]Unknown token received from SQL Server”.

If you are unsure if you are using any affected apps, open any apps which use a database and then open Command Prompt and run following command:

tasklist /m sqlsrv32.dll

Status: Resolved

Workaround or Fix: To mitigate this issue, you can do one of the following:

• If your app is already using or able to use Data Source Name (DSN) to select ODBC connections, install Microsoft ODBC Driver 17 for SQL Server and select it for use with your app using DSN. Note: Microsoft recommends the latest version of Microsoft ODBC Driver 17 for SQL Server, as it is more compatible with apps currently using the legacy Microsoft ODBC SQL Server Driver (sqlsrv32.dll) than Microsoft ODBC Driver 18 for SQL Server.
• If your app is unable to use DSN, the app will need to be modified to allow for DSN or to use a newer ODBC driver than Microsoft ODBC SQL Server Driver (sqlsrv32.dll).

Resolution: This issue was resolved in KB5022303.

ISSUE: Provisioning Packages might not Work as Expected

Date: January 06, 2023

Details: Windows might only be partially configured, and the Out Of Box Experience might not finish or might restart unexpectedly. Provisioning packages are .PPKG files which are used to help configure new devices for use on business or school networks. Provisioning packages which are applied during initial setup are most likely to be impacted by this issue. Note: Provisioning Windows devices using Windows Autopilot is not affected by this issue. Windows devices used by consumers in their home or small offices are not likely to be affected by this issue.

Status: Resolved

Workaround or Fix: If you can provision the Windows device before upgrading to Windows 11, version 22H2, this will prevent the issue.

Resolution: This issue was resolved in KB5020044.

ISSUE: Task Manager might not Display in Expected Colors

Date: December 13, 2022

Details: After installing KB5020044, Task Manager might display certain elements in the user interface (UI) in unexpected colors. On affected devices, Task Manager should function as expected but some parts of the UI might not be readable. You might be affected by this issue if you have “Choose your mode” set to “Custom”, in the Personalization -> colors section of Settings. If you are using Dark or Light for the “Choose your mode” setting, you should not be affected by this issue.

Status: Resolved

Workaround or Fix: To mitigate this issue, you can set the “Choose your mode” setting to either Dark or Light until this issue is resolved. To do this, right click or long press on the desktop, select “Personalize”, select “Colors”, and then select either “Dark” or “Light” for “Choose your mode”.

Resolution: This issue was resolved in KB5021255.

ISSUE: Lower than Expected Performance in Some Games

Date: November 29, 2022

Details: 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 users upgrade experience, Microsoft has 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.

Status: Resolved

Workaround or Fix: 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.

Resolution: This issue was resolved in KB5020044. The safeguard hold is estimated to be removed in mid-December 2022.

ISSUE: Changing IME Input Modes might Cause Applications to Become Unresponsive

Date: November 29, 2022

Details: After installing Windows 11, version 22H2, certain applications may become unresponsive when keyboard shortcuts are used to turn on/off or change IME (Input Method Editor) input modes. It is possible this issue will occur silently, and not result in the display of any error messages. This issue is observed for applications which load certain components of the Text Services Framework (TSF). Only some applications do this, not all. Applications which don’t load these components should not experience this issue, and are expected to function normally when keyboard shortcuts are used.

Status: Resolved

Workaround or Fix: Changing input mode by clicking the IME mode icon in the taskbar should not trigger this issue. This issue occurs only when using keyboard shortcuts.

Resolution: This issue was resolved in updates released November 29, 2022 ( KB5020044) and later.

ISSUE: Some Installed Printers might Only Allow Default Settings

Date: November 18, 2022

Details: Your printer might be unable to use printer specific features such as color, two-sided/duplex printing, paper size or type settings, or resolutions higher than 300x300dpi.

It might happen if your printer was set up with default settings. When a Windows device is having connectivity issues to the printer and the user tries to install the printer, Windows installs the printer using default Microsoft IPP Class Driver or Universal Print Class Driver. Since Windows needs connectivity to the printer to identify all the features of the printer, without connectivity, the printer is set up with default settings. In some scenarios Windows might not update the printer driver once connectivity to the printer is restored.

Status: Resolved

Workaround or Fix: A troubleshooter has been released which will automatically download and resolve this issue on affected devices. Restarting your device and checking for updates might help the troubleshooter apply sooner.

To allow your Windows 11 device to upgrade to version 22H2, you can remove any printers installed using Microsoft IPP Class Driver or Universal Print Class Driver. Once you have removed any affected installed printers, you should be able to upgrade to Windows 11, version 22H2. It can take up to 48 hours before the upgrade to Windows 11 is offered to your device. You can also try to restart your device and then manually check for updates to immediately get 2022 Update.

Resolution: This issue was resolved, and the safeguard hold has been removed as of November 10, 2022.

ISSUE: Sign in Failures and Other Issues Related to Kerberos Authentication

Date: November 17, 2022

Details: 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”:

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.

Status: Resolved

Resolution: This issue was resolved in out-of-band updates released on November 17, 2022 for installation on all the Domain Controllers (DCs) in environment. You do not need to install any update or make any changes to other servers or client devices in your environment to resolve this issue.

ISSUE: Direct Access might be Unable to Reconnect After Your Device has Connectivity Issues

Date: November 13, 2022

Details: 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.

Status: Resolved

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>.

Group Policy downloads with Group Policy name:

• ​Download for Windows 11 22H2 – KB5018427 221029_091533 Known Issue Rollback
• ​Download for Windows 11 21H2 – KB5018483 220927_043051 Known Issue Rollback
• ​Download for Windows Server 2022 – KB5018485 220927_043049 Known Issue Rollback
• ​Download for Windows 10 – KB5018482 220927_043047 Known Issue Rollback

ISSUE: Audio might be Out of Sync when Capturing Video via Xbox Game Bar

Date: October 25, 2022

Details: The Xbox Game Bar app might have issues in which the audio is out of sync when capturing gameplay to a video file. You are more likely to encounter this issue when using the “Record last 30 seconds” feature when “Record in the background while I’m playing game” is enabled in Xbox Game Bar. Apps which capture or process video files using the same underlying Windows libraries or APIs as Xbox Game Bar might also be affected by this issue.

Status: Resolved

Resolution: This issue was resolved in KB5018496. The hotfix will not install automatically. To apply this update, you can check for updates and select the optional preview to download and install.

ISSUE: Possible Issues Caused by Daylight Savings Time Change in Jordan

Date: October 25, 2022

Details: On October 5, 2022, the Jordanian government made an official announcement ending the winter-time Daylight Saving Time (DST) time zone change. Due to this change, starting at 12:00 a.m. Friday, October 28, 2022, clocks will not be advanced by an hour for the Jordan time zone and the Jordan time zone will permanently shift to the UTC + 3 time zone.

Status: Resolved

Workaround or Fix: Select the Windows logo key, type “Date and time”, and select Date and time settings. From the Date & time settings page, toggle Adjust for daylight saving time automatically to Off. Alternatively, go to Control Panel > Clock and Region > Date and Time > Change time zone and uncheck the option for “Automatically adjust clock for Daylight Saving Time”.

Resolution: This issue was resolved in KB5018496. The hotfix will not install automatically. To apply this update, you can check for updates and select the optional preview to download and install.

ISSUE: SSL/TLS Handshake might Fail

Date: October 25, 2022

Details: After installing KB5018427 update, some types of SSL (Secure Sockets Layer) and TLS (Transport Layer Security) connections might have handshake failures. Affected connections are likely to be sending multiple frames within a single input buffer, specifically one or more complete records with a partial record that is less than 5 bytes all sent in a single buffer. When this issue is encountered, an app will receive SEC_E_ILLEGAL_MESSAGE when the connection fails.

Status: Resolved

Resolution: This issue was resolved in KB5018496. The hotfix will not install automatically. To apply this update, you can check for updates and select the optional preview to download and install.

ISSUE: Copying Files/Shortcuts Using Group Policy Preferences might not Work as Expected

Date: October 11, 2022

Details: If you copy files using Group Policy Preferences, it might fail or might create empty shortcuts or files using 0 (zero) bytes. Known affected Group Policy Objects are related to files and shortcuts in User Configuration -> Preferences -> Windows Settings section in Group Policy Editor (gpedit.msc).

Status: Resolved.

Workaround or Fix: To mitigate this issue, you can follow any of the following solutions:

• Uncheck the “Run in logged-on user’s security context” (user policy option). Note: This might not mitigate the issue for items using a wildcard (*).
• Within the affected Group Policy, change “Action” from “Replace” to “Update”.
• If a wildcard (*) is used in the location or destination, deleting the trailing “\” (backslash, without quotes) from the destination might allow the copy to be successful.

Resolution: This issue was resolved in KB5018427. Installation of the hotfix prevents and resolves this issue but if any workaround was used to mitigate this issue, it will need to be changed back to the original configuration.

ISSUE: Signing in Using Windows Hello might not Work after Upgrade

Date: September 30, 2022

Details: Signing in using Windows Hello might not work as expected after upgrading to Windows 11, version 22H2 on devices using Windows Hello Enhanced Sign-in Security. Windows Hello using face, fingerprint or PIN might be affected. This issue might be encountered on devices which already have Windows Hello when upgrading but should not happen on devices which enable Windows Hello after upgrading or installing Windows 11, version 22H2.

Status: Resolved.

Workaround or Fix: If you upgraded to Windows 11, version 22H2 and are unable to sign-in using Windows Hello, you can sign-in using the password for your user.

Resolution: This issue was resolved in KB5017389. The safeguard hold is estimated to be removed in mid-October 2022.

We’ll keep updating this page whenever a known issue is resolved or fixed. Keep checking this page regularly.

Also Check:

[FAQ] Installing Windows 11 on Unsupported Hardware Devices

[Tip] How to Download Windows 11 Offline ISO Files

How to Create Bootable USB Drive to Install Windows 11

[Tip] How to Complete Windows 11 Setup Without Internet Connection