Microsoft has significantly sweetened the deal for consumers clinging to Windows 10 past its October 14, 2025 end-of-support date—but there’s a new string attached. The company now confirms that a single $30 Extended Security Updates (ESU) license will protect up to 10 devices logged into the same Microsoft Account, a dramatic improvement over the originally implied per-device cost. However, the flip side is that a Microsoft Account is mandatory for enrollment, even if you’re paying cash. This double-edged update, rolled out quietly through support documentation, reshapes the calculus for the estimated hundreds of millions of users still running Windows 10 as they face a looming security cliff and a confusing landscape of browser versus OS support timelines.

The larger backdrop remains Windows 10’s hard end-of-support date: October 14, 2025. After that, Microsoft will stop issuing free security updates, feature improvements, or technical support for the aging OS. The primary path forward is upgrading to Windows 11, but for those unable or unwilling to do so, ESU provides a lifeline. Crucially, Microsoft has also decoupled the lifecycles of Microsoft Edge and the WebView2 runtime from the OS itself. Even without ESU, Edge and WebView2 will continue receiving updates on Windows 10 22H2 until at least October 2028, aligning with the end of the ESU program. This means web-based components inside desktop apps—like Progressive Web Apps (PWAs) and hybrid applications—stay patched, even as the operating system beneath them rots.

The ESU Program Gets a Quiet Upgrade—And a New Requirement

The Windows Central report clarifies that the ESU enrollment window, which began rolling out in July, now requires sign-in with a Microsoft account regardless of enrollment method. Users have three options: a $30 one-time purchase, redeeming 1,000 Microsoft Rewards points, or linking OneDrive backup of Windows settings for free enrollment. But all three now demand the account. Microsoft’s support document states plainly: “You will need to sign into your Microsoft account in order to enroll in ESU.” This ties the license to the account, enabling the multi-device perk: one license can cover up to 10 devices that sign in with that same account. Each device still needs individual enrollment, but the fee is not repeated.

This revelation changes the value proposition dramatically for families and small businesses. Originally, the $30 price was widely interpreted as a per-device cost, which would have added up quickly for users with multiple aging PCs. Now, a single $30 purchase shields an entire household’s worth of Windows 10 machines for one additional year of security patches—through October 13, 2026. For those who’ve already embraced Microsoft’s ecosystem with a single account, the savings are real. But for privacy-conscious users who’ve studiously avoided linking a Microsoft Account to their local Windows login, this requirement feels like a forced ultimatum: trade privacy for protection.

Enrollment itself is rolling out in waves. If your Windows 10 device meets prerequisites, you’ll see an “Enroll now” link in Settings > Update & Security > Windows Update. Those signed in with a local account will be prompted to switch to a Microsoft Account. The process is straightforward, but the psychological barrier may still deter a significant minority.

Edge and WebView2: The Browser That Outlasts the OS

While the ESU drama unfolds, a separate but equally critical timeline is at play. Microsoft’s Edge lifecycle documentation makes clear that Microsoft Edge and the WebView2 Runtime will continue to receive updates on Windows 10, version 22H2, until at least October 2028. Critically, enrollment in ESU is not required to keep getting these browser and runtime patches. This decoupling is a pragmatic acknowledgment that modern apps rely heavily on embedded web components, and pulling the plug on their security updates would be too disruptive.

What does this actually protect? Edge and WebView2 updates primarily patch the Chromium-based browser engine (Blink and V8), renderer-level bugs, and web-facing vulnerabilities. For organizations that depend on line-of-business apps embedding WebView2, or on PWAs installed via Edge, these updates keep the most common web attack surface patched. That means less pressure to migrate purely for web-security reasons. Hardware that can’t run Windows 11 but runs a critical WebView2-based application can, in theory, keep functioning securely from a web perspective until 2028.

But there’s a decisive caveat: no amount of browser patching fixes the underlying OS. After October 14, 2025, Windows 10 will receive no more kernel security updates, driver fixes, firmware patches, or platform-level mitigations against privilege escalation or sandbox escapes. An attacker might still use a kernel exploit to break out of Edge’s sandbox, even if Edge itself is fully up to date. The extended Edge/WebView2 support reduces one slice of risk—the web vector—but leaves a gaping hole at the operating system level. It’s a tactical buffer, not a strategic solution.

