Last week, Microsoft issued a public advisory noting that it has fixed a Windows Firewall issue that was plaguing Windows 11, version 24H2 since June"s non-security preview update. However, some of our readers pointed out that this is false since they are still seeing the problem on their installations. Microsoft has now admitted that it updated its Windows Release Health dashboard by accident.
In the dedicated advisory for this Windows Firewall bug, Microsoft has noted that it accidentally updated its disclosure to a Resolved status on July 8, despite the issue not actually being fixed. As such, it has reverted to the Confirmed status, while still saying that it is working on a fix that will be released in a few weeks, no concrete timeline has been provided just yet.
As a refresher for those who haven"t been actively following this thread: many Windows 11 customers began reporting that following the installation of June"s non-security preview update (KB5060829), they were seeing Windows Firewall with Advanced Security being triggered by the operating system. Microsoft confirmed this behavior but encouraged customers that this error event is nothing to worry about since it"s a false positive that is being mistakenly generated by an upcoming feature that is currently in development.
Then, on July 8, the company rolled out Patch Tuesday updates for Windows 11 (KB5062553), while also confirming that it has resolved the issue with Windows Firewall. However, as we have now learned, this disclosure was accidental. So, customers should still see the pesky error event being logged as Event 2042 in Event Viewer each time they restart their device. It will be listed as Config Read Failed with an additional message noting that "More data is available", but like before, it can be ignored. This error event does not impact any of the operating system"s processes.