Windows 10 KB5061087: Final Preview Update Before October 2025 End of Support

As Windows 10 approaches its October 14, 2025 end-of-support deadline, Microsoft continues to deliver meaningful refinements through its June 2025 non-security preview update, KB5061087 (OS Build 19045.6036). This update represents one of the final opportunities for users and organizations to receive quality improvements before Windows 10 transitions to unsupported status, making it particularly significant for the millions still running Microsoft's most widely deployed operating system.

The Context: Windows 10's Final Year

Windows 10, version 22H2, remains the final feature update before extended support ceases in October 2025. According to Microsoft's official lifecycle documentation, after this date, the company will no longer provide free security updates, technical assistance, or new fixes for Windows 10 devices. This looming deadline frames every 2025 update as potentially the last opportunity to secure reliability and compatibility fixes before official patches cease entirely.

The preview update model, which includes KB5061087, represents Microsoft's ongoing commitment to operational stability and user experience during this transition period. These non-security releases offer quality improvements, fixes, and feature adjustments ahead of the broader "Patch Tuesday" security updates, allowing users to opt-in and businesses to test changes before widespread deployment.

Key Improvements in KB5061087

Mobile Connectivity Enhancements

Microsoft has updated the Country and Operator Settings Asset (COSA) profiles in this release. These profiles enable Windows to connect reliably to various mobile operator networks worldwide. For enterprise users leveraging Windows 10 in field devices or mobile environments, this update helps maintain seamless connectivity, potentially improving roaming capabilities and reducing connectivity issues with new or updated mobile network infrastructure.

App Platform and Framework Fixes

One significant technical fix addresses a Component Object Model (COM) bug affecting remote activations. Users and developers had been experiencing remote COM activation attempts failing with error 0x8001011, which could disrupt the functioning of distributed applications reliant on COM inter-process communication. This fix is particularly important for enterprise environments running legacy applications that depend on COM technology.

The update also includes an upgrade to the built-in curl tool to version 8.13.0. Curl is a fundamental open-source tool for transferring data with URLs, widely used in scripting and automation. According to the official curl changelog, this version introduces bug fixes and improved handling for various protocols, providing valuable improvements for IT professionals and scripts running directly from Windows consoles.

Authentication Platform Corrections

Microsoft has fixed device registration issues with Entra ID (formerly Azure Active Directory) through Windows Account Manager (WAM). Entra ID is foundational for enterprise authentication, and registration failures could delay or block device onboarding in managed environments. This fix restores confidence in trust management and IT deployment pipelines, ensuring smoother enterprise device management during Windows 10's final operational year.

Input and Composition Improvements

The update resolves an issue with the removal of unused language packs and Feature on Demand (FOD) packages. Previously, stale language packs or FODs would linger, wasting disk space and inflating update times. For users managing diverse, multilingual environments, this represents a significant quality-of-life improvement that helps maintain system efficiency.

Peripheral and Printing Fixes

A particularly impactful fix addresses USB-connected multifunction printers with dual protocol interfaces that could not scan. 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, making this fix crucial for maintaining productivity.

Start Menu Reliability

Microsoft has addressed two critical Start Menu issues in this update. First, the disappearance of Start Menu jump lists—which provide shortcuts to frequently accessed files and commands—has been resolved. Second, some Start Menus not opening after updates has been fixed. This rare but critical regression could leave devices functionally unusable if the primary navigation interface was broken after update installation, making this fix essential for system stability.

DMA Compliance and Browser Management

In response to European Economic Area (EEA) regulations, Microsoft has implemented DMA (Digital Markets Act) compliance updates for browsers. Whenever a new default browser is set, it now pins itself automatically to both the Taskbar and Start menu. This strengthens compliance with EU DMA requirements, striving for browser choice transparency. Additionally, HTTP and .pdf files now properly associate with the selected default browser, preventing inadvertent fallback to Microsoft Edge.

Enterprise and Server Improvements

For enterprise environments, Microsoft has corrected an issue where "Settings > System > About" was showing version 2009 instead of 22H2. While cosmetic, accuracy in version labeling helps IT departments properly inventory and support devices. The update also fixes a blue screen issue on kiosk devices using ForceAutoLogon and Shift Override, which is crucial for managed kiosk devices used in point-of-sale or public terminal settings.

On the server side, Microsoft has 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, maintaining business continuity.

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. This approach represents Microsoft's effort to streamline the update process during Windows 10's final year of support.

Known Issues: Font Rendering Challenges

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. Microsoft acknowledges this as an active investigation, promising further updates as their font rendering engineers identify root causes and develop a lasting solution.

Deployment and Management Considerations

Installation Methods

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

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 Considerations

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 Analysis: Strengths and Challenges

Positive Developments

Microsoft's continued support for legacy devices through niche fixes (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. The 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.

The bundled SSU approach, coupling the latest servicing stack improvements with monthly updates, reduces the support burden for IT staff, limiting classic "update cannot be installed" errors that previously plagued some cumulative update cycles. Additionally, proactive disclosure of known issues like the Noto font rendering case enables IT teams and users to make informed decisions, seek workarounds, or delay adoption as appropriate.

Potential Risks and Concerns

The imminent October 2025 end-of-support deadline 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. The ongoing Noto font issue, while minor for global users, represents a substantial hurdle for Chinese, Japanese, and Korean-speaking users and could accelerate user frustration if unresolved.

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. Additionally, complex prerequisite chains for offline or WSUS deployments could confound less experienced IT admins, risking incomplete deployments or inconsistent fleet states, particularly in large or air-gapped networks.

Migration Imperatives and Planning

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. Organizations should now be actively auditing 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.

According to industry analysis, organizations that delay migration face increasing security risks and potential compliance issues once Windows 10 reaches end of support. Microsoft's extended security update (ESU) program will be available for purchase for up to three years after the end of support, but this represents additional cost and complexity compared to timely migration.

Conclusion: A Mature Platform's Final Refinements

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. This update represents Microsoft's commitment to maintaining stability and reliability for the millions of users and organizations still dependent on Windows 10 as they plan their transition to newer platforms.

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 transparent handling of edge cases like the Noto font controversy. Organizations must recognize that these updates represent the last reliable opportunity to firm up Windows 10 environments before unsupported status and the full shift to Windows 11 becomes unavoidable.

In this context, KB5061087 serves as both an end and a beginning—a marker of Windows 10's mature reliability and a clear signal to prepare for its inevitable sunset. As the final preview update before the October deadline, it represents Microsoft's last substantial quality improvements for an operating system that has served billions of users worldwide.