Should You Ignore the “Firewall Config Read Failed” Windows 11 firewall error?
Ignore “Firewall Config Read Failed” in Windows 11 firewall error After KB5060829
Windows 11 users installing the June 2025 preview update (KB5060829) reported seeing Event 2042 warnings in their Event Viewer labeled “Windows 11 firewall error Config Read Failed—More data is available.” Despite the alarming message, Microsoft confirmed this error is a harmless artifact of an in-progress feature and can be safely ignored.
Content Outline
- What triggered the error
- Event View details
- Why it’s harmless
- Microsoft statement & timing
- When to take action
- How to verify firewall works
- Additional tips & troubleshooting
What triggered this error?
Microsoft’s June 2025 preview update (KB5060829) includes a new firewall feature still in development. Because it’s not fully integrated yet, it triggers a “Config Read Failed” event during system reboot.
How to identify Event 2042 in Event Viewer
When checking Event Viewer → Windows Logs → Security, you might see:
- Source: Windows Firewall with Advanced Security
- Event ID: 2042
- Message: Config Read Failed / More data is available
This describes only a log entry—not broken firewall functionality.
Why this isn’t a real firewall error
Microsoft clarified: “Windows Firewall is expected to function normally, and no action is required.” The error stems from the new feature’s logging process—not a malfunction BleepingComputer.
Official Microsoft statement
On the Windows release health dashboard, Microsoft says this warning can be safely ignored and that a dedicated fix is being prepared BleepingComputer.
When you should investigate further
Only take action if, in addition to Event 2042 entries, you face:
- Issues with internet connectivity
- Third-party firewall alerts
- Unable to update Windows
Otherwise, no further steps are needed.
Verify Firewall is working
- Open Windows Security → Firewall & network protection
- Ensure active profiles (Domain, Private, Public) say Active
- Use PowerShell:
Get-NetFirewallProfile | Format-Table Name,Enabled. All profiles should be True.
Troubleshooting tips
- Temporarily disable third-party software that might misinterpret firewall logs.
- Restart after July/August updates—Microsoft will fix the logging error automatically.
- For enterprise setups, review Centralized Firewall logs in your SIEM; ignore Event 2042 entries from Windows 11 24H2.
Related known issues
Microsoft has recently addressed similar false alarms, such as BitLocker warnings and WinRE update failures PCWorld.
Conclusion
Windows 11’s Event 2042 firewall warning (Config Read Failed) after KB5060829 is a benign log event, not a security flaw. Microsoft advises ignoring it as the firewall still works normally.
A fix is expected in upcoming cumulative updates—no action required on your part unless additional firewall issues appear.
FAQs
Q: Does this error block my firewall?
A: No. Windows Firewall continues to work normally despite the warning.
Q: Should I reboot or roll back?
A: No. Reboot isn’t necessary. Rolling back the update isn’t advised unless you experience other issues.
Q: When will Microsoft fix this?
A: A fix is planned in an upcoming cumulative Windows 11 update. Keep your system updated.
Q: How can I verify firewall is functioning?
A: Check active firewall profiles in Windows Security or use PowerShell as shown above.