Windows 11 Firewall Error: Microsoft Apologizes for Premature “Resolved” Status, Fix Still Coming

Earlier this month, Microsoft added an event tag to the Windows 11 Health Dashboard, noting that beginning with the installation of the June 2025 preview update, users may encounter firewall configuration error warnings in the system’s Event Viewer.

Specifically, users will observe Event ID 2042, accompanied by a detailed log stating: “Windows Firewall with Advanced Security failed to read configuration.” This warning is generated after every system reboot.

At the time, Microsoft clarified that despite the recurring appearance of this event in the Event Viewer, it does not affect the actual functionality of the firewall, and users could safely disregard the warning.

In the July 2025 cumulative update, Microsoft initially marked the issue as resolved. However, the company has since revised the documentation, admitting that the problem remains unresolved and apologizing for the premature resolution status.

As noted in Microsoft’s support document:

“This disclosure was mistakenly updated to Resolved status on July 8. A resolution for this issue is planned to be included in an update to be released in the coming weeks. We apologize for any inconvenience or confusion.”

In essence, the issue itself is relatively benign, as it does not impact the firewall’s operation or user experience. What is surprising, however, is Microsoft’s erroneous status update—raising questions about how such an oversight could occur internally.

That said, this error might have some implications for enterprise IT administrators, many of whom routinely monitor system error events. Firewall-related warnings typically fall within the scope of such monitoring activities.

Since the issue remains unaddressed, any new instances of Event ID 2042 can be safely ignored until Microsoft delivers a permanent fix. Only then should administrators resume monitoring these events to guard against potential security disruptions caused by actual firewall malfunctions.

Related Posts:

• GitHub admitted to record some Plaintext Passwords in Its Internal Logs
• PyPI Swiftly Patches Privilege Escalation Flaw in Organizations Feature