Microsoft has successfully addressed a persistent issue that led to erroneous Windows Firewall notifications following the reboot of Windows 11 24H2 systems, particularly those equipped with the June 2025 preview update. This resolution is encapsulated in the KB5062660 preview cumulative update for Windows 11 24H2, which was released on Tuesday. Users can expect this fix to be rolled out more broadly with the upcoming August Patch Tuesday updates.
Background on the Issue
The company first acknowledged the existence of this bug on July 3rd, advising system administrators to disregard misleading warnings that appeared in the Event Viewer concerning Windows Firewall with Advanced Security. Microsoft clarified that the root cause of the issue stemmed from a new feature still in development, which had not yet been fully integrated into the operating system.
Specifically, the error manifested in the Event Viewer as event 2042 for Windows Firewall With Advanced Security, displaying the message ‘Config Read Failed’ along with ‘More data is available.’ Microsoft reassured users that despite the frequent logging of this event upon device restarts, it did not indicate a genuine problem with Windows Firewall and could be safely ignored.
On July 8th, Microsoft issued an apology after erroneously declaring the issue resolved, promising that a fix would be forthcoming. This incident is part of a broader pattern, as the company has recently navigated similar challenges affecting various Windows features, leading to a series of misleading notifications without any real consequences.
For instance, in April, Microsoft confirmed and rectified another known issue that resulted in invalid 0x80070643 failure errors during the installation of the April 2025 Windows Recovery Environment (WinRE) updates. Furthermore, that same month, the company addressed a bug that triggered incorrect BitLocker drive encryption errors on both Windows 10 and Windows 11 devices, a problem attributed to a reporting issue. This particular bug, confirmed in October, primarily affected managed Windows environments where drive encryption was enforced on the operating system and fixed drives.
