Windows 10 June 2025 KB5061087 Update: Final Support and Key Improvements

With the arrival of the June 2025 Windows non-security preview update (KB5061087, OS Build 19045.6036), the Windows 10 ecosystem continues to receive meaningful refinements even as its official end-of-support date draws closer. Windows 10, version 22H2, remains the final major feature set before extended support ceases in October 2025, but Microsoft’s cadence of preview and cumulative updates persists with an emphasis on stability, compatibility, and focused quality improvements. Parsing the details of this update provides deep insight not only into what users and administrators can expect, but also Microsoft’s shifting priorities as it gradually returns its full attention to Windows 11 and beyond.

Windows 10’s Final Act and the Preview Update Model​

Windows 10's development has long relied on a predictable system of monthly cumulative updates, including both security and non-security "preview" releases. The June 2025 non-security preview update, KB5061087, falls into the latter category. This means the update offers quality improvements, fixes, and non-security feature adjustments ahead of next month’s broader 'Patch Tuesday' release, allowing users to opt-in and businesses to test changes before they're widely deployed.
It should be emphasized: preview updates like KB5061087 do not include critical security patches; those arrive in the regular cumulative updates. However, these previews serve as a critical part of Microsoft's ongoing commitment to operational stability and user experience, even as Windows 10 transitions toward the end of its lifecycle.

Key Facts: End-of-Support Looming​

Perhaps the most impactful context for this update is Windows 10's approaching end-of-support date. After October 14, 2025, Microsoft will no longer provide free updates, technical assistance, or new fixes for Windows 10 devices. The company’s advice is unequivocal: migrate to Windows 11 for ongoing support and features.
This looming deadline frames every update in 2025. For organizations or users holding off on upgrades, each monthly preview and cumulative release becomes not just an incremental improvement, but a potential last opportunity to secure reliability and compatibility fixes before official patches cease.

A Deep Dive into June 2025’s Key Changes​

This KB5061087 update is designed exclusively for Windows 10, version 22H2, across all its mainstream editions: Home, Pro, Enterprise Multi-Session, Enterprise, Education, and IoT Enterprise. Below, each notable fix and enhancement is examined for its technical implications and day-to-day impact.

[Mobile Operator Profiles]​

• Updated Country and Operator Settings Asset (COSA) profiles.
• Impact: COSA profiles enable Windows to connect reliably to various mobile operator networks worldwide. Updates to these profiles may improve roaming, reduce connectivity issues, and ensure compatibility with new or updated mobile network infrastructure. For enterprise users leveraging Windows 10 in field devices or mobile environments, this update helps maintain seamless connectivity.

[App Platforms and Frameworks]​

• Fixed a Component Object Model (COM) bug affecting remote activations.
• Technical details: Users and developers saw remote COM activation attempts fail with error 0x8001011, potentially disrupting the functioning of distributed applications reliant on COM inter-process communication.
• Updated the built-in curl tool to v8.13.0.
• Impact: Curl is a fundamental open-source tool for transferring data with URLs, widely used in scripting and automation. The update to v8.13.0 likely reflects improvements in security, protocol support, and stability. According to the official curl changelog, this version introduces bug fixes and improved handling for various protocols—valuable for IT professionals and scripts running directly from Windows consoles.

[Authentication Platform]​

• Fixed: Device registration issues with Entra ID through Windows Account Manager (WAM).
• Details verified: Entra ID (which recently replaced Azure Active Directory branding) is foundational for enterprise authentication. Registration failures could delay or block device onboarding in managed environments; the fix restores confidence in trust management and IT deployment pipelines.

[Input and Composition]​

• Fixed an issue with the removal of unused language packs and Feature on Demand (FOD) packages.
• User impact: Previously, stale language packs or FODs would linger, wasting disk space and inflating update times. For users managing diverse, multilingual environments, this is a significant quality-of-life fix.

[Print and Peripherals]​

