Fix Your Windows 11 Firewall After the Security Bug

Windows 11 users were quickly surprised after a recent update from Microsoft resulted in a never-ending firewall error that shows every time they restart their system. The May 13th KB5058411 update is causing frustration for a number of users who find errors when trying to install it, as well as the system failing to reboot after updating. When Windows Firewall with Advanced Security shows you the “Config Read Failed” message, one could take it the wrong way and assume security on the system is worse off than it is.

This is not a valid security concern. On the contrary, it is just another fumbled update from Microsoft where users don’t know which update is safe and which is not. Here’s what to know about this Windows 11 Firewall problem and how to fix it.

The Real Story Behind Event 2024

Windows 11 users experiencing this issue will have event 2024 recorded in the Event Viewer under Windows Firewall with Advanced Security. The error is "Config Read Failed" with the mysterious "More data is available" added, not exactly what users expect to see communicated to them when their security is in question.

Use IPQualityScore to identify virtual devices and spoofers, helping your business prevent fraud and ensure authentic user interactions.

The thing that makes this so annoying: the error occurs every time I restart the system. Now, imagine if every time you booted up your computer, you were to see what looked like a firewall failure message. Naturally, most people would think their defences had been breached.

Microsoft has now acknowledged that the problem is the result of the June 26 KB5060829 Windows update. But this is the worst possible time, given the continuing cybersecurity threats in which attackers take advantage of weaknesses in the system to gain remote access. When users experience firewall errors, they are rightly concerned about their protection from real threats like CVE-2025-33073.

This is not just about system messages. Some of my visitors can tell me that they have got a virus after browsing some "bad" websites for fun content. ReaperScans became one of such scanlation sites. This mirrored entertainment may have malware that can mess with your Windows. This type of setting explains why legitimate system failures are so alarming to users since there are many ways they can already be attacked.

Microsoft’s Admission and What It Reveals

So Microsoft’s response to this Windows 11 Firewall bug is a bit of reassurance, but also a worrying admission. The company also confirmed that users should have “no reason to be concerned, as this does not reflect an issue with Windows Firewall.” Despite all the scary messages, your firewall protection still works.

But here’s where things get a little alarming: Microsoft said this failure is tied to “a feature” that is presently being developed but isn’t yet supported. This is terrible news for Microsoft’s quality control. How is half-baked, not-fully-developed code responsible for popping error messages onto millions of Production systems?

The company is sticking to “working on a resolution and will provide an update in an upcoming release,” so there’s no telling when users will get this fix. This leaves Windows 11 users to deal with recurring error messages while they wait for Microsoft to redress its development oversight.

Practical Steps While Waiting for Microsoft’s Fix

What should Windows 11 users do while living with these misleading error messages? Here are the most practical approaches:

Monitor official Microsoft channels for updates. Generally, the company pushes out information through Microsoft Support pages, Windows Central, or an announcement. Subscribe to notifications for the acceptance of Windows update news. Subscribing to notifications for the acceptance news of Windows update is what’s helpful; you get to know about the resolution timelines.

Continue everyday security practices without concern about this specific error. Your Windows Firewall remains fully operational despite the misleading display messages. Don’t disable firewall protection or install alternative security software specifically because of this error.

Document error occurrences if you’re in an enterprise environment. IT personnel might need to assure users and management that these are not real security holes being reported. Good documentation is key to keeping stakeholders (who could panic at the sight of firewall errors) in the loop of what’s happening.

Avoid making hasty security changes based on these messages. The temptation to “fix” what appears broken can lead to actually compromising your security by disabling legitimate protection features.

Why This Matters Beyond One Update

This Windows 11 Firewall security flaw isn’t just an ordinary update issue. It raises some fundamental queries about how large technology companies validate updates before they are rolled out to live systems.

If Microsoft needs to acknowledge that error messages are a “feature in development”, then it implies that their update pipeline allowed unfinished code to reach the public. This is not just a horrible user experience; it’s a failure of quality control that erodes user trust in actual security warnings.

The far-reaching consequences include the ways in which users will view future security warnings. When companies keep pushing out updates that create false alarms, users tend to become immune to real security alerts. This “cry wolf” effect can then leave systems susceptible if real threats do appear.

Think about how this impacts enterprise environments where IT needs to separate absolute security from display errors related to updates. Resources expended to investigate false alarms are resources that are not available to respond to real threats.

Your Firewall Protection Continues Working

You have exception messages releasing your Event Viewer, and your Windows 11 firewall is still getting the job done. This security issue is only a display and logging issue and not a functionality issue with your firewall protection.

Microsoft recognises that no security feature has been broken in practice. The error messages cause worry with no evidence of actual leaks. Your network traffic filtering, application blocking, and other firewall tasks work just like they should.

It’s just a reminder that even big tech companies shit the bed every once in a while to throw up a little half-baked, poorly tested code.” Annoying to users who have to contend with obfuscated error messages, but it doesn’t suggest that your system has been compromised in any way.