BURSTMicrosoft has officially acknowledged a harmless error event appearing in Windows Firewall With Advanced Security logs following the installation of the June 2025 Windows non-security preview update.
The company confirmed on July 2, 2025, that the error event, designated as event 2042, poses no security risks and can be safely disregarded by users.
Key Takeaways
1. Event 2042 "Config Read Failed" in Windows Firewall logs after the June 2025 update is benign and can be ignored.
2. Windows Firewall functions normally despite error messages appearing on restart.
3. Users don't need to troubleshoot—it's just a cosmetic logging issue from incomplete development feature.
4. Microsoft is working on resolution for upcoming release (no timeline given).
The issue affects Windows 11 version 24H2 systems running OS Build 26100.4484 that received the KB5060829 update released on June 26, 2025.
Technical Details of Event 2042 Error
The error manifests in Windows Event Viewer as event 2042 under the Windows Firewall With Advanced Security category, displaying a “Config Read Failed” status message accompanied by the description “More data is available.”
This event entry is automatically generated each time affected devices undergo a restart cycle, creating repetitive log entries that may concern system administrators and security-conscious users monitoring their firewall operations.
Despite its prominent placement in security event logs, Microsoft emphasizes that this particular error does not indicate any functional impairment of the Windows Firewall system.
The firewall continues to operate with full security capabilities, maintaining network protection protocols and filtering mechanisms without interruption.
The error stems from an incomplete implementation of a feature currently under development within Microsoft’s firewall architecture, rather than from any operational malfunction or security vulnerability.
System administrators can identify this specific error by examining Event Viewer logs under Windows Logs > Security, where event 2042 entries will appear with the characteristic “Config Read Failed” message.
The error’s technical classification falls under informational logging rather than critical system alerts, distinguishing it from genuine security or operational issues that require immediate attention.
Microsoft’s Response
Microsoft has categorized this issue as “Confirmed” in their official documentation, indicating acknowledgment and active investigation.
The company has explicitly stated that no user intervention or administrative action is required to address this error event, as it represents a cosmetic logging issue rather than a functional problem requiring remediation.
The technology giant is currently developing a resolution for this erroneous event logging and has committed to delivering a fix through an upcoming Windows release.
However, Microsoft has not provided a specific timeline for when users can expect the corrected update to become available through Windows Update channels.
Users experiencing this error on Windows 11 version 24H2 systems can continue normal operations without concern for security implications.
System administrators are advised to document this known issue when reviewing security logs to avoid unnecessary troubleshooting efforts.
Microsoft recommends monitoring their official update channels for future announcements regarding the resolution’s availability and deployment schedule.
Investigate live malware behavior, trace every step of an attack, and make faster, smarter security decisions -> Try ANY.RUN now
The post Microsoft Confirms Error Entry in Windows Firewall With Advanced Security appeared first on Cyber Security News.