A recent update to Windows 11 24H2 has stirred a bit of confusion among users, as a piece of “under development” code appears to be causing disruptions with the Windows Firewall. This issue has emerged following the installation of the June 2025 Windows non-security preview update, leading to an error being logged in the Event Viewer for Windows Firewall With Advanced Security.
Details of the Disruption
According to Microsoft’s Release Health Dashboard, the error manifests as ‘Config Read Failed’ accompanied by the message ‘More data is available.’ Users may notice this event being logged every time their device restarts. However, Microsoft reassures that these entries do not indicate a genuine problem with the Windows Firewall and can be safely ignored.
The company has clarified that the underlying issue is tied to a feature still under development and not fully implemented. They have emphasized that the Windows Firewall is expected to operate normally, and there is no adverse effect on Windows processes related to this event. Nevertheless, the presence of erroneous logs can complicate the monitoring of device health, creating unnecessary headaches for users.
Inquiries made by The Register regarding further details about the enigmatic feature have yet to elicit a response from Microsoft. The situation raises eyebrows, particularly as it reflects poorly on the development process when an unfinished feature inadvertently finds its way into production code. One might wonder if this oversight could have been avoided through the Windows Insider program, designed to catch such issues before they reach the broader user base.
While it would be easy to expect a higher standard from Microsoft, the ongoing challenges associated with Windows 11 24H2 suggest that users may need to temper their expectations. Fortunately, this particular glitch does not appear to be causing significant disruptions, unlike some previous issues that have surfaced since the update’s initial rollout.
As for a timeline for resolution, Microsoft has not provided specifics but has indicated that they are actively working on a fix and will share updates in future releases.