• Resolved: USB-connected multifunction printers with dual protocol interfaces could not scan.
• Verification: Dual-protocol Multi-Function Printers (MFPs), which provide both printing and scanning via the same cable, were intermittently unable to use the built-in scanning feature after previous Windows 10 changes. This bug would have severely impacted small businesses and home offices reliant on such peripherals.

[Start Menu]​

• Fixed: Disappearance of Start Menu jump lists.
• *These lists provide shortcuts to frequently accessed files and commands and are integral to fast task switching.**
• Resolved: Some Start Menus not opening after updates.
• This rare, but critical, regression could leave devices functionally unusable if the primary navigation interface was broken after update installation.

[WinSaS]​

• Corrected: "Settings > System > About" showing version 2009 instead of 22H2.
• While cosmetic, accuracy in version labeling helps IT departments properly inventory and support devices.
• DMA Compliance Updates for Browsers in the European Economic Area (EEA):
• Behavior change verified against Microsoft and EEA regulations: Whenever a new default browser is set, it now pins itself automatically to both the Taskbar and Start menu. This strengthens compliance with EU Digital Markets Act (DMA) requirements, striving for browser choice transparency.
• Default file associations update: HTTP and .pdf files now properly associate with the selected default browser, preventing inadvertent fallback to Microsoft Edge.

[Servicing]​

• Fix: Blue screen on kiosk devices using ForceAutoLogon and Shift Override.
• Details checked against enterprise forums: Managed kiosk devices—used in point-of-sale or public terminal settings—could crash if support staff tried to interrupt auto-login. Reliable kiosk operation is essential for public-facing or high-volume business environments.

[File Server]​

• Corrected: SMB share lock-ups when handling Oplock break requests.
• Oplock (Opportunistic Lock) is an SMB file sharing feature for synchronization performance. This bug fix prevents server-side hangs that could cascade into broad file access outages in corporate environments.

Servicing Stack Update: KB5061902​

Bundled within KB5061087 is a new servicing stack update (SSU), version 19045.6035. The servicing stack is the underlying infrastructure that manages installing Windows updates. Microsoft’s ongoing bundling approach ensures users always have the latest SSU, reducing the likelihood of update installation failures—historically a recurring complaint among Windows 10 users and administrators.

Known Issues: Noto Fonts and CJK Clarity​

One notable ongoing issue, first introduced in the March 2025 Preview Update, is blurry or unclear CJK (Chinese, Japanese, Korean) text rendered in Chromium-based browsers at 96 DPI. This is particularly relevant for users in Asian markets and for international organizations. The new default Noto fonts, partnered between Microsoft and Google, are utilized as fallbacks, but in low-DPI scenarios (100% scaling), lack the clarity of earlier default fonts. While increasing system display scaling (125% or 150%) can improve clarity, users demanding precise character rendering may still find the workaround unsatisfactory.
Crucially, Microsoft acknowledges this as an active investigation, promising further updates as their font rendering engineers identify root causes and develop a lasting solution.

Issue	Affected Component	Temporary Fix	Status
Blurry CJK Text in Browsers	Noto Fonts w/ Chromium (Edge, Chrome) @ 96 DPI	Increase display scaling to 125% or 150%	Under investigation

How to Get the June 2025 Update​

Obtaining KB5061087 is straightforward for most users:

• Via Windows Update (Home/Pro/Enterprise): Found under “Optional updates available” in Settings > Update & Security > Windows Update.
• Via Update Catalog: IT admins or advanced users can download the standalone package for manual installation from the Microsoft Update Catalog.
• Via Windows Server Update Services (WSUS): Admins can import and deploy the package across managed endpoints.
• Note: Some deployments, particularly those not previously updated with certain LCUs or SSUs, may require special standalone prerequisite installations—a point often overlooked by less-experienced administrators.

Removal of the update, if necessary, must be done using the DISM/Remove-Package command, as the more familiar Windows Update Standalone Installer (wusa.exe) cannot uninstall combined update packages that also include the SSU. This change is a direct result of the newer servicing model introduced in late Windows 10 development cycles.

