Microsoft rolls back Windows 10 update KB5005101 using Known Issue Rollback for resolving multiple issues

Microsoft has acknowledged multiple issues caused by Windows 10 update KB5005101. On Windows 10 devices using Microsoft Exploit Protection Export Address Filtering (EAF), the update may have been resulting in issues like “apps failing to open, failing to open files, or receiving a white window when attempting to login.

Microsoft has also claimed to resolve the issues by using “Known Issue Rollback (KIR)”. It has also mentioned that it may take up to 24 hours for the resolution to propagate automatically to consumer devices and non-managed business devices. Read all the details below.

Apps might fail to open, close unexpectedly or become unresponsive
Status	Originating update	History
Resolved	OS Build 19043.1202 KB5005101 2021-09-01	Resolved: 2021-09-24, 11:22 PT Opened: 2021-09-24, 11:00 PT
After installing KB5005101 or a later update on devices using Microsoft Exploit Protection Export Address Filtering (EAF), you might have issues with some applications. You might be experiencing this issue if apps fail to open, fail to open files, or you might receive a white window when attempting to login. Affected platforms: Client: Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 2004; Windows 10, version 1909; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019 Server: Windows Server 2022; Windows Server, version 20H2; Windows Server, version 2004; Windows Server, version 1909; Windows Server, version 1809; Windows Server 2019 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, it can be resolved by installing and configuring a special Group Policy (preferred) or setting a registry key according to the version of Windows you are using. Important Verify that you are using the correct Group Policy or registry key for your version of Windows. Group Policy (preferred): Windows Sever 2022 Windows 10, version 2004, Windows 10, version 20H2 and Windows 10, version 21H1 Windows 10, version 1909 Windows 10, version 1809, Windows Server 2019 For help, please see How to use Group Policy to deploy a Known Issue Rollback. For general information on using Group Policies, see Group Policy Overview. Registry Key: Open a Command Prompt window (cmd.exe) with elevated permissions. Type the following command depending on which Windows version you are using and then press Enter. Windows Sever 2022: reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides /v 2801335948 /t REG_DWORD /d 0 /f Windows 10, version 2004, Windows 10, version 20H2 and Windows 10, version 21H1: reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides /v 2767781516 /t REG_DWORD /d 0 /f Windows 10, version 1909: reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides /v 928713355 /t REG_DWORD /d 0 /f Windows 10, version 1809, Windows Server 2019: reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides /v 2371422858 /t REG_DWORD /d 0 /f Note Devices need to be restarted after configuring the special Group Policy or adding the registry key.