Windows 10 June 2025 KB5061087 Update: Critical Fixes & End-of-Life Prep

Amid the approach of Windows 10’s final stretch before end-of-life, Microsoft has released the June 2025 non-security preview update—KB5061087 (OS Build 19045.6036)—for Windows 10 version 22H2. This update, applicable to Home, Pro, Enterprise, Education, and IoT Enterprise editions, offers a collection of quality improvements, critical fixes, and a subtle reminder of the ticking clock: official support for Windows 10 is set to expire on October 14, 2025. For organizations and users still tethered to Windows 10, this update delivers more than routine maintenance; it frames the landscape of last-chance upgrades before mandatory transition to Windows 11 or the risks associated with unsupported operating systems.

Understanding the June 2025 Preview Update​

Microsoft’s non-security preview updates serve as a way for users and organizations to test forthcoming improvements and changes ahead of wider Patch Tuesday deployments. KB5061087 follows this tradition, addressing a swath of issues impacting device stability, user experience, enterprise scenarios, and regional compliance. It’s worth recalling, however, that “preview” means these updates are optional: they’re offered to catch issues before wide release, but organizations should weigh the immediate need for fixes against the risk of early adoption.

Key Issues Addressed​

Mobile Operator Profiles​

• Updated COSA Profiles: The Country and Operator Settings Asset (COSA) profiles have received an update. While largely invisible to the end-user, these profiles play a critical role in how Windows 10 devices connect and configure themselves on global mobile networks. The update is particularly relevant for business travelers or IoT deployments relying on cellular connectivity, suggesting Microsoft’s ongoing commitment to worldwide compatibility until Windows 10 bows out.

App Platforms and Frameworks​

• COM Functionality Fix: A significant bug in Component Object Model (COM) operations—specifically, remote activation failures with error code 0x8001011—has been squashed. This addresses issues in distributed applications and scripts reliant on COM automation, a backbone for legacy enterprise apps and management tools.
• curl Updated to v8.13.0: Recognizing the importance of up-to-date networking tools, Microsoft now includes a more recent version of curl, the widely used command-line tool for transferring data with URLs. Such upgrades tighten security, add protocol support, and enhance reliability, especially in scripting and automation scenarios.

Authentication Platform​

• Entra ID WAM Plugin Fix: Windows Account Manager's plugin for Entra ID—formerly Azure Active Directory—received a fix for device registration failures. This is a critical patch for organizations running hybrid cloud or identity-intensive environments, as it ensures smoother onboarding and device compliance under Microsoft’s identity systems.

Input and Composition​

• Language Pack Removal Fix: Addressing a long-standing pain point, this update corrects the removal logic for unused language packs and Features on Demand (FOD) packages. Previously, leftover components led to unnecessary storage and protracted update installs—a silent but measurable productivity drain.

Print and Peripherals​

• Multi-Function Printer (MFP) Scanning Fix: Users with USB-connected MFPs featuring dual protocol interfaces found that scanning functionality was broken at the OS level. This update restores built-in scan support, which is crucial for small businesses and education sectors still relying heavily on physical document workflows.

Start Menu​

• Jump List Disappearance & Start Menu Launch Failure: Two Start Menu bugs—one causing jump lists to vanish, another blocking the menu from opening post-update—are resolved. For IT administrators and end-users alike, Start Menu reliability is foundational to user satisfaction and support overhead.

WinSaS (System > About Dialog)​

• Version Display Correction: The Settings > System > About screen was incorrectly showing 'version 2009' instead of '22H2', which has been rectified. While seemingly trivial, accurate version reporting helps both users and support desks diagnose compliance and compatibility issues.

EU Digital Markets Act (DMA) Compliance​

• Browser Defaults & Pinning: In a nod to European legislation, the update changes default browser behavior in the European Economic Area (EEA): any newly set default browser is automatically pinned to the Taskbar and Start menu, and takes over HTTP and .pdf associations. This increases user choice and aligns with regulatory requirements, but may surprise users accustomed to a more hands-off browser setup.

Servicing Stack Improvements​

