Microsoft acknowledges that the Windows Firewall problem hasn't been fully fixed yet.

 
Microsoft announced last week that it has resolved a Windows Firewall bug that had been affecting Windows 11, version 24H2, since the non-security preview release in June. Some of our readers, however, pointed out that this is untrue because the issue persists on their installs. Microsoft has officially acknowledged that it made an inadvertent modification to its Windows Release Health dashboard.

According to Microsoft's dedicated warning for this Windows Firewall fault, on July 8, it unintentionally changed its disclosure to a resolved state even though the problem had not been repaired. It has therefore returned to the Confirmed status, although it has not yet given a specific timeframe. It still states that it is working on a patch that will be made available in a few weeks.

For those who haven't been actively following this issue, a lot of Windows 11 users started complaining that the operating system was activating Windows Firewall with Advanced Security after installing June's non-security preview update (KB5060829). Although Microsoft acknowledged this behavior, they reassured users that this error occurrence is not cause for concern because it is a false positive that is being inadvertently caused by a feature that is currently under development.

The company then confirmed that it had fixed the Windows Firewall issue and released Patch Tuesday updates for Windows 11 (KB5062553) on July 8. But as we now know, this revelation was unintentional. Therefore, every time a consumer restarts their device, they should still see the annoying error event recorded as Event 2042 in Event Viewer. The notice "More data is available" will appear alongside the Config Read Failed listing, but as previously, it can be disregarded. None of the operating system's processes are impacted by this error event.

Previous Post Next Post