Compliance and Risk: Why Enterprises Can’t Ignore the OS EoL

For regulated industries, the OS end-of-support remains a hard compliance deadline. Auditors and regulators expect fully supported platforms, especially on systems that handle sensitive data. Extended browser servicing does not satisfy those requirements. Even with Edge patches flowing until 2028, a Windows 10 machine after October 2025 will often be flagged as non-compliant. The ESU program adds one year of OS patches, but only for enrolled devices. That extension might buy time for audit negotiations, but it doesn’t remove the ultimate need to migrate.

Third-party software vendors also watch Microsoft’s lifecycle announcements closely. Many ISVs will align their support policies with the OS EoL, not the browser lifecycle. Enterprises should gather vendor roadmaps now to avoid being blindsided by dropped support. Procurement teams can use the Edge/WebView2 extension to spread hardware replacement costs across multiple budget cycles, but they must weigh the security debt of lingering on an unsupported OS. Increasingly, cyber insurance policies may require supported operating systems, and claims could be denied after an incident if the OS was EoL.

A Tactical Migration Playbook

The right course depends on exposure and risk tolerance, but a structured approach helps:

  • Immediate actions (next 30–90 days): Inventory all Windows 10 devices and identify those running 22H2 versus older builds. Catalog applications that depend on WebView2 or Edge PWAs. Use the PC Health Check tool to assess Windows 11 compatibility. For ineligible hardware, determine whether upgrades (SSD, RAM) or replacement is needed.
  • Short-to-medium term (3–12 months): Prioritize internet-facing endpoints and systems handling sensitive data for OS upgrades or hardware refresh. For devices that can’t migrate, consider enrolling in ESU (if Microsoft Account linkage is acceptable) and beef up endpoint detection and response. Apply network segmentation to limit the impact of a potential compromise on unpatched systems.
  • Long-term (12–36 months): Plan permanent migrations off Windows 10. Even with ESU, running an end-of-life OS indefinitely is not sustainable. By 2028, when Edge updates cease, you should have fully transitioned to supported platforms. Update contract language with vendors and insurers to account for the transition period.

Home users with compatible hardware should simply upgrade to Windows 11—it’s free and the least risky path. The ESU is best viewed as a stopgap for machines that can’t upgrade immediately, like an old family PC running a legacy app that isn’t yet ready for Windows 11. But treat the October 2025 date as the real deadline; the extra years of Edge updates are a safety net, not a hammock.

Strengths of Microsoft’s Approach—and Where It Falls Short

Microsoft earns credit for clarity. The explicit commitment that Edge and WebView2 updates will continue on Windows 10 22H2 through at least October 2028 provides a concrete timeline for planning. The decoupling prevents panic among developers and enterprises whose apps rely on modern web runtimes. The multi-device ESU licensing is also a surprisingly consumer-friendly move, especially for households with multiple devices.

But the forced Microsoft Account requirement sours the deal for many. It adds friction and forces a philosophical choice on users who prefer local accounts. From a technical standpoint, the broader risk remains: after October 2025, Windows 10 will be a cemetery for OS-level bugs. The headline “Edge supported until 2028” can lull organizations into complacency, overlooking the fact that a fully patched browser on an unpatchable OS is still dangerously exposed.

What to Watch in the Coming Months

Third-party browser vendors like Google and Mozilla may release their own Windows 10 support timelines. Assuming parity with Microsoft’s Edge commitment would be speculative. Organizations should monitor vendor announcements rather than infer alignment. Meanwhile, ESU enrollment specifics—including any last-minute pricing or policy changes—remain fluid. Confirm the latest through official Microsoft channels and your device’s Windows Update settings.

Final Analysis

Microsoft’s $30 ESU now covering 10 devices is a genuine perk for multi-PC households, but the mandatory Microsoft Account is a bitter pill. The separate Edge/WebView2 extension through 2028 gives organizations breathing room to migrate methodically, but it cannot mask the fact that Windows 10’s OS-level support ends in October 2025. The optimal strategy uses this extra time deliberately: inventory, prioritize, and migrate in a way that reduces both technical debt and exposure. Treat Edge’s extended servicing as a tactical buffer, and plan permanent migrations or hardware refreshes to restore full platform-level protection before the clock runs out.