• Kiosk Device Crash Resolved: Devices running in kiosk mode with ForceAutoLogon and Shift Override configurations were susceptible to blue screen crashes when locked/unlocked by support staff. Given the heavy use of Windows 10 in secure kiosks, education labs, and retail, this fix should reduce downtime in critical environments.

File Server (SMB Oplock Handling)​

• Resource Hang Fix: An obscure but potentially severe bug where the system could stop responding due to mishandling Oplock break requests (crucial in synchronized file access over SMB shares) is now addressed. This stability fix is most relevant to organizations using Windows 10 as a lightweight file server or in remote/home office storage scenarios.

Servicing Stack Update: KB5061902​

With KB5061087, Microsoft continues the practice of bundling the latest Servicing Stack Update (SSU)—KB5061902, version 19045.6035—with the cumulative package. SSUs are critical building blocks that improve the reliability of the Windows Update process itself, reducing instances of update failures and corrupted OS images. Failure to maintain or apply the correct SSU has historically been a root cause of patching headaches—particularly so for offline imaging, Windows Server Update Services (WSUS) deployments, and enterprise environments employing custom servicing workflows.

Known Issues: Noto Font Rendering in CJK Languages​

A prominent known issue flagged in KB5061087 centers on blurry or unclear text rendering for CJK (Chinese, Japanese, Korean) scripts when displayed at 96 DPI (100% scaling) in Chromium-based browsers—including Microsoft Edge and Google Chrome. This artifact traces back to Microsoft’s adoption of Noto fonts in March 2025, aiming to enhance font fallback and CJK character display.
Unfortunately, the Noto font rendering at standard pixel densities results in less legible text due to inadequate pixel density, leading to poor character clarity and alignment. While increasing display scaling (to 125% or 150%) offers a workaround, this is not always practical on devices with fixed UI or stringent accessibility requirements.
Both Microsoft and Google jointly introduced Noto fonts to address missing glyphs and inconsistencies with poorly specified web fonts—an effort that benefits internationalized web apps and global businesses. However, the ongoing browser rendering issue undermines this benefit for now, and Microsoft's notice of investigation implies that users should expect further mitigations or documentation before a permanent fix is deployed.

Critical Analysis: Risks Associated with Font Changes​

Font rendering is a subtle but impactful part of international user experience. Microsoft’s willingness to experiment with new font defaults during the last year of Windows 10’s life cycle is bold, but perhaps precarious for enterprises and consumers heavily dependent on CJK workflows. For regulated businesses in Asia or internationalized development teams, this preview build is better tested in staged environments before wide deployment.

Installation and Deployment Guidance​

The mechanics of installing KB5061087 are straightforward for most users: it can be fetched as an optional update via Windows Update (“Settings > Update & Security > Windows Update”), manually from the Microsoft Update Catalog, or deployed in bulk using WSUS.

Prerequisites​

• Offline Imaging: Devices lacking the July 2023 (KB5028244) or later cumulative update must first apply the standalone October 2023 SSU (KB5031539).
• WSUS/Manual Deployments: Devices without May 2021 (KB5003173) or later must first install the special August 2021 SSU (KB5005260).

These prerequisites ensure that older Windows 10 images or infrequently updated systems can accept and process the new cumulative update smoothly. Microsoft’s detailed attention to prerequisite combinations is a testament to the lingering complexity in Windows client servicing, especially across different patching cadences.

Uninstallation Caveats​

Uninstalling the LCU (Latest Cumulative Update) gets more complex once SSU and LCU are combined:

• Use DISM with the /Remove-Package option, specifying the correct LCU package name. The usual Windows Update Standalone Installer (wusa.exe /uninstall) will not work, as the SSU cannot be removed individually post-installation.
• This requires technical know-how, making it a non-trivial operation for average consumers or small business admins.

End of Support Is Nigh: What’s Next for Windows 10?​

The most significant meta-narrative of the June 2025 preview update is its imminent finality. Windows 10—trusted by over a billion users at its height—will see end of support after October 14, 2025. This means:

• No more free security updates.
• No ongoing technical support (from Microsoft) for newly discovered bugs or third-party compatibility issues.
• Growing risk exposure—especially for businesses bound by cybersecurity frameworks or handling sensitive data.

