Firewall errors? Present. Explanations? Absent. Microsoft, true to tradition, suggests “not to worry.”
What else does Windows 11 have in store for us?
What else does Windows 11 have in store for us?
Windows 11 users have once again encountered an unpleasant surprise following the installation of the June preview update version 24H2. This time, the issue stems from Windows Firewall — the built-in firewall has begun consistently logging errors, leaving behind alarming traces in the system log.
The incident affects exactly the build that Microsoft is currently distributing as part of the unprotected updates. This refers to the version preceding the official 24H2 release update for Windows 11, which is expected later this year.
After installing the update, users began noticing messages in the Event Viewer indicating firewall configuration failures. The system log displays a notification titled “Config Read Failed,” accompanied by the comment “More data is available.” This message appears every time the computer restarts.
What’s especially concerning is that this notification is tied to the Windows Firewall With Advanced Security section — a sensitive part of the system that many users and specialists monitor closely.
However, according to Microsoft, this is no cause for panic. In the official Release Health Dashboard, where the company tracks and comments on known Windows issues, Microsoft states that the logged error does not affect the actual functioning of the firewall.
The corporation assures users that despite the alarming entries, the firewall continues to operate normally. The errors in the log can be safely ignored — at least until the next fix is released.
Later, Microsoft clarified that the source of the issue lies in a feature still under development that has not yet been fully implemented. The company didn’t explain how this unfinished mechanism made its way into a public Windows 11 build.
What is known, however, is that the experimental feature affects firewall components, and its incomplete state is responsible for the recurring system notifications.
Interestingly, the operating system continues to function normally. Microsoft emphasizes that these log entries do not impact network performance or system security. Windows Firewall is working correctly, and the Event Viewer messages are merely a side effect of internal, unfinished enhancements.
At the same time, security experts and system administrators rightly point out that such false positives make it harder to monitor system health. The Windows Event Viewer is often used to assess a system’s reliability and detect potential problems, and constant erroneous logs only clutter the reports.
Analysts note that incidents like this undermine trust in the quality of Windows preview builds. Ironically, the existence of unfinished features in public versions of the OS contradicts the very purpose of the Windows Insider program, which is supposed to test such elements in a closed environment.
So far, Microsoft has not provided further details about the mysterious feature causing the errors. Nor has the company announced a specific timeline for resolving the issue. Instead, they issued a vague statement that developers are working on a fix, which will be included in an upcoming update.
Microsoft also declined to comment on how the unfinished code ended up in a user-facing build. Still, such occurrences are not unusual, even for tech giants.
Experienced developers are well aware that software often contains “future” components that aren’t supposed to affect users. But in practice, such code fragments can sometimes manifest — as happened here.
Nevertheless, compared to the more serious issues accompanying the Windows 11 24H2 update, this situation is seen more as a mild annoyance than a major crisis. After all, systems remain stable, connections are uninterrupted, and user data stays safe.
Version 24H2 itself has already been the subject of discussion due to numerous bugs. The appearance of yet another glitch only reinforces the opinion that this build is still far from final.
Users who have already installed the June update have no choice but to wait for the next release, which, according to Microsoft, will fix the event log error. In the meantime, it’s wise to stay alert and remember that the system log may reflect not only real threats, but also the behind-the-scenes experiments of developers.
