

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.

Workaround: We recommend uninstalling any third-party UI customization app before installing KB5022913 to prevent this issue. These types of apps often use unsupported methods to achieve their customization and as a result can have unintended results on your Windows device. The known affected third-party UI customization apps are ExplorerPatcher and StartAllBack.

These third-party apps might cause errors with explorer.exe that might repeat multiple times in a loop. Third-party UI customization apps might cause Windows to not start upĪfter installing KB5022913 or later updates, Windows devices with some third-party UI customization apps might not start up. Client: Windows 11, version 22H2 Windows 11, version 21H2.Next steps: We are working on a resolution and will provide an update as soon as it is available. Important: Currently, we do not recommend any other workaround for this issue. You can verify that LSA protection is enabled by looking in Event Viewer using the information available here. Workaround: 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. All other Windows updates released on Mafor affected platforms ( KB5023706 and KB5023698), do not cause this issue. Important: This issue affects only "Update for Microsoft Defender Antivirus antimalware platform - KB5007651 (Version. Your device may be vulnerable." and once protections are enabled, your Windows device might persistently prompt that a restart is required. 21002)", you might receive a security notification or warning stating that "Local Security protection is off. "Local Security Authority protection is off." with persistent restartĪfter installing "Update for Microsoft Defender Antivirus antimalware platform - KB5007651 (Version.