Microsoft advocates upgrading to Windows 11 wherever possible, citing ongoing security, feature, and management improvements.

Extended Security Updates (ESU): A Possible Option?​

Historically, for Windows 7 and earlier, Microsoft has offered Extended Security Updates (ESU) for a fee, buying additional years of critical patching for organizations unable to migrate quickly. No announcement has been made regarding an ESU option for Windows 10 as of June 2025, but many analysts expect a similar program. Still, this would only prolong the inevitable—core innovation and broad support are undeniably shifting to Windows 11.

Evaluating the Update: Strengths and Weaknesses​

Notable Strengths​

• Comprehensive App and Device Fixes: By targeting everything from COM-based app compatibility to niche scenarios involving kiosk and print devices, KB5061087 displays a holistic approach to Windows reliability.
• Regulatory Compliance: Incorporating EEA browser default requirements ahead of enforcement demonstrates Microsoft’s responsiveness to changing legislative environments.
• Bundled SSU/LCU Simplicity: The ongoing effort to streamline updates with bundled Servicing Stack and Cumulative Updates lowers the friction for IT departments managing large estates or slow-moving images.

Potential Risks​

• Font Rendering Issues: The only flagged known issue—blurry CJK text in popular browsers at standard scaling—potentially affects millions of users, mainly in Asia, who routinely browse with Edge or Chrome. For public institutions, schools, and businesses, this can compromise accessibility and clarity.
• End of Life Looms: Some devices may not support Windows 11 due to hardware requirements, leaving users with the difficult choice of running unsupported Windows 10, repurposing old hardware, or seeking costly ESUs (if and when offered).
• Complex Uninstall Path: Should the update introduce incompatibilities, the process to roll back is less user-friendly, especially as combined package rollbacks require DISM and technical familiarity.

Cautious Notes on Unverified Claims​

While Microsoft’s documentation is the primary and reliable source for update details, it’s always prudent to monitor community and IT admin feedback on early rollout days for emergent or undocumented regressions. Historically, minor Windows updates have occasionally reclaimed notoriety in unforeseen compatibility glitches.

Best Practices for Windows 10 IT Administrators and Power Users​

• Test in a Controlled Environment: Don’t rush the preview update to production endpoints, especially in businesses with high CJK utilization or custom Kiosk setups.
• Monitor Font Rendering: Solicit feedback from users working in Chinese, Japanese, or Korean environments and be prepared to use workarounds or alternative browsers until a fix arrives.
• Stay Informed on Support Timelines: Make sure all device owners and relevant stakeholders are aware of Windows 10’s pending end of support. Plan migration budgets and timelines accordingly.
• Leverage Update Channels Wisely: Use the Update Catalog or WSUS for staged deployments; avoid 'set and forget' where known issues could impact mission-critical workflows.
• Review Regulatory Impacts: For organizations in the EEA, ensure that new browser default and pinning behaviors do not conflict with imaging/customization standards.

Conclusion: A Preview with Purpose—and a Final Countdown​

KB5061087 is more than a routine roll-up: it’s a reflection of Microsoft’s commitment to stable, secure, and compliant Windows 10 environments, even as the platform approaches sunset. With targeted fixes for enterprise-critical workflows (printing, authentication, COM applications), and an eye on global consumers (mobile profiles, browser defaults, font fallbacks), the June 2025 preview balances necessity with responsiveness.
However, its deployment comes against the inescapable reality of Windows 10’s end of support. While the update enhances short-term reliability, users and organizations must pivot their long-term strategies to avoid the risks of unsupported infrastructure. Whether through careful rollout of these final updates, increased vigilance regarding known issues, or planning aggressive migration campaigns, the clock is ticking. The June 2025 preview is a necessary stopgap, not a pathway to indefinite stability.
For up-to-date details and additional documentation, always consult Microsoft’s official update history and support articles, as community forums often surface real-world issues faster than official channels. As KB5061087 rolls out, it’s a prime opportunity for IT decision-makers to inventory their upgrade plans and ensure no device is left behind as Windows 10’s historic journey draws to a close.

---

Source: Microsoft - Message Center June 24, 2025—KB5061087 (OS Build 19045.6036) Preview - Microsoft Support