Windows 10 KB5061087 Update: Final Enhancements Before Support Ends

As Microsoft edges closer to the end of mainstream support for Windows 10, the June 2025 non-security preview update—KB5061087, OS Build 19045.6036—delivers critical quality improvements aimed at stabilizing the user experience for those committed to Windows 10 version 22H2 across Home, Pro, Enterprise, Education, and IoT flavors. With the official support cutoff slated for October 14, 2025, these final rounds of updates represent a crucial bridge for users and enterprises transitioning—or hesitating to transition—to Windows 11. But what, precisely, does this latest update bring to the table, and how should users assess its impact amid the broader lifecycle of Microsoft’s flagship OS?

Navigating the Final Stretch: Windows 10 Update Context​

Microsoft’s release of KB5061087 lands at a time of change and uncertainty for millions of users. With less than four months left before the product enters its end-of-life phase, every update carries heightened significance. Importantly, this release underscores that Microsoft remains committed to its promise of monthly, cumulative improvements for Windows 10 until the very end, even as the drumbeat of Windows 11 adoption continues.
Before diving into the nitty-gritty of the update, it’s important to recognize the unique context for both home users and organizations. While consumers are gently nudged toward Windows 11, enterprises—often supporting massive device fleets—are watching these updates closely for security, compatibility, and operational stability. This update, as with previous cumulative releases, focuses on resolving reliability snags, squashing persistent bugs, and subtly tweaking the user experience to comply with evolving regulations, especially in the European Economic Area.

What’s Inside KB5061087: Core Improvements and Notable Fixes​

The June 2025 update is categorized as a “non-security” release, but its breadth covers areas often deeply felt by users and IT managers alike. Here’s an in-depth look at the key changes and their implications:

Mobile Operator Profile Updates​

Microsoft has updated the Country and Operator Settings Asset (COSA) profiles, a relatively under-the-hood change that will mostly benefit users who rely on cellular connectivity, such as in laptops with LTE/5G capabilities. These profiles determine how Windows interacts with mobile networks for connectivity, roaming, and SMS features. For global enterprises or users frequently moving between networks and regions, such updates can help ensure connection reliability and compliance with evolving telecom standards.

App Platforms, Frameworks, and Critical Tools​

Fixes for COM (Component Object Model) Functionality​

Component Object Model (COM) is a legacy yet vital backbone for inter-process communication in Windows. The update addresses an error (0x8001011) that was causing remote COM activations to fail. In enterprise environments where distributed applications or legacy automation scripts rely on COM, this fix resolves critical workflow interruptions. Independent verification via forums such as Microsoft Q&A and official documentation confirm that this was a long-standing pain point for automation-dependent setups.

Curl Tool Update​

The update also refreshes the version of curl—a widely used command-line tool for transferring data with URLs—to version 8.13.0. This change, confirmed on the official curl changelog, offers improved security, performance, and protocol compatibility, particularly in scenarios involving automated data transfers and cross-platform scripts. For scripters and IT admins, keeping core tools current is more than convenience: it’s a safety net against known vulnerabilities and incompatibilities.

Authentication and Account Management​

Entra ID Registration Fixes​

Microsoft has resolved an issue affecting device registration in the Entra ID Windows Account Manager (WAM) plugin. Entra ID (formerly Azure AD) powers much of Microsoft’s current identity and access management strategy. The issue previously caused hiccups during device onboarding, impeding organizations’ zero-trust rollouts and hybrid work initiatives. According to security experts and Microsoft’s own documentation, robust device registration is foundational for enforcing secure, compliant access to resources.

Input, Composition, and Language Management​

One significant fix targets a nagging problem with the removal of unused language packs and Features on Demand (FOD). Before this update, these leftovers could consume disk space and slow future update times, a particularly acute annoyance in environments with aggressive language management or frequent OS refresh cycles. The update promises not only tighter storage hygiene but also a smoother upgrade path for organizations deploying custom or multilingual images.

Print and Peripheral Support​

