Microsoft Windows Firewall complains about Microsoft code
Briefly

A preview update for Windows 11 24H2 has introduced a 'Config Read Failed' error in the Event Viewer related to Windows Firewall. This error occurs after the June 2025 non-security update and appears every time the device is restarted. Microsoft has clarified that despite the logged error, the Windows Firewall operates normally and there are no negative effects on Windows processes. The issue arises from a feature still under development, leading to potential confusion for users monitoring device health through the Event Log.
The event appears as 'Config Read Failed' with message 'More data is available.' Although this event is logged in Event Viewer every time the device is restarted, they do not reflect an issue with Windows Firewall, and can be disregarded.
The problem is related to a feature that is currently under development and not fully implemented. Microsoft stated that the Windows Firewall is expected to function normally.
The Event Log is also used to monitor the health of Windows devices, so spurious errors - even ones that can be ignored - will be a headache.
Confessing to leaving an in-development feature in production code is not a great look, particularly when it triggers errors in the Event Log.
Read at Theregister
[
|
]