Windows 11 July 2025 update issues confirmed, Microsoft says it falsely claimed fixes

In the latest developments surrounding Windows 11 24H2, users have encountered a persistent issue flagged by the Event Viewer, indicating a critical Firewall error labeled as “Windows Firewall With Advanced Security 2042 None.” This error, while alarming in its presentation, is ultimately a false alarm—harmless and ignorable. However, Microsoft’s initial assertion that this issue was resolved in the July 2025 Update (KB5062553) has proven to be misleading, as the update inadvertently propagated the error rather than rectifying it.

The origins of this confusion trace back to the June 2025 optional update (KB5060829), where the Firewall error first emerged. When Microsoft subsequently released KB5062553, the company confidently stated in their release notes that the issue had been “fully” addressed. A cached version of those notes reveals a clear misrepresentation: “This update addresses an issue found in Event Viewer as Event 2042 for Windows Firewall with Advanced Security. The event appears as ‘Config Read Failed’ with the message ‘More data is available.’” This claim, now recognized as erroneous, has left many users, including myself, still grappling with the same Firewall error.

In a recent update to their documentation, Microsoft has acknowledged the oversight and expressed regret for the confusion caused. They have assured users that a resolution for the Windows Firewall errors is on the horizon, slated for inclusion in an upcoming cumulative update. The company noted, “This disclosure was mistakenly updated to Resolved status on July 8. A resolution for this issue is planned to be included in an update to be released in the coming weeks. We apologize for any inconvenience or confusion.”

What is the Windows Firewall error, and why can you safely ignore it?

The Windows Firewall error, as displayed in the Event Viewer, is titled “Windows Firewall With Advanced Security 2042 None.” It is crucial to understand that this error is benign, allowing users to disregard it without concern for their system’s integrity. The error arises when the operating system anticipates a specific amount of information but receives an excess that exceeds its initial reading capacity. Consequently, the firewall logs Event ID 2042 with a “Config Read Failed” message, even though the service promptly rereads the data and continues to function normally.

Microsoft has confirmed that this warning stems from a coding bug introduced with recent updates to Windows 11 24H2. Importantly, this glitch affects only the event log entry and does not compromise the firewall’s performance. Reports suggest that Microsoft is currently testing a new feature for the Firewall, which, while not yet ready for deployment, inadvertently contributed to the emergence of these erroneous logs in the Event Viewer.

Additionally, it is worth noting that the July update, KB5062553, has been associated with various other issues, including installation problems, which may also be addressed in the forthcoming cumulative update.

Winsage
Windows 11 July 2025 update issues confirmed, Microsoft says it falsely claimed fixes