Printing issues are a perennial thorn in the side of Windows users. This release tackles a bug where USB-connected multi-function printers—specifically those with dual protocol interfaces—were failing to scan, often blocking access to the built-in scanning modules of the operating system. For small businesses and educational institutions, reliability of scanning and printing functions is not just convenience, but a workflow necessity. Community threads and feedback from major printer vendors have corroborated the prevalence of these scanning failures, making this fix a welcome relief.

Start Menu and UI Improvements​

The Start Menu remains a central user interface element and is the focus of two critical bug fixes:

• Jump Lists Disappearance: The restoration of jump lists—contextual menus accessible from pinned icons—will help return continuity to task switching and productivity.
• Start Menu Launch Failure: Not being able to open Start after installing updates was a high-visibility issue, hampering user navigation immediately post-update. With this fix, users regain confidence that critical navigation tools will remain reliable across update cycles.

WinSaS, Browser Default Behavior, and DMA Compliance in the EEA​

Version Reporting Correction​

Whereas previously the Settings > System > About page mistakenly showed version “2009” instead of “22H2,” this minor correction is more than cosmetic—it’s essential for IT managers tracking device health and compliance.

Default Browser Handling (EEA DMA Compliance)​

A more significant change is the behavioral shift to maintain DMA (Digital Markets Act) compliance in the European Economic Area. When a new default browser is selected, Windows 10 will now auto-pin it to the Taskbar and Start menu, and associate it with HTTP and .pdf file types. This is a direct response to regulatory demands to promote browser choice and counter historic “default browser bias.” It’s a notable example of regulation shaping OS design, and a signpost for non-EEA users about potential future changes as legislative landscapes evolve worldwide.

Servicing and Device Management​

Kiosk Mode Reliability​

For organizations running public terminals or controlled environments (e.g., kiosks), stability is paramount. Microsoft has resolved an issue where devices under ForceAutoLogon and Shift Override configurations could trigger blue screens after a lock/unlock sequence. This fix takes on outsized importance in retail, healthcare, or educational settings, where disruptions translate directly into service downtime.

File Server Stability​

Finally, in the file services realm, the update addresses a rare but impactful bug where the system could hang when acknowledging an Oplock (Opportunistic Lock) break on SMB shares. Such situations, while uncommon, pose significant risk to data integrity and service availability—particularly in high-throughput, shared storage environments.

Quality Improvements to the Servicing Stack​

The update also delivers a new servicing stack update, KB5061902 (build 19045.6035), now bundled with the LCU for a streamlined experience. Servicing stack updates are vital for improving the robustness and reliability of future updates. Microsoft’s practice of combining the latest SSU with the primary cumulative update helps reduce update friction and eliminates a longstanding pain point where missing an SSU could block future patches or produce arcane errors during the update process.

Known Issues: Noto Fonts and CJK Clarity​

No software update is without its pitfalls, and Microsoft is transparent about a notable known issue in this release: the rendering of Noto fonts for CJK (Chinese, Japanese, Korean) characters at 96 DPI (100% scaling) in Chromium-based browsers. Many users are reporting blurry or unclear text, a direct outcome of the March 2025 Preview Update which introduced Noto fonts as fallbacks to improve font selection in cases where websites don’t specify suitable CJK fonts.
The root of the problem is that at standard DPI, the pixel density is too low for some glyphs to be rendered sharply. The recommended temporary fix is to increase display scaling to 125% or 150%, which significantly improves clarity but could frustrate users accustomed to legacy scaling and desktop layouts. While Microsoft and Google are actively investigating, those reliant on razor-sharp multilingual text should consider this limitation before updating, especially in environments with significant CJK user bases.

How to Obtain and Manage the Update​

Installation Guidance​

For most individual users, the update is straightforwardly available under the “Optional updates available” section in the Windows Update settings. Power users, IT professionals, and those managing offline images or enterprise deployments should be mindful of prerequisite sequence dependencies. Specifically, if an image lacks the July 2023 LCU or certain earlier SSUs, manual installation steps are necessary to bring the system current.
The update is also available via the Microsoft Update Catalog and can be imported into Windows Server Update Services (WSUS) for network-wide distribution. Removal protocols, however, have become slightly more rigid—in line with the combined SSU+LCU package structure, uninstalling only the LCU (leaving the SSU) requires careful use of the DISM /Remove-Package tool, and the old wusa.exe approach no longer supports full removal.

