Microsoft Mislabels Windows Firewall Bug as Fixed
▼ Summary
– Microsoft mistakenly marked a Windows Firewall error message bug as fixed in recent updates but later admitted it remains unresolved.
– The bug causes Event ID 2042 errors in Windows Firewall With Advanced Security, appearing as “Config Read Failed” upon restart.
– Microsoft clarified these errors are harmless and can be ignored, as they stem from an upcoming feature not yet fully implemented.
– The company incorrectly labeled the issue as resolved in July Patch Tuesday updates and later apologized for the error.
– A fix for the bug is in development and will be released in an upcoming update.
Microsoft has incorrectly listed a Windows Firewall bug as resolved in recent updates, despite ongoing investigations into the issue. The company later acknowledged the error, clarifying that a proper fix remains in development and will arrive in a future release.
Earlier this month, Microsoft alerted users that Windows 11 preview builds from June 2025 onward would display misleading firewall error messages in Event Viewer. These entries, identified as Event ID 2042, appear each time the system reboots. The logs indicate a “Config Read Failed” status with the message “More data is available,” though Microsoft insists these warnings do not indicate an actual firewall malfunction.
According to Microsoft, the errors stem from an incomplete feature implementation rather than a security vulnerability or operational flaw. Users can safely ignore the notifications until an official patch arrives.
During July’s Patch Tuesday rollout, the company mistakenly marked the issue as resolved in its update documentation. Shortly after, Microsoft corrected the record, admitting the premature classification was an error. “The status was incorrectly updated to ‘Resolved’ on July 8,” the company stated. “A fix is still in progress and will be delivered in an upcoming update. We apologize for any confusion this may have caused.”
No workaround currently exists, but Microsoft confirms the bug poses no immediate risk to system security or firewall functionality. The final resolution is expected within weeks.
(Source: BLEEPING COMPUTER)
