Microsoft has claimed fixes for two lingering Windows 11 version 24H2 issues; BSOD because of Easy Anti-Cheat stop and Windows Firewall logging issue. Coming to the BSOD issue, Microsoft has removed the safeguard hold on July 24, 2025. Therefore, eligible devices without other safeguard holds can install Windows 11, version 24H2 via Windows Update now.
Microsoft has mentioned that some devices might still display a warning indicating that an incompatible version of Easy Anti-Cheat is installed on the device and that it may be possible to update to it by launching and updating frequently played games. Since easy Anti-Cheat update availability depends on the game publisher, a confirmation will be required for proceeding with the Windows installation.
Microsoft is working with Easy Anti-Cheat on an incompatibility issue between Window 11, version 24H2 and the Easy Anti-Cheat application. This software is automatically installed with some games as part of security and cheat-prevention measures used in multiplayer online PC games. Only devices with Intel’s Alder Lake+ processors and vPro platform are affected. In rare cases, when users open or play certain games, this issue causes affected devices to stop responding and to show a blue screen with the error “MEMORY_MANAGEMENT”. Most devices experiencing this issue use Easy Anti-Cheat drivers released before April 2024.
To safeguard your update experience, we have applied a compatibility hold on devices running the incompatible Easy Anti-Cheat drivers. These devices will not be offered to install Windows 11, version 24H2 via the Windows Update release channel. IT administrators using Windows Update for Business reports can check this issue using its safeguard ID: 52325539.
If you are trying to install Windows 11, version 24H2 through the media creation tool and your device has incompatible drivers, you will receive a pop-up message alerting that your device is not ready for this new version of Windows.
Resolution: The safeguard hold has been removed as of July 24, 2025. Eligible devices without other safeguard holds can install Windows 11, version 24H2 via Windows Update. Some devices might display a warning indicating that an incompatible version of Easy Anti-Cheat is installed on the device and that it may be possible to update to it by launching and updating frequently-played games. Easy Anti-Cheat update availability depends on the game publisher. A confirmation will be requested in order to proceed with the Windows installation.
Please note that the issue described here is not expected to occur even if older versions of Easy Anti-Cheat are present on a device, unless they are launched as part of a game. Windows is not affected by the inactive presence of these older versions of Easy Anti-Cheat, if they are unused.
Coming to the Windows Firewall logging issue, Microsoft has claimed that the issue is resolved in the July 2025 Windows non-security update (KB5062660) and later updates. Funnily, Microsoft already claimed resolution for this update on July 8 and has now apologized for any inconvenience or confusion.
Following installation of the June 2025 Windows non-security preview update (KB5060829), security event logs might include an error event related to Windows Firewall With Advanced Security, which can be safely ignored.
The error is found in Event Viewer as event 2042 for Windows Firewall With Advanced Security. The event appears as “Config Read Failed” with message “More data is available”. Although this event is logged in Event Viewer every time the device is restarted, they do not reflect an issue with Windows Firewall, and can be disregarded.
Please note Windows Firewall is expected to function normally, and no action is required to prevent or resolve this error event. This event is related to a feature that is currently under development and not fully implemented. There is no impact to Windows processes associated to this event.
Resolution: This issue is resolved in the July 2025 Windows non-security update (KB5062660) and later updates. We recommend you install the latest update for your device as it contains important improvements and issue resolutions, including this one.
Note: This disclosure was mistakenly updated to Resolved status on July 8. The issue was resolved on July 22. We apologize for any inconvenience or confusion.
