Microsoft Acknowledges Windows 11 KB5060829 Problems, But It’s Safe to Ignore

The recent KB5060829 update for Windows 11 24H2 has introduced a noteworthy bug concerning the Windows Firewall with Advanced Security. Initially released as an optional update, this patch subsequently triggered a persistent error message that users could not overlook, prompting Microsoft to acknowledge the issue on their release health page.

According to reports from Windows Latest, a newly identified bug has been listed in the July 2025 documentation, specifically added on July 2. This entry refers to an incorrect event 2042 related to Windows Firewall, further complicating post-update experiences for Windows users.

Microsoft has attributed the root cause of this bug to an experimental feature that leads to the aforementioned error. However, it remains unclear whether this is linked to a new security feature or a different issue altogether. It’s important to note that this error is only affecting users who installed the update from June 2025 and are running the 24H2 version of Windows 11.

To alleviate this issue, Microsoft is actively developing a solution aimed at preventing the system from generating these unnecessary event viewer alerts. Users may expect this correction to be included in the upcoming Patch Tuesday update.

2025-06 Cumulative Update Preview for Windows 11 Version 24H2 for x64-based Systems (KB5060829)

For those seeking immediate relief, an effective workaround involves uninstalling the KB5060829 update via the Settings app. By removing this particular update and restarting your PC, you can then verify the Event Viewer for any lingering 2402 entries. Nonetheless, this isn’t the sole issue currently acknowledged in Microsoft’s ongoing list.

Growing Concerns: Issues from Recent Updates

The updates from March and April have resulted in several complications with third-party applications functioning within 24H2. Problems such as the Dirac Audio issue and other conflicting app integrations have persisted without resolution.

It is worth noting that many of these complications are addressable through necessary updates from developers, though the timeline for these fixes appears longer than expected. Until developers issue patches, users reliant on affected applications are prevented from updating to the 24H2 version.

As of June 1, users experienced another interruption: the web filtering feature within Family Safety was compromised, preventing parents from successfully adding browsers to their blocklist. This issue primarily impacts those who have recently updated their browsers, which occasionally remain unrecognized until Microsoft updates their compatibility lists.

Source & Images