Edge and WebView2 Updates on Windows 10 22H2 Extend to October 2028

Microsoft has quietly clarified that its Chromium-based Microsoft Edge browser and the Microsoft WebView2 Runtime will continue to receive updates on machines running Windows 10, version 22H2 for substantially longer than the operating system’s own end-of-support date — through at least October 2028. (learn.microsoft.com)

Background​

Windows 10’s mainstream lifecycle reaches a hard stop on October 14, 2025, when Microsoft will end mainstream technical support and stop shipping regular security and feature updates for the OS itself. (support.microsoft.com)
That milestone prompted confusion and concern across consumers and enterprises: if the OS is out of support, will critical apps and online services continue to work safely on older Windows 10 devices? Microsoft’s update to the Microsoft Edge Lifecycle Policy directly addresses one part of that question by confirming Edge and WebView2 updates for Windows 10 22H2 will continue until at least October 2028 — a three-year extension beyond the OS end-of-support date. (learn.microsoft.com)
Third‑party technology publications that track Microsoft’s lifecycle announcements picked up and amplified the guidance, noting the practical implications for users who plan to remain on Windows 10 after 2025. (windowscentral.com, borncity.com)

---

What Microsoft actually said: the hard facts​

• Microsoft Edge and WebView2 updates for Windows 10, version 22H2, will continue until at least October 2028. This is stated in the Microsoft Edge Lifecycle Policy. (learn.microsoft.com)
• Windows 10 itself reaches end of support on October 14, 2025. After that date Microsoft stops regular security and quality updates for the OS unless a device is enrolled in an ESU program. (support.microsoft.com)
• Extended Security Updates (ESU) remain available as a paid option to receive critical security fixes beyond October 14, 2025; enterprise customers can extend support for up to three years (through 2028) under the ESU program, while consumer ESU options and timelines differ. (learn.microsoft.com, support.microsoft.com)
• Microsoft explicitly states ESU is not required to continue receiving Microsoft Edge or WebView2 updates on Windows 10 22H2. In practice, Edge updates will be provided to devices even if they do not participate in ESU. (learn.microsoft.com)

These are the most important operational facts for users and IT teams planning the next 12–36 months.

---

Why Edge and WebView2 matter after Windows 10’s end of support​

Browsing security and modern web compatibility​

Edge is the default browser on Windows and serves as a critical portal to the web. Keeping Edge updated on Windows 10 has three primary benefits:

• Security fixes — browser vulnerabilities are frequently exploited; ongoing updates reduce exposure to web-based threats.
• Engine parity with Chromium — Edge’s frequent updates keep it aligned with modern web standards, which improves site compatibility and PWA (Progressive Web App) behavior.
• Feature and performance improvements — while not strictly security-related, ongoing feature updates can improve user experience and mitigate compatibility gaps.

WebView2 is even more consequential in the enterprise context. It’s the runtime used by many Windows apps to embed web content. Continued WebView2 updates mean those host applications retain access to updated web platform security and APIs — even if the underlying OS is no longer receiving feature updates. Microsoft’s policy confirming updates for WebView2 on Windows 10 22H2 therefore reduces one important vector of application breakage and risk. (learn.microsoft.com)

---

The ESU context: who can get what, and when​

Microsoft’s Extended Security Updates (ESU) program enables customers to keep receiving critical security patches for Windows 10 beyond October 14, 2025. The ESU program has several permutations and timelines:

• Consumer ESU: Microsoft published a consumer ESU option and specific enrollment details that allow individual users to receive updates for a limited period after the 2025 EOL. The consumer ESU program has its own enrollment and end dates and is not required to receive Edge updates. (support.microsoft.com)
• Commercial/Enterprise ESU: Organizations can purchase ESUs in up to three consecutive annual increments. The enterprise ESU option effectively enables security patching through October 2028 when fully applied across the three‑year window. Microsoft’s enterprise ESU pricing model follows a per-device structure with a stepped price that increases in subsequent years. (learn.microsoft.com)

Note that while ESU covers OS-level security updates, Microsoft has stated that Edge and WebView2 updates will not require ESU participation. That distinction is central: you can still receive browser and WebView2 updates even on Windows 10 devices not enrolled in ESU — but the OS will otherwise be out of security servicing unless enrolled. (learn.microsoft.com)

