Microsoft has officially acknowledged a known issue affecting Windows 11 users following the installation of the June 2025 non-security preview update, with error events appearing in Windows Firewall logs that can be safely disregarded by users and system administrators.
Microsoft confirmed on July 2, 2025, that users who installed the June 2025 Windows non-security preview update (KB5060829) may encounter recurring error events in their security event logs related to Windows Firewall With Advanced Security.
The acknowledgment comes as part of Microsoft’s ongoing effort to maintain transparency regarding known issues affecting their operating systems.
The error specifically manifests in Event Viewer as event 2042 for Windows Firewall With Advanced Security, displaying a “Config Read Failed” status accompanied by the message “More data is available.”
This error event occurs systematically each time affected devices are restarted, potentially causing concern among users who monitor their system logs for security-related issues.
The issue affects Windows 11 version 24H2 systems running OS Build 26100.4484, with Microsoft confirming that server editions remain unaffected by this particular problem.
The timing of this disclosure follows Microsoft’s standard practice of documenting known issues shortly after they are identified in widespread deployments.
Error Details and User Impact
Despite the alarming nature of firewall-related error messages, Microsoft has provided clear guidance that these specific events pose no actual threat system security or functionality.
The company emphasizes that Windows Firewall continues to operate normally, with all protective features functioning as intended throughout the error logging process.
Technical analysis reveals that the error stems from a feature currently under development within Microsoft’s firewall architecture that has not yet been fully implemented.
This incomplete implementation triggers the configuration read failure, resulting in the repetitive logging of event 2042 without affecting the underlying security infrastructure.
System administrators and users can safely ignore these error entries without compromising their security posture.
Microsoft’s assessment indicates that no remedial action is necessary, as the errors represent logging artifacts rather than functional deficiencies in the firewall system.
The company has specifically noted that no Windows processes are impacted by these events, maintaining system stability despite the presence of the logged errors.
Future Resolution Plans
Microsoft has committed to addressing this issue through their standard update cycle, indicating that a resolution will be included in an upcoming release.
The company’s next steps involve developing a fix that will eliminate the erroneous logging while preserving the intended functionality of the feature under development.
The timeline for resolution remains unspecified, though Microsoft’s acknowledgment suggests that work is actively underway.
Users can expect the fix to be delivered through regular Windows Update channels, likely as part of a cumulative update or monthly security release.
This incident highlights Microsoft’s proactive approach to communicating known issues, even when they pose no immediate threat to users.
By documenting and publicizing such problems, Microsoft enables system administrators to make informed decisions about their monitoring and response protocols.
Find this Story Interesting! Follow us on LinkedIn and X to Get More Instant Updates.
.webp?w=356&resize=356,220&ssl=1 "Microsoft Teams Blocking Users from Accessing Embedded Office Documents")
