Microsoft Windows Server | WI287244

Impact: Devices using Microsoft Exploit Protection Export Address Filtering (EAF) might have issues with some apps. Originating KB URL: https://support.microsoft.com/en-us/topic/5005102 Originating KB Release Date: 2021-08-26T10:00:00-07:00 Originating Build: 17763.2145 Resolved KB URL: https://support.microsoft.com/en-us/topic/5006672 Date Resolved: 2021-10-12T10:00:00-07:00 Vendor Message History: ======================= Published: 2023-01-19T02:36:34.22+00:00 ---------------------------------------- After installing KB5005102 (https://support.microsoft.com/help/5005102) 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 was resolved in KB5006672 (https://support.microsoft.com/help/5006672), released October 12, 2021. If you are using an update released before October 12, 2021, you can resolve this issue using Known Issue Rollback (KIR) (https://techcommunity.microsoft.com/t5/windows-it-pro-blog/known-issue-rollback-helping-you-keep-windows-devices-protected/ba-p/2176831). 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 (https://download.microsoft.com/download/7/f/1/7f194890-eea9-4cad-b19f-25ab67e41bbe/Windows%20Server%202022%20Known%20Issue%20Rollback%20091821%2001.msi) - Windows 10, version 2004, Windows 10, version 20H2 and Windows 10, version 21H1 (https://download.microsoft.com/download/7/f/1/7f194890-eea9-4cad-b19f-25ab67e41bbe/Windows%2010%20(2004%20,%2020H2%20and%2021H1)%20Known%20Issue%20Rollback%20091721%2001.msi) - Windows 10, version 1909 (https://download.microsoft.com/download/7/f/1/7f194890-eea9-4cad-b19f-25ab67e41bbe/Windows%2010%20(1903%20&%201909)%20Known%20Issue%20Rollback%20091721%2001.msi) - Windows 10, version 1809, Windows Server 2019 (https://download.microsoft.com/download/7/f/1/7f194890-eea9-4cad-b19f-25ab67e41bbe/Windows%2010%20(1809)%20&%20Windows%20Server%202019%20Known%20Issue%20Rollback%20091821%2001.msi) For help, please see How to use Group Policy to deploy a Known Issue Rollback (https://docs.microsoft.com/troubleshoot/windows-client/group-policy/use-group-policy-to-deploy-known-issue-rollback). For general information on using Group Policies, see Group Policy Overview (https://docs.microsoft.com/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/hh831791(v=ws.11)). Note Devices need to be restarted after configuring the special Group Policy or adding the registry key. Registry Key: 1, Open a Command Prompt window (cmd.exe) with elevated permissions. 2, 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 3, All version of Windows require a restart of the device for the registry key to take effect. Before restarting Windows 10, version 1909, Windows 10, version 1809 and Windows Server 2019, you will need to also run following command from elevated PowerShell prompt: Get-ScheduledTask -TaskName "ReconcileFeatures" | Start-ScheduledTask Published: 2023-01-15T01:09:48.663+00:00 ---------------------------------------- After installing KB5005102 (https://support.microsoft.com/help/5005102) 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 was resolved in KB5006672 (https://support.microsoft.com/help/5006672), released October 12, 2021. If you are using an update released before October 12, 2021, you can resolve this issue using Known Issue Rollback (KIR) (https://techcommunity.microsoft.com/t5/windows-it-pro-blog/known-issue-rollback-helping-you-keep-windows-devices-protected/ba-p/2176831). 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 (https://download.microsoft.com/download/7/f/1/7f194890-eea9-4cad-b19f-25ab67e41bbe/Windows%20Server%202022%20Known%20Issue%20Rollback%20091821%2001.msi) - Windows 10, version 2004, Windows 10, version 20H2 and Windows 10, version 21H1 (https://download.microsoft.com/download/7/f/1/7f194890-eea9-4cad-b19f-25ab67e41bbe/Windows%2010%20(2004%20,%2020H2%20and%2021H1)%20Known%20Issue%20Rollback%20091721%2001.msi) - Windows 10, version 1909 (https://download.microsoft.com/download/7/f/1/7f194890-eea9-4cad-b19f-25ab67e41bbe/Windows%2010%20(1903%20&%201909)%20Known%20Issue%20Rollback%20091721%2001.msi) - Windows 10, version 1809, Windows Server 2019 (https://download.microsoft.com/download/7/f/1/7f194890-eea9-4cad-b19f-25ab67e41bbe/Windows%2010%20(1809)%20&%20Windows%20Server%202019%20Known%20Issue%20Rollback%20091821%2001.msi) For help, please see How to use Group Policy to deploy a Known Issue Rollback (https://docs.microsoft.com/troubleshoot/windows-client/group-policy/use-group-policy-to-deploy-known-issue-rollback). For general information on using Group Policies, see Group Policy Overview (https://docs.microsoft.com/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/hh831791(v=ws.11)). Note Devices need to be restarted after configuring the special Group Policy or adding the registry key. Registry Key: 1, Open a Command Prompt window (cmd.exe) with elevated permissions. 2, 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 3, All version of Windows require a restart of the device for the registry key to take effect. Before restarting Windows 10, version 1909, Windows 10, version 1809 and Windows Server 2019, you will need to also run following command from elevated PowerShell prompt: Get-ScheduledTask -TaskName "ReconcileFeatures" | Start-ScheduledTask Published: 2023-01-13T23:42:54.827+00:00 ---------------------------------------- After installing KB5005102 (https://support.microsoft.com/help/5005102) 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 was resolved in KB5006672 (https://support.microsoft.com/help/5006672), released October 12, 2021. If you are using an update released before October 12, 2021, you can resolve this issue using Known Issue Rollback (KIR) (https://techcommunity.microsoft.com/t5/windows-it-pro-blog/known-issue-rollback-helping-you-keep-windows-devices-protected/ba-p/2176831). 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 (https://download.microsoft.com/download/7/f/1/7f194890-eea9-4cad-b19f-25ab67e41bbe/Windows%20Server%202022%20Known%20Issue%20Rollback%20091821%2001.msi) - Windows 10, version 2004, Windows 10, version 20H2 and Windows 10, version 21H1 (https://download.microsoft.com/download/7/f/1/7f194890-eea9-4cad-b19f-25ab67e41bbe/Windows%2010%20(2004%20,%2020H2%20and%2021H1)%20Known%20Issue%20Rollback%20091721%2001.msi) - Windows 10, version 1909 (https://download.microsoft.com/download/7/f/1/7f194890-eea9-4cad-b19f-25ab67e41bbe/Windows%2010%20(1903%20&%201909)%20Known%20Issue%20Rollback%20091721%2001.msi) - Windows 10, version 1809, Windows Server 2019 (https://download.microsoft.com/download/7/f/1/7f194890-eea9-4cad-b19f-25ab67e41bbe/Windows%2010%20(1809)%20&%20Windows%20Server%202019%20Known%20Issue%20Rollback%20091821%2001.msi) For help, please see How to use Group Policy to deploy a Known Issue Rollback (https://docs.microsoft.com/troubleshoot/windows-client/group-policy/use-group-policy-to-deploy-known-issue-rollback). For general information on using Group Policies, see Group Policy Overview (https://docs.microsoft.com/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/hh831791(v=ws.11)). Note Devices need to be restarted after configuring the special Group Policy or adding the registry key. Registry Key: 1, Open a Command Prompt window (cmd.exe) with elevated permissions. 2, 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 3, All version of Windows require a restart of the device for the registry key to take effect. Before restarting Windows 10, version 1909, Windows 10, version 1809 and Windows Server 2019, you will need to also run following command from elevated PowerShell prompt: Get-ScheduledTask -TaskName "ReconcileFeatures" | Start-ScheduledTask Published: 2023-01-13T23:39:45.75+00:00 ---------------------------------------- After installing KB5005102 (https://support.microsoft.com/help/5005102) 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 was resolved in KB5006672 (https://support.microsoft.com/help/5006672), released October 12, 2021. If you are using an update released before October 12, 2021, you can resolve this issue using Known Issue Rollback (KIR) (https://techcommunity.microsoft.com/t5/windows-it-pro-blog/known-issue-rollback-helping-you-keep-windows-devices-protected/ba-p/2176831). 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 (https://download.microsoft.com/download/7/f/1/7f194890-eea9-4cad-b19f-25ab67e41bbe/Windows%20Server%202022%20Known%20Issue%20Rollback%20091821%2001.msi) - Windows 10, version 2004, Windows 10, version 20H2 and Windows 10, version 21H1 (https://download.microsoft.com/download/7/f/1/7f194890-eea9-4cad-b19f-25ab67e41bbe/Windows%2010%20(2004%20,%2020H2%20and%2021H1)%20Known%20Issue%20Rollback%20091721%2001.msi) - Windows 10, version 1909 (https://download.microsoft.com/download/7/f/1/7f194890-eea9-4cad-b19f-25ab67e41bbe/Windows%2010%20(1903%20&%201909)%20Known%20Issue%20Rollback%20091721%2001.msi) - Windows 10, version 1809, Windows Server 2019 (https://download.microsoft.com/download/7/f/1/7f194890-eea9-4cad-b19f-25ab67e41bbe/Windows%2010%20(1809)%20&%20Windows%20Server%202019%20Known%20Issue%20Rollback%20091821%2001.msi) For help, please see How to use Group Policy to deploy a Known Issue Rollback (https://docs.microsoft.com/troubleshoot/windows-client/group-policy/use-group-policy-to-deploy-known-issue-rollback). For general information on using Group Policies, see Group Policy Overview (https://docs.microsoft.com/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/hh831791(v=ws.11)). Note Devices need to be restarted after configuring the special Group Policy or adding the registry key. Registry Key: 1, Open a Command Prompt window (cmd.exe) with elevated permissions. 2, 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 3, All version of Windows require a restart of the device for the registry key to take effect. Before restarting Windows 10, version 1909, Windows 10, version 1809 and Windows Server 2019, you will need to also run following command from elevated PowerShell prompt: Get-ScheduledTask -TaskName "ReconcileFeatures" | Start-ScheduledTask Published: 2023-01-13T23:36:25.743+00:00 ---------------------------------------- After installing KB5005102 (https://support.microsoft.com/help/5005102) 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 was resolved in KB5006672 (https://support.microsoft.com/help/5006672), released October 12, 2021. If you are using an update released before October 12, 2021, you can resolve this issue using Known Issue Rollback (KIR) (https://techcommunity.microsoft.com/t5/windows-it-pro-blog/known-issue-rollback-helping-you-keep-windows-devices-protected/ba-p/2176831). 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 (https://download.microsoft.com/download/7/f/1/7f194890-eea9-4cad-b19f-25ab67e41bbe/Windows%20Server%202022%20Known%20Issue%20Rollback%20091821%2001.msi) - Windows 10, version 2004, Windows 10, version 20H2 and Windows 10, version 21H1 (https://download.microsoft.com/download/7/f/1/7f194890-eea9-4cad-b19f-25ab67e41bbe/Windows%2010%20(2004%20,%2020H2%20and%2021H1)%20Known%20Issue%20Rollback%20091721%2001.msi) - Windows 10, version 1909 (https://download.microsoft.com/download/7/f/1/7f194890-eea9-4cad-b19f-25ab67e41bbe/Windows%2010%20(1903%20&%201909)%20Known%20Issue%20Rollback%20091721%2001.msi) - Windows 10, version 1809, Windows Server 2019 (https://download.microsoft.com/download/7/f/1/7f194890-eea9-4cad-b19f-25ab67e41bbe/Windows%2010%20(1809)%20&%20Windows%20Server%202019%20Known%20Issue%20Rollback%20091821%2001.msi) For help, please see How to use Group Policy to deploy a Known Issue Rollback (https://docs.microsoft.com/troubleshoot/windows-client/group-policy/use-group-policy-to-deploy-known-issue-rollback). For general information on using Group Policies, see Group Policy Overview (https://docs.microsoft.com/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/hh831791(v=ws.11)). Note Devices need to be restarted after configuring the special Group Policy or adding the registry key. Registry Key: 1, Open a Command Prompt window (cmd.exe) with elevated permissions. 2, 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 3, All version of Windows require a restart of the device for the registry key to take effect. Before restarting Windows 10, version 1909, Windows 10, version 1809 and Windows Server 2019, you will need to also run following command from elevated PowerShell prompt: Get-ScheduledTask -TaskName "ReconcileFeatures" | Start-ScheduledTask Published: 2021-10-15T00:34:00.653+00:00 ---------------------------------------- After installing KB5005102 (https://support.microsoft.com/help/5005102) 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 was resolved in KB5006672 (https://support.microsoft.com/help/5006672), released October 12, 2021. If you install an update released October 12, 2021 (KB5006672 (https://support.microsoft.com/help/5006672)) or later, you do not need to use a Known Issue Rollback (KIR) (https://techcommunity.microsoft.com/t5/windows-it-pro-blog/known-issue-rollback-helping-you-keep-windows-devices-protected/ba-p/2176831) or a special Group Policy to resolve this issue. If you are using an update released before October 12, 2021, you can resolve this issue using KIR. 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 (https://download.microsoft.com/download/7/f/1/7f194890-eea9-4cad-b19f-25ab67e41bbe/Windows%20Server%202022%20Known%20Issue%20Rollback%20091821%2001.msi) - Windows 10, version 2004, Windows 10, version 20H2 and Windows 10, version 21H1 (https://download.microsoft.com/download/7/f/1/7f194890-eea9-4cad-b19f-25ab67e41bbe/Windows%2010%20(2004%20,%2020H2%20and%2021H1)%20Known%20Issue%20Rollback%20091721%2001.msi) - Windows 10, version 1909 (https://download.microsoft.com/download/7/f/1/7f194890-eea9-4cad-b19f-25ab67e41bbe/Windows%2010%20(1903%20&%201909)%20Known%20Issue%20Rollback%20091721%2001.msi) - Windows 10, version 1809, Windows Server 2019 (https://download.microsoft.com/download/7/f/1/7f194890-eea9-4cad-b19f-25ab67e41bbe/Windows%2010%20(1809)%20&%20Windows%20Server%202019%20Known%20Issue%20Rollback%20091821%2001.msi) For help, please see How to use Group Policy to deploy a Known Issue Rollback (https://docs.microsoft.com/troubleshoot/windows-client/group-policy/use-group-policy-to-deploy-known-issue-rollback). For general information on using Group Policies, see Group Policy Overview (https://docs.microsoft.com/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/hh831791(v=ws.11)). Note Devices need to be restarted after configuring the special Group Policy or adding the registry key. Registry Key: 1, Open a Command Prompt window (cmd.exe) with elevated permissions. 2, 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 3, All version of Windows require a restart of the device for the registry key to take effect. Before restarting Windows 10, version 1909, Windows 10, version 1809 and Windows Server 2019, you will need to also run following command from elevated PowerShell prompt: Get-ScheduledTask -TaskName "ReconcileFeatures" | Start-ScheduledTask Published: 2021-10-02T00:16:58.703+00:00 ---------------------------------------- After installing KB5005102 (https://support.microsoft.com/help/5005102) 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) (https://techcommunity.microsoft.com/t5/windows-it-pro-blog/known-issue-rollback-helping-you-keep-windows-devices-protected/ba-p/2176831). 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 (https://download.microsoft.com/download/7/f/1/7f194890-eea9-4cad-b19f-25ab67e41bbe/Windows%20Server%202022%20Known%20Issue%20Rollback%20091821%2001.msi) - Windows 10, version 2004, Windows 10, version 20H2 and Windows 10, version 21H1 (https://download.microsoft.com/download/7/f/1/7f194890-eea9-4cad-b19f-25ab67e41bbe/Windows%2010%20(2004%20,%2020H2%20and%2021H1)%20Known%20Issue%20Rollback%20091721%2001.msi) - Windows 10, version 1909 (https://download.microsoft.com/download/7/f/1/7f194890-eea9-4cad-b19f-25ab67e41bbe/Windows%2010%20(1903%20&%201909)%20Known%20Issue%20Rollback%20091721%2001.msi) - Windows 10, version 1809, Windows Server 2019 (https://download.microsoft.com/download/7/f/1/7f194890-eea9-4cad-b19f-25ab67e41bbe/Windows%2010%20(1809)%20&%20Windows%20Server%202019%20Known%20Issue%20Rollback%20091821%2001.msi) For help, please see How to use Group Policy to deploy a Known Issue Rollback (https://docs.microsoft.com/troubleshoot/windows-client/group-policy/use-group-policy-to-deploy-known-issue-rollback). For general information on using Group Policies, see Group Policy Overview (https://docs.microsoft.com/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/hh831791(v=ws.11)). Note Devices need to be restarted after configuring the special Group Policy or adding the registry key. Registry Key: 1, Open a Command Prompt window (cmd.exe) with elevated permissions. 2, 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 3, All version of Windows require a restart of the device for the registry key to take effect. Before restarting Windows 10, version 1909, Windows 10, version 1809 and Windows Server 2019, you will need to also run following command from elevated PowerShell prompt: Get-ScheduledTask -TaskName "ReconcileFeatures" | Start-ScheduledTask Published: 2021-09-29T21:32:14.393+00:00 ---------------------------------------- After installing KB5005102 (https://support.microsoft.com/help/5005102) 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) (https://techcommunity.microsoft.com/t5/windows-it-pro-blog/known-issue-rollback-helping-you-keep-windows-devices-protected/ba-p/2176831). 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 (https://download.microsoft.com/download/7/f/1/7f194890-eea9-4cad-b19f-25ab67e41bbe/Windows%20Server%202022%20Known%20Issue%20Rollback%20091821%2001.msi) - Windows 10, version 2004, Windows 10, version 20H2 and Windows 10, version 21H1 (https://download.microsoft.com/download/7/f/1/7f194890-eea9-4cad-b19f-25ab67e41bbe/Windows%2010%20(2004%20,%2020H2%20and%2021H1)%20Known%20Issue%20Rollback%20091721%2001.msi) - Windows 10, version 1909 (https://download.microsoft.com/download/7/f/1/7f194890-eea9-4cad-b19f-25ab67e41bbe/Windows%2010%20(1903%20&%201909)%20Known%20Issue%20Rollback%20091721%2001.msi) - Windows 10, version 1809, Windows Server 2019 (https://download.microsoft.com/download/7/f/1/7f194890-eea9-4cad-b19f-25ab67e41bbe/Windows%2010%20(1809)%20&%20Windows%20Server%202019%20Known%20Issue%20Rollback%20091821%2001.msi) For help, please see How to use Group Policy to deploy a Known Issue Rollback (https://docs.microsoft.com/troubleshoot/windows-client/group-policy/use-group-policy-to-deploy-known-issue-rollback). For general information on using Group Policies, see Group Policy Overview (https://docs.microsoft.com/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/hh831791(v=ws.11)). Note Devices need to be restarted after configuring the special Group Policy or adding the registry key. Registry Key: 1, Open a Command Prompt window (cmd.exe) with elevated permissions. 2, 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 3, All version of Windows require a restart of the device for the registry key to take effect. Before restarting Windows 10, version 1909, Windows 10, version 1809 and Windows Server 2019, you will need to also run following command from elevated PowerShell prompt: Get-ScheduledTask -TaskName "ReconcileFeatures" | Start-ScheduledTask Published: 2021-09-24T18:03:17.017+00:00 ---------------------------------------- After installing KB5005102 (https://support.microsoft.com/help/5005102) 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) (https://techcommunity.microsoft.com/t5/windows-it-pro-blog/known-issue-rollback-helping-you-keep-windows-devices-protected/ba-p/2176831). 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 (https://download.microsoft.com/download/7/f/1/7f194890-eea9-4cad-b19f-25ab67e41bbe/Windows%20Server%202022%20Known%20Issue%20Rollback%20091821%2001.msi) - Windows 10, version 2004, Windows 10, version 20H2 and Windows 10, version 21H1 (https://download.microsoft.com/download/7/f/1/7f194890-eea9-4cad-b19f-25ab67e41bbe/Windows%2010%20(2004%20,%2020H2%20and%2021H1)%20Known%20Issue%20Rollback%20091721%2001.msi) - Windows 10, version 1909 (https://download.microsoft.com/download/7/f/1/7f194890-eea9-4cad-b19f-25ab67e41bbe/Windows%2010%20(1903%20&%201909)%20Known%20Issue%20Rollback%20091721%2001.msi) - Windows 10, version 1809, Windows Server 2019 (https://download.microsoft.com/download/7/f/1/7f194890-eea9-4cad-b19f-25ab67e41bbe/Windows%2010%20(1809)%20&%20Windows%20Server%202019%20Known%20Issue%20Rollback%20091821%2001.msi) For help, please see How to use Group Policy to deploy a Known Issue Rollback (https://docs.microsoft.com/troubleshoot/windows-client/group-policy/use-group-policy-to-deploy-known-issue-rollback). For general information on using Group Policies, see Group Policy Overview (https://docs.microsoft.com/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/hh831791(v=ws.11)). Registry Key: 1. Open a Command Prompt window (cmd.exe) with elevated permissions. 2. 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.