Microsoft Windows Firewall complains about Microsoft code

A mysterious piece of “under development” code is playing havoc with the Windows Firewall after the latest preview update for Windows 11 24H2.

The problem manifests as an error in the Event Viewer for Windows Firewall With Advanced Security and can occur following the installation of the June 2025 Windows non-security preview update.

In the latest entry in Windows 11 24H2’s hall of shame – aka Microsoft’s Release Health Dashboard – the company explained: “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.”

So, there you go. Something in the update has upset the Windows Firewall, but users should ignore it and continue with their day.

The problem is “related to a feature that is currently under development and not fully implemented,” according to Microsoft. It also stated that the Windows Firewall “is expected to function normally,” which is reassuring, and “there is no impact to Windows processes associated to [sic] this event.”

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.

The Register asked Microsoft for more details about the mystery feature in question, but the company has yet to respond.

Confessing to leaving an in-development feature in production code is not a great look, particularly when it triggers errors in the Event Log. Isn’t that what the Windows Insider program is for?

That said, let the programmer who has never left a bit of work-in-progress code in an app that can, in theory, never be accessed by end users cast the first stone.

We’d like to say that we expect better from Microsoft, but judging by the cavalcade of problems that have cropped up with Windows 11 24H2 since it first seeped under the Redmond build lab’s door, we’re relieved that at least this one doesn’t seem to be crashing anything.

Microsoft did not provide an estimated timeframe for when the issue will be resolved. It said, “We are working on a resolution and will provide an update in an upcoming release.” ®

READ MORE HERE