When Microsoft released the Windows 11 24H2 update, users anticipated new features and crucial security improvements as part of their regular Patch Tuesday experience. However, the June 2025 rollout—specifically cumulative update KB5060842—became a textbook example of how even thoroughly-tested patches can introduce critical compatibility issues, especially for gaming enthusiasts. The fallout triggered an urgent response from Microsoft, resulting in a rare out-of-band (OOB) update: KB5063060. Let’s delve into the details of this incident, exploring what went wrong, how Microsoft responded, and what Windows 11 users can expect moving forward.
Patch Tuesday, Microsoft’s tradition of monthly cumulative updates, is known for introducing both security fixes and incremental feature updates. On June 10, 2025, Microsoft pushed KB5060842 to Windows 11 users running version 24H2. The intent was straightforward: strengthen security and iron out lingering bugs. Yet, almost immediately, user reports began surfacing about failed installations, error messages, and, most concerning for gamers, unexpected system reboots when launching popular titles like Fortnite.
One specific error code, “0x80073712,” was frequently cited. According to official Microsoft documentation, this code typically indicates missing or corrupt update files. Users noticed that the update either refused to install or, if installed, caused subsequent issues with system stability and gaming performance.
This was far from a fringe issue: Fortnite boasts tens of millions of active players, and EAC support extends to a broad portfolio of high-profile multiplayer games. A break in compatibility threatened to alienate both casual players and professionals, raising the stakes for a rapid fix.
KB5063060, according to support notes, “addresses an incompatibility issue where Windows might restart unexpectedly when opening games that use the Easy Anti-Cheat service. Easy Anti-Cheat automatically installs with certain games to enhance security and prevent cheating in multiplayer online PC games.”
For devices that already updated to KB5060842 before it was withdrawn, the new patch installs rapidly, acting more like a small bugfix. But for those who did not receive the earlier update—either because it never appeared or failed to install—KB5063060 offers the entire suite of changes in one go. This dual behavior minimizes complexity for end-users, a move that earned Microsoft some praise.
Additionally, the update advances the OS build number to 26100.4351 and includes the latest servicing stack update, KB5059502. This was observed firsthand by testers at Windows Latest, who reported stable operations after installing the emergency update.
That said, some users are not seeing KB5063060 immediately. Microsoft confirmed this is intentional: the update is rolling out in phases to ensure stability. Patience, they emphasize, is warranted as the update propagates through the various Windows Update channels.
Microsoft’s recommendation for affected users is to adjust display scaling to 125% or 150% until a permanent fix can be released. This workaround is consistent with common best practices for font scaling issues, but it remains an inconvenience for those seeking crisp text at default settings.
There are, however, notable strengths in Microsoft’s response:
Still, the incident demonstrates that targeted compatibility testing, especially around security-critical gaming environments, is fundamental. Online gaming is often a target for cheaters and hackers, and interruptions in anti-cheat services have both security and reputational consequences.
Yet, complexity is growing. Windows 11 now supports x64 and ARM architectures, multiple language packs, and deep integration with third-party frameworks. Each of these factors multiplies the number of variables Microsoft must account for in pre-release testing and in managing live rollouts.
For IT professionals, this incident serves as a reminder to:
As of this writing, the latest stable OS build after installation will be 26100.4351, with the included servicing stack update ensuring robust future patch reliability.
If you rely on East Asian language settings and notice blurry text in Edge or Chrome, the quick fix remains scaling your display up, which prompts Windows to render fonts with greater clarity. Microsoft has committed to delivering a more robust fix in a subsequent patch.
For users, the key takeaway is that while Windows 11’s update system is more resilient and responsive than ever before, vigilance and proactive engagement with official documentation are necessary. For Microsoft, the imperative is clear: continuous investment in compatibility testing, real-time telemetry, and clear user communication must remain at the forefront as Windows evolves.
As Windows 11 24H2 users transition to the newly patched build, the lessons learned from this episode should help inform better practices across the industry, ensuring that future updates deliver improvements without unintended consequences—and that when issues do arise, they are addressed with speed, clarity, and a user-first approach.
Source: Windows Latest Windows 11 KB5063060 24H2 out after KB5060842 issues with Fortnite and more
Patch Tuesday, Microsoft’s tradition of monthly cumulative updates, is known for introducing both security fixes and incremental feature updates. On June 10, 2025, Microsoft pushed KB5060842 to Windows 11 users running version 24H2. The intent was straightforward: strengthen security and iron out lingering bugs. Yet, almost immediately, user reports began surfacing about failed installations, error messages, and, most concerning for gamers, unexpected system reboots when launching popular titles like Fortnite.One specific error code, “0x80073712,” was frequently cited. According to official Microsoft documentation, this code typically indicates missing or corrupt update files. Users noticed that the update either refused to install or, if installed, caused subsequent issues with system stability and gaming performance.
The Gaming Angle: Easy Anti-Cheat and Widespread Reboots
The heart of the crisis revolved around the anti-cheat technology used by several popular online games. Epic Games’ Fortnite, among others, relies on Easy Anti-Cheat (EAC) to maintain a fair and hacker-free multiplayer environment. After installing KB5060842, some users found their systems abruptly rebooting upon launching EAC-protected games. The cause was a newly identified incompatibility between the cumulative update and kernels or services leveraged by EAC.This was far from a fringe issue: Fortnite boasts tens of millions of active players, and EAC support extends to a broad portfolio of high-profile multiplayer games. A break in compatibility threatened to alienate both casual players and professionals, raising the stakes for a rapid fix.
Microsoft’s Response: Rolling Out KB5063060
Within a day of these reports reaching critical mass, Microsoft made the rare decision to pull KB5060842 from Windows Update on affected machines, essentially stalling the normal Patch Tuesday rollout. Microsoft’s next move was to develop and release KB5063060—an out-of-band, cumulative update designed to resolve the specific EAC incompatibility while still delivering the full suite of June 2025 improvements and security patches.KB5063060, according to support notes, “addresses an incompatibility issue where Windows might restart unexpectedly when opening games that use the Easy Anti-Cheat service. Easy Anti-Cheat automatically installs with certain games to enhance security and prevent cheating in multiplayer online PC games.”
Dissecting the Patch: What KB5063060 Offers
Unlike minor hotfixes, KB5063060 is a heavyweight installer: the Microsoft Update Catalog notes the package weighs more than 3GB for both Intel and ARM64 systems. That’s because this update isn’t a simple patch; it’s a comprehensive cumulative update including everything from June’s Patch Tuesday (KB5060842) alongside the explicit correction for the EAC issue. This ensures users who skipped the problematic update can still bring their systems fully up-to-date by installing just KB5063060.For devices that already updated to KB5060842 before it was withdrawn, the new patch installs rapidly, acting more like a small bugfix. But for those who did not receive the earlier update—either because it never appeared or failed to install—KB5063060 offers the entire suite of changes in one go. This dual behavior minimizes complexity for end-users, a move that earned Microsoft some praise.
Additionally, the update advances the OS build number to 26100.4351 and includes the latest servicing stack update, KB5059502. This was observed firsthand by testers at Windows Latest, who reported stable operations after installing the emergency update.
Global Rollout, Staged and Monitored
Microsoft’s distribution of KB5060842 was not uniform—the company leveraged telemetry to identify systems using EAC and paused the update’s rollout there proactively. Despite this, the number of affected users was large enough to justify the OOB release. With KB5063060, Microsoft re-enabled Patch Tuesday delivery for all eligible PCs, promising that systems previously blocked due to EAC-related risks would now safely receive the update.That said, some users are not seeing KB5063060 immediately. Microsoft confirmed this is intentional: the update is rolling out in phases to ensure stability. Patience, they emphasize, is warranted as the update propagates through the various Windows Update channels.
Residual Bugs: The Font Rendering Problem
While KB5063060 effectively quashes the EAC-induced reboot bug, it is not entirely free of issues. Microsoft openly documented a new known problem: users of East Asian languages—specifically Chinese, Japanese, or Korean—might notice blurry text in browsers like Microsoft Edge and Google Chrome, especially when display scaling is set to 100%. This is due to recent changes in Windows’ fallback font logic, which now introduces Noto fonts to improve rendering.Microsoft’s recommendation for affected users is to adjust display scaling to 125% or 150% until a permanent fix can be released. This workaround is consistent with common best practices for font scaling issues, but it remains an inconvenience for those seeking crisp text at default settings.
Critical Analysis: What Went Wrong and What Was Done Right
In the rapidly shifting landscape of software updates, even industry giants like Microsoft can misstep. The root cause of the KB5060842 fiasco was a compatibility oversight with a third-party vendor (Easy Anti-Cheat) whose deep integration with Windows kernel services meant that even modest changes could trigger unforeseen interactions.There are, however, notable strengths in Microsoft’s response:
- Swift Withdrawal: Upon confirming the root cause, Microsoft moved quickly to pull the problematic update from distribution, limiting further user impact.
- Telemetry-Based Blocking: The company’s use of system data to pre-emptively halt updates for high-risk setups helped reduce the number of affected PCs.
- Comprehensive Communication: Both the Windows Latest report and Microsoft’s own support documentation kept users informed, outlining not just the nature of the problem but also clear steps for mitigation and workarounds.
- OOB Update Delivery: The release of an out-of-band cumulative update demonstrates flexibility in Microsoft’s patch management process, prioritizing customer experience over rigid scheduling.
- Testing Scope for Critical Third-Party Software: The incident highlights a persistent weakness in development and QA cycles: insufficient depth in third-party compatibility testing, especially for widely-used software like gaming anti-cheat systems.
- Complex Update Channels and User Confusion: Some users remain unaware of which updates they have received, which can create anxiety and uncertainty during critical patch rollouts. More transparent update logs and clearer UI notification would be beneficial.
- Residual Bugs Suggest Regression Risks: While the EAC issue is fixed, the emergence of new font rendering bugs in East Asian languages underscores how hotfixes can have ripple effects elsewhere. This “fix one, break another” tradeoff is a perennial challenge in cumulative update models.
Security Stakes: The Importance of Timely Patching
The security context of Patch Tuesday cannot be overstated. Delays in security patching expose users to evolving threats, including zero-day vulnerabilities and actively exploited bugs. By releasing KB5063060 promptly, Microsoft minimized the window of exposure introduced by pausing KB5060842. The company’s modern approach—prioritizing cumulative, all-in-one updates—helps ensure that all users, regardless of when they patch, are protected from the latest known vulnerabilities.Still, the incident demonstrates that targeted compatibility testing, especially around security-critical gaming environments, is fundamental. Online gaming is often a target for cheaters and hackers, and interruptions in anti-cheat services have both security and reputational consequences.
The Big Picture: Update Management in the Cloud Era
Modern Windows update infrastructure relies increasingly on telemetry, active monitoring, and dynamic rollout controls. Microsoft’s handling of this crisis, compared to past Patch Tuesday incidents, demonstrates how adaptive controls (like phased rollouts and OOB releases) can balance risk and coverage.Yet, complexity is growing. Windows 11 now supports x64 and ARM architectures, multiple language packs, and deep integration with third-party frameworks. Each of these factors multiplies the number of variables Microsoft must account for in pre-release testing and in managing live rollouts.
For IT professionals, this incident serves as a reminder to:
- Monitor Patch Status Actively: Don’t assume smooth updates; check vendor communication channels and Windows Update logs after each Patch Tuesday.
- Test Updates in Staging Environments: Especially crucial for gaming rigs, business-critical workstations, and non-English environments where font rendering or locale logic may change.
- Educate Users on Update Messaging: Normalizing the appearance of OOB or cumulative updates can reduce end-user confusion and support tickets.
Direct Downloads and Workarounds
For users or administrators needing immediate resolution, Microsoft has provided direct download links for KB5063060 via the Update Catalog for both 64-bit and ARM-64 systems. Download sizes remain hefty—over 3GB—reinforcing that this package is essentially a full OS refresh for the patch cycle.As of this writing, the latest stable OS build after installation will be 26100.4351, with the included servicing stack update ensuring robust future patch reliability.
If you rely on East Asian language settings and notice blurry text in Edge or Chrome, the quick fix remains scaling your display up, which prompts Windows to render fonts with greater clarity. Microsoft has committed to delivering a more robust fix in a subsequent patch.
Concluding Thoughts: Transparency and Agility in 2025’s Windows Update Reality
The unexpected events surrounding KB5060842 and the swift deployment of KB5063060 highlight both the challenges and the evolving strengths of Microsoft’s modern Windows update strategy. The saga underscores the critical importance of transparency, rapid incident response, and maintaining strong relationships with third-party software vendors. The growing complexity of the Windows ecosystem, from gaming to multilingual environments, means that even small changes can have wide-reaching effects.For users, the key takeaway is that while Windows 11’s update system is more resilient and responsive than ever before, vigilance and proactive engagement with official documentation are necessary. For Microsoft, the imperative is clear: continuous investment in compatibility testing, real-time telemetry, and clear user communication must remain at the forefront as Windows evolves.
As Windows 11 24H2 users transition to the newly patched build, the lessons learned from this episode should help inform better practices across the industry, ensuring that future updates deliver improvements without unintended consequences—and that when issues do arise, they are addressed with speed, clarity, and a user-first approach.
Source: Windows Latest Windows 11 KB5063060 24H2 out after KB5060842 issues with Fortnite and more