---

What this means for users and IT administrators​

Practical implications for consumers​

• If you plan to continue using Windows 10 22H2 past October 2025, your Edge browser will still receive updates and security fixes through at least October 2028, reducing the immediate risk from browser-based attacks. (learn.microsoft.com)
• The operating system itself will not get general security updates after October 14, 2025 unless you enroll in an ESU plan; that means kernel-level vulnerabilities, driver issues and OS components remain at risk. (support.microsoft.com)
• Consumer ESU enrollment options and dates differ from enterprise ESU; individual users should review Microsoft’s consumer ESU policy and enrollment windows to confirm eligibility and costs. (support.microsoft.com)

Practical implications for enterprises​

• IT departments gain breathing room for web-facing security by keeping Edge and WebView2 updated on existing Windows 10 22H2 machines. That can be particularly valuable for application compatibility testing and staged migrations to Windows 11 or cloud-based Windows 365 solutions. (learn.microsoft.com)
• However, enterprises must weigh the residual risk: drivers, third-party software, and OS-level subsystems will not receive non-ESU patching. If maintaining a secure environment is critical, ESU enrollment (paid) remains the official path for OS-level protection through 2028. (learn.microsoft.com)
• Organizations should also confirm vendor support policies: hardware drivers and ISV (independent software vendor) products may stop supporting Windows 10 even if Edge remains serviced.

---

Strengths of Microsoft’s approach​

• Targeted mitigation for web risk: By decoupling Edge/WebView2 updates from OS lifecycle, Microsoft addresses one of the highest-risk components for attackers — browsers and embedded web runtimes — without necessarily extending full OS support.
• Consistency for app developers: WebView2 updates give developers predictable, modern web platform capabilities inside desktop apps, reducing churn and compatibility drift as Windows 10 declines.
• Easier transition path: Organizations that need more time to validate hardware compatibility with Windows 11 get a partial safety net that eases migration timing.

These moves reduce short-term exposure for users who cannot or will not upgrade immediately, and they acknowledge the reality that large numbers of devices will continue to run Windows 10 for years after EOL.

---

Risks, caveats, and unanswered questions​

• OS-level vulnerabilities remain: Edge updates mitigate browser-based exploits, but a non-patched OS surface (drivers, kernel, system services) remains attractive to attackers. Relying solely on browser updates is insufficient for comprehensive security. (support.microsoft.com)
• Third-party support is uncertain: Browser vendors such as Google (Chrome) and Mozilla (Firefox) may maintain their own support timelines for Windows 10, but they aren’t bound to Microsoft’s policy. Continued third-party browser support on Windows 10 is likely but not guaranteed. Publications note that this is unclear and may differ by vendor. (windowscentral.com)
• Hardware and driver compatibility: New peripheral drivers and firmware updates are unlikely to be backported to an EOL OS. Over time, hardware vendors will shift focus to Windows 11 and newer platforms, which can break functionality on aging Windows 10 machines.
• Edge updates can’t fix everything: Many threat vectors operate at the OS, firmware, or network level; Edge updates reduce web-triggered risks but do not replace full OS security servicing.
• Potential complexity for compliance: Organizations with regulatory obligations may find the mixture of Edge updates plus OS EOL complicates compliance posture (e.g., requirements about supported OS versions or patching policies).

Where Microsoft’s policy reduces specific risks, it does not eliminate the broader security and maintenance burden of running an unsupported OS.

---

Recommended actions and migration checklist​

The following is a prioritized, practical checklist for users and administrators navigating Windows 10’s end-of-support while benefiting from Edge/WebView2 updates.

• Inventory and classify systems by criticality: identify devices that must remain on Windows 10 for legacy application compatibility or hardware constraints.
• Enroll high‑risk or critical endpoints in ESU if full OS‑level patching is required and migration is not immediately feasible. Review enterprise ESU pricing and procurement timelines. (learn.microsoft.com)
• Ensure all devices remain on Windows 10, version 22H2, as Microsoft’s post‑EOL Edge/WebView2 commitments explicitly target that release. (learn.microsoft.com)
• Maintain up-to-date Edge installations on Windows 10 endpoints and monitor WebView2 usage across internal apps. Prioritize replacing any applications that embed outdated or unsupported web controls.
• Validate vendor support statements for key third‑party software and drivers; plan for replacement or upgrade paths where vendors have signaled Windows 10 deprecation.
• Where possible, prioritize migrating workloads to Windows 11 or Windows 365 Cloud PCs for long-term platform and security alignment.
• For home users uncomfortable with OS end-of-life, consider upgrading hardware that meets Windows 11 requirements, or leverage Microsoft’s consumer ESU enrollment if eligible. (support.microsoft.com)