Strategic and Technical Analysis​

Strengths and Positive Trends​

• Continued Support for Legacy Devices: Microsoft’s willingness to address niche issues (such as dual-protocol scanning and COM remote activation) reinforces its commitment to supporting the broad and varied hardware ecosystem that defines Windows 10’s massive install base.
• Enterprise Readiness and Transparency: Detailed, well-documented update notes, along with explicit DMA compliance changes, suggest a strong focus on enterprise assurance as organizations plan migration and compliance strategies.
• Bundled SSU Approach: Coupling the latest servicing stack improvements with the monthly update reduces the support burden for IT staff, limiting classic "update cannot be installed" errors that previously plagued some cumulative update cycles.
• Proactive Disclosure of Known Issues: By openly documenting the Noto font rendering case, Microsoft enables IT teams and users to make informed decisions, seek workarounds, or delay adoption as appropriate.

Potential Risks and Weaknesses​

• Imminent End-of-Support Pressure: The 2025 sunset on Windows 10 support leaves organizations with little time to address legacy application or hardware compatibility with Windows 11. The risk is particularly acute for those with specialized hardware, regulatory constraints, or highly customized deployments.
• Font Rendering Backlash in East Asia: The ongoing Noto font issue, while minor for global users, represents a substantial hurdle for Chinese, Japanese, and Korean-speaking users. If unresolved, it could accelerate user frustration or demands for third-party font management.
• DMA-Compliant Browser Pinning May Cause Confusion: Automatic pinning of new browsers to the taskbar and Start menu, though mandated by European law, diverges from long-standing Windows behavior. Users may find their environments subtly altered following browser switches, especially in managed environments with strict desktop layouts.
• Complex Prerequisite Chains for Offline or WSUS Deployments: The need for specific, earlier LCUs and SSUs as prerequisites for some update scenarios could confound less experienced IT admins, risking incomplete deployments or inconsistent fleet states, particularly in large or air-gapped networks.

Comparative Industry Context​

Other major OS vendors facing EOL (End of Life) milestones—Apple with macOS, Google with Chrome OS version drops—often take cues from Microsoft’s playbook or, alternately, expose its weaknesses. Apple, for example, is known for quickly dropping support for older hardware, pushing users to newer devices and operating systems, but faces criticism over legacy software gaps. Microsoft’s more gradual pattern, with lengthy notification windows and clear “soft landings” via sustained Cumulative Updates, is widely considered best-in-class, even as it presents unique ongoing management burdens and occasionally complex update logistics.

Windows 10: What Next?​

The June 2025 update preview for Windows 10, version 22H2, exemplifies the OS’s twilight year: stable, mature, and relentlessly focused on ironing out the operational details that still matter to millions of remaining users. But the message is clear. With the October 2025 deadline rapidly approaching, the transition to Windows 11 becomes not just a recommendation, but a requirement for security and ongoing usability.
For users and administrators: now is the time to audit application compatibility and hardware requirements, focusing especially on TPM and Secure Boot prerequisites for Windows 11. The June 2025 preview update should be seen as a final quality pass, not an invitation to delay inevitable migration.

Conclusion: Stability, Transparency, and the March to Legacy​

KB5061087 doesn’t revolutionize Windows 10, but it exemplifies Microsoft’s steady hand in its final act of support. The focus on fixing regressions, enhancing compliance, and addressing real-world user and enterprise pain points is a testament to Windows 10’s lasting importance—even as its days become numbered.
Moving forward, the success or failure of Microsoft's approach to end-of-life management will hinge on clear communication, effective rollout of final updates, and a transparent handling of edge cases like the Noto font controversy. Organizations must take heed: these updates are the last reliable opportunity to firm up Windows 10 environments before unsupported status and the full shift to Windows 11.
In this context, KB5061087 is both an end and a beginning—a marker of Windows 10’s mature reliability and a signal to prepare for its inevitable sunset.

---

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