Microsoft Apologizes After Mistakenly Claiming Windows 11 Update Fixed A Firewall Error
Quietly revises its documentation to clarify that the firewall issue was not resolved.
Windows 11 update was supposed to fix a firewall error – but instead introduced the issue to more users.
Microsoft has issued an apology following widespread confusion over a Windows 11 update that was supposed to fix a critical-looking but ultimately harmless firewall error – but instead introduced the issue to more users.
The problem centers on Windows 11 24H2 and a bug involving the Event Viewer, which logs a cryptic error titled "Windows Firewall With Advanced Security 2042 None."
This error, which reads "Config Read Failed: More data is available," first appeared in the June 2025 optional update (KB5060829), according to Windows Latest.
Microsoft initially acknowledged it and then claimed to have resolved the issue with the July 2025 Patch Tuesday update (KB5062553).
In its official release notes dated July 8, Microsoft stated: "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"".
However, the fix never took effect. Instead, the KB5062553 update introduced the bug to systems that hadn't experienced it previously, effectively widening the issue rather than resolving it.
"It kept showing up on my devices, and dozens of users told me they're still running into the same 'Windows Firewall With Advanced Security 2042 None' problem," Windows Latest reported.
After facing mounting feedback, Microsoft quietly revised its documentation to clarify that the firewall issue was not resolved, contrary to what was previously stated.
The company acknowledged the miscommunication and pledged a proper fix in an upcoming cumulative update.
"This disclosure was mistakenly updated to Resolved status on July 8," Microsoft wrote in the revised support document.
"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.”
2042 Firewall Error
Though the Event Viewer entry may appear alarming, the underlying bug is harmless. The error is triggered when the operating system attempts to read a firewall configuration and receives more data than expected.
The system then logs Event ID 2042 as a warning but successfully rereads the data and continues normal operation. In essence, this is a logging glitch, not a functional failure of the firewall.
The issue has been traced back to backend code changes introduced as part of Microsoft's ongoing work to expand firewall functionality.
Other Windows Problems Surface in July Updates
In addition to the firewall issue, Windows Latest has flagged problems stemming from other updates rolled out this month.
The July 2025 cumulative update for Windows 10 (KB5062554) has partially broken the emoji picker tool.
"Whenever you try searching for something, the feature doesn't execute it," the report said. "After clicking on the search icon in the emoji picker, we straight up saw the 'We couldn't find this one' message in the dialog box."
While the emoji panel still launches, its search function is effectively non-functional after the update – a minor but noticeable inconvenience for many users.
Two further issues in Windows 10 have drawn user complaints.
Microsoft's parental control tool, which restricts access to specific web browsers, now only allows approvals for Microsoft Edge. In the past, parents could approve other popular browsers like Chrome or Firefox. The limitation arises because Microsoft has not yet updated its internal browser version block list to reflect recent releases, rendering parental controls ineffective with those newer versions.
Additionally, users of the ChangJie IME (used for typing traditional Chinese characters) have reported that keys have become unresponsive and input functionality has degraded significantly. The bug has been linked to recent updates, and Microsoft has provided a workaround – restoring a previous version of the ChangJie IME – via its official Windows Health Dashboard.
This article originally appeared on our sister site Computing.