Microsoft’s Recent Windows 11 Updates and Firewall Issues
At the close of June, Microsoft deployed a series of setup and recovery updates for Windows 11, identified as KB5062233, KB5060843, KB5062197, and KB5061090. These updates followed the earlier non-security preview updates for versions 24H2 (KB5060829) and 23H2/22H2 (KB5060826).
Identifying the Firewall Error
Recently, Microsoft acknowledged an issue associated with the KB5060829 update, particularly affecting the Windows Firewall functionality. IT and system administrators are likely to observe a persistent error in the Security event log, registering under event ID 2042 labeled “Config Read Failed, ” which indicates “More data is available” upon each device reboot.
Understanding the Error’s Implications
Despite being logged as an error, Microsoft emphasizes that this event does not signify a failure of the Windows Firewall itself. In fact, users can “safely ignore and disregard”it as the firewall continues to function properly, effectively enforcing security rules and monitoring network traffic. Microsoft assures that this event does not compromise any associated Windows processes.
Impact on IT and General Users
For IT support teams and average users, error logs are crucial for identifying configuration issues and maintaining system integrity. Consequently, unexpected log entries like these can generate unnecessary alerts, potentially leading to confusion and misdirected troubleshooting efforts.
A Unique Development Behind the Scene
Interestingly, this logged event is related to a new feature currently in development by Microsoft, which is not yet fully operational. Specific details regarding this new feature remain undisclosed as of now.
Cleaning Up the Event Logs
For administrators seeking to maintain clearer logs, it is possible to filter out event ID 2042 using the Event Viewer or PowerShell. Administrators can create a custom view in Event Viewer to exclude this specific ID from the Security log. Alternatively, users can utilize the Get-WinEvent -FilterHashtable command in PowerShell to achieve the same result.
Looking Ahead
Microsoft has communicated that efforts are underway to resolve the issue, with updates anticipated in the near future. However, no estimated time of arrival (ETA) has been disclosed yet. For further information regarding this issue, users can refer to the official Windows Health dashboard.
Leave a Reply