These steps create a defensible transition strategy that balances immediate security needs against migration realities.

---

How long is “at least October 2028”? Could Microsoft change course?​

Microsoft’s language — updates will continue “until at least October 2028” — leaves room for further changes. Historically, vendors sometimes extend, reduce, or otherwise modify lifecycle commitments to reflect business or technical realities. There is no public guarantee beyond the stated date, and Microsoft’s policy explicitly ties the Edge/WebView2 support horizon to the Extended Security Updates timeline. Organizations should therefore treat October 2028 as the minimum guaranteed horizon and plan migrations accordingly. (learn.microsoft.com)
Any statements or rumors about support beyond that point should be treated as speculative until confirmed via official Microsoft lifecycle documentation or corporate announcements.

---

Frequently asked questions (short answers)​

• Will Edge receive updates on all Windows 10 versions?
  No. Microsoft’s policy specifically references Windows 10, version 22H2 as the release that will receive Edge and WebView2 updates through 2028. Other Windows 10 builds are not covered by that commitment. (learn.microsoft.com)
• Do I need ESU to get Edge updates after October 14, 2025?
  No. Microsoft has stated that ESU enrollment is not required to receive Edge or WebView2 updates on Windows 10 22H2. (learn.microsoft.com)
• Does this mean Windows 10 is “safe” until 2028?
  Not entirely. Edge updates reduce browser-related risk, but the OS itself will not receive general security patches after October 14, 2025 unless ESU is purchased and applied. Critical OS-level vulnerabilities will remain unpatched for non‑ESU systems. (support.microsoft.com, learn.microsoft.com)

---

Editorial analysis: what Microsoft’s decision signals​

Microsoft’s decoupling of browser and OS update lifecycles is a pragmatic response to a widely recognized reality: billions of devices take years to transition, and web exposure is a dominant attack surface. Keeping Edge and WebView2 current on Windows 10 22H2 reduces a major portion of user-facing risk while allowing Microsoft to drive enterprise and consumer transitions toward Windows 11 and cloud-hosted Windows experiences.
That pragmatism does not remove incentives to migrate. Edge updates are a stopgap for web-related threats, but they are not a substitute for OS-level security servicing, hardware support, or long-term feature improvements. The policy also reflects Microsoft’s increasing tendency to productize components (browsers, runtimes, cloud services) that can be serviced independently of Windows itself.
For enterprises, the mix of Edge updates plus optional ESU purchases creates a menu of choices: pay to keep OS security supported or rely on browser updates as a partial mitigation while accelerating migration. Both options carry operational and financial tradeoffs.

---

Final assessment and practical takeaway​

Microsoft’s explicit commitment to keep Microsoft Edge and WebView2 updated on Windows 10 22H2 through at least October 2028 is an important reassurance for organizations and users who cannot immediately migrate. It materially reduces some web-driven security risks and extends the usable life of many Windows 10 devices.
However, it is not a silver bullet. The operating system itself is still scheduled to reach end of support on October 14, 2025, and OS-level patches require ESU enrollment or migration. Organizations and users should treat Edge/WebView2 updates as one element of a broader security and migration strategy: inventory devices, assess risk, evaluate ESU for critical endpoints, and plan upgrades to supported platforms before the end of Microsoft’s stated support horizon. (learn.microsoft.com, support.microsoft.com)
Conclusion: Microsoft has reduced one piece of the immediate risk equation by keeping the browser and embedded web runtime current on 22H2, but long-term security, compliance, and hardware compatibility still favor moving to a fully supported platform well before October 2028.

---

Source: BornCity Windows 10 22H2: Microsoft Edge will receive updates until October 2028 | Born's Tech and Windows World