Enterprise Readiness​

Enterprises and managed environments must carefully test the update before broad deployment, given the short runway to end-of-support and the critical fixes involved. Compatibility, particularly with in-house applications relying on COM, printing, device registration, and kiosk features, warrants particular scrutiny. Consulting Microsoft’s official deployment documentation and community forums is advised before mass rollout.

Critical Analysis: Strengths, Limitations, and the Big Picture​

Strengths and High Points​

• Comprehensive Bug Fixes: This update delivers a genuinely useful set of fixes targeting not just esoteric edge cases, but also high-impact productivity and device stability issues. The addressal of longstanding COM and kiosk mode bugs stands out.
• Regulatory Responsiveness: The DMA-compliant browser behavior signals Microsoft’s willingness to adapt to shifting regulatory environments, a plus for organizations operating across multiple legal jurisdictions.
• Servicing Stack Evolution: The seamless bundling of SSU with LCU marks a major pain point resolved—a particularly significant administrative simplification as organizations navigate the final miles of Windows 10 deployment.
• Transparency Around Known Issues: Microsoft’s early and explicit flagging of the Noto fonts CJK rendering problem, including an immediate workaround, is a model for vendor transparency.

Limitations and Risks​

• Short Window to End-of-Life: With support ending in October 2025, this and subsequent updates represent stopgaps rather than futureproofing. The risk of late-breaking compatibility or security issues will only grow as Windows 10 sunsets.
• Font Rendering Issues for East Asian Users: The Noto font issue, though acknowledged, is not trivial for users heavily reliant on East Asian languages, and no short-term fix is available beyond increasing display scaling—a potential workflow disruptor.
• Complexity for Legacy and Offline Installations: The process for updating legacy offline images, or handling environments with dormant servicing stack versions, remains intricate. Without careful sequencing, organizations may find themselves locked out of receiving critical fixes.
• No New Features: As with most post-mainstream-support updates, this release focuses strictly on maintenance. Users hoping for new features, performance leaps, or expansive UI improvements will need to look to Windows 11 and beyond.

End-of-Support Countdown: What Next for Windows 10 Users?​

Microsoft’s messaging is unequivocal: after October 14, 2025, no further free software updates, technical support, or security fixes will be delivered for Windows 10. From that point forward, use of Windows 10 will be at the user’s (or organization’s) own risk. While the OS will continue to function, running critical infrastructure on unsupported software is increasingly untenable from a security and compliance perspective.
For enterprises not ready to migrate, Microsoft is expected to offer paid Extended Security Updates (ESU), as it did with Windows 7, but at a cost and with strict eligibility requirements. Most households and small businesses, however, must now seriously consider scheduling hardware and software migration to Windows 11—a process that can require months of planning and testing, especially for older hardware or specialized vertical market applications.

Actionable Recommendations​

• Apply This Update Promptly: Especially for users impacted by print, COM, kiosk, or device registration issues, and for those needing to ensure browser behavior compliance in the EEA.
• Test Font Rendering Post-Update: In CJK-intense environments, verify that text appears sharp enough for your use case, and consider the scaling workaround where necessary.
• Check Update Prerequisites: For offline or enterprise image management, confirm that all servicing stack and cumulative update sequences are in place to avoid install errors.
• Plan Your Migration: With the end of Windows 10 support looming, begin inventorying systems and mapping out your move to Windows 11 or alternate supported operating systems.

Conclusion​

KB5061087 is emblematic of Microsoft’s steady, no-nonsense approach to sunsetting its long-reigning Windows 10 platform. The update prioritizes quality and compliance fixes over flashy features, and in doing so, helps enterprises and consumers alike navigate the final few months of official support with increased confidence. Still, the ongoing Noto font challenge is a reminder that even as one era ends, the complexity of global user needs remains a moving target.
As October 2025 fast approaches, users and organizations must weigh immediate stability against the urgent need to migrate forward. This update, and those like it, are not only patches—they are mile markers on the road to the next phase in desktop computing. Actively engaging with these updates, understanding their implications, and embracing readiness for what comes next will position all users ahead of the impending Windows 10 sunset.

---

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