Edge and WebView2 Updates on Windows 10 Extend Security to 2028

Windows 10 will reach its official end of support on October 14, 2025, but one critical piece of the platform — Microsoft Edge and the WebView2 runtime — will continue to receive security and feature updates on Windows 10 (22H2) through at least October 2028, even for devices that do not purchase Extended Security Updates (ESU).

Background​

Microsoft’s lifecycle for Windows 10 has been fixed in public notices for months: the OS will stop receiving regular security patches and technical support on October 14, 2025. That is the formal end-of-support date that drives enterprise migration plans, managed device lifecycles, and most vendor compatibility roadmaps.
At the same time, Microsoft has made two parallel commitments that change how a consumer or small-business PC will behave after that date. First, Microsoft has created consumer-friendly ESU enrollment options so individual Windows 10 PCs can obtain a year of extended security updates (through October 13, 2026) via a new enrollment wizard that offers three methods: enable Windows Backup (cloud sync), redeem 1,000 Microsoft Rewards points, or pay a one-time $30 fee (requirements vary regionally and a Microsoft account is involved).
Second — and most relevant to everyday web use — Microsoft explicitly states that Microsoft Edge and the Microsoft WebView2 Runtime will continue to receive updates on Windows 10 (22H2) until at least October 2028, and that these Edge/WebView2 updates will not require ESU enrollment. This was published in Microsoft’s Edge lifecycle policy and repeated across technology outlets.

---

What Microsoft actually announced​

Edge and WebView2: three more years of updates​

Microsoft’s official lifecycle page for Edge spells the policy out clearly: Edge and the WebView2 Runtime will continue to receive updates on Windows 10 22H2 until at least October 2028, aligned with the end of ESU for enterprises. Microsoft also confirmed that ESU enrollment is not required for Edge/WebView2 updates on consumer Windows 10 devices.
That statement separates browser/runtime updates from full OS servicing. In other words, even as Windows 10 itself becomes unsupported from a platform perspective, Microsoft will continue to ship updated builds of Edge and WebView2 (both Chromium-based) to keep web browsing, web-based apps, and embedded web content safer and more compatible.

Windows 10 OS support and Microsoft 365 timing​

Microsoft’s Windows support and Microsoft 365 guidance make parallel commitments: while Windows 10’s general support ends on October 14, 2025, Microsoft will continue to provide security updates for Microsoft 365 apps on Windows 10 for a total of three years after the OS end-of-support — running through October 2028 — to reduce risk during migrations.

Consumer ESU options and regional caveats​

For consumer PCs, Microsoft introduced a one-year ESU option via a new enrollment wizard in mid‑2025, with three enrollment paths (Windows Backup sync to OneDrive, redeem Microsoft Rewards points, or pay $30). Regions within the European Economic Area (EEA) have since been offered a more generous arrangement under regulatory pressure, with free ESU availability in some EEA markets subject to Microsoft account sign-in and periodic re-authentication rules. Outside the EEA, the free path is not uniform and conditions apply.

---

Why Edge and WebView2 matter after October 2025​

Edge is the browser, WebView2 is the in-app web platform​

• Microsoft Edge is the default and deeply integrated browser on Windows 10, and it’s used directly for browsing, web apps, and many system-level experiences.
• Microsoft WebView2 Runtime is the embeddable Chromium-based web control used by thousands of Windows apps (e.g., Teams, Office components, many third-party apps) to render web content inside native applications.

Keeping both components updated matters because vulnerabilities in the rendering engine or browser features are prime attack vectors. Maintaining up-to-date Edge/WebView2 is therefore materially beneficial for security and compatibility even when the rest of the OS stops receiving full platform patches.

What continued Edge/WebView2 updates deliver​

• Regular security patching of Chromium engine flaws that would otherwise be exploitable by malicious websites.
• Updated web standards and features, improving site compatibility and reducing rendering bugs.
• Critical stability fixes for apps that rely on WebView2 to display content inside native windows.

Because Edge and WebView2 are Chromium-based, Microsoft can push engine and security patches to large numbers of Windows 10 devices without shipping full OS servicing packages. That reduces the attack surface for web-based threats even as OS-level fixes become less frequent.

---

What this DOES — and DOES NOT — mean for users​

It DOES mean:​

• Browsing in Edge on Windows 10 (22H2) will remain patched and receive feature/security updates through at least October 2028, independent of ESU purchases.
• Many apps that rely on WebView2 will continue to display web content securely because the embedded runtime will also be maintained.
• Microsoft 365 customers and many consumers will have Microsoft-provided browser and Office security assurances that overlap with Edge/WebView2 updates through 2028.

It DOES NOT mean:​

• Windows 10 will be fully supported as an OS after October 14, 2025; system-level vulnerabilities, device driver issues, or OS component bugs that are outside Edge/WebView2 will not be fixed.
• All third-party software or drivers will continue to be compatible; hardware vendors are not obligated to release updated drivers for an unsupported OS.
• Other browsers will automatically be updated indefinitely by their vendors; Edge’s guarantee is Microsoft’s decision and is not a universal promise by Chromium or Mozilla. Users must verify vendor commitments.

---

How other browsers might behave — realistic expectations​

Chromium-based browsers (Chrome, Brave, Vivaldi, Opera)​

Microsoft’s Edge is built on Chromium. When Microsoft pledged to keep Chromium-based Edge updated on Windows 10 through 2028, it implicitly lowered the technical barrier for other Chromium-based vendors to continue support on Windows 10 as well: they can still ship updates that use the same core engine while maintaining backward compatibility. Several outlets noted that Chrome and other Chromium browsers could remain operable on Windows 10 until 2028 if the maintainers choose to do so, but that is not a guarantee — each vendor sets its own platform support policy. Historically, Google ended Chrome support for older OSes (e.g., Windows 7 and 8.1) in early 2023, demonstrating that vendor policy choices matter.

Firefox (Gecko engine)​

Firefox uses Mozilla’s Gecko engine and runs on a different update cadence and lifecycle model. Mozilla has previously extended Firefox ESR support on older operating systems beyond the OS end-of-life (for example, extending ESR 115 support on Windows 7/8/8.1 until March 2026). That shows Mozilla may take a cautious, case-by-case approach that can extend compatibility on older OSes — but again, Firefox’s long-term support decisions for Windows 10 beyond 2028 are not guaranteed.
Bottom line: Edge’s commitment is explicit; other vendors will likely weigh commercial and technical factors before making multi-year promises for an OS that Microsoft declares out of support.

---

Enterprise vs. consumer impact​

Enterprises​

Enterprises usually manage browser updates through enterprise channels, group policies, and managed WebView2 distributions. Microsoft’s announcement aligns Edge lifecycle with enterprise ESU timelines, but organizations must still consider:

• Device management and driver support when Windows 10 loses platform patches.
• Compliance and audit obligations: running an OS out of mainstream support can affect compliance status.
• Application compatibility testing for upgraded Edge versions on legacy systems.

For many large organizations, the Edge continuity is helpful but insufficient as a standalone mitigation. Enterprises should treat Edge/WebView2 updates as one layer in a broader migration and security plan.

Consumers and small businesses​

Consumers receive the largest immediate benefit: a modern browser and safer in-app web content without paying for ESU specifically to get Edge/WebView2 patches. Coupled with Microsoft’s one-year consumer ESU enrollment options (including the Windows Backup or Rewards paths), many home users will find the transition less urgent. However, consumers should still assess hardware capability, driver availability, and long-term exposure to OS-level vulnerabilities.

---

Practical guidance: what to do now​

1. Keep Edge updated and turn on auto-update​

Edge updates are the security lifeline for browser-based threats. Ensure Edge auto-update is enabled so security fixes are applied as Microsoft publishes them. For managed environments, ensure update policies or the Edge Update service are correctly configured.

2. Enroll in ESU if you need OS-level protections​

If a device cannot be migrated to Windows 11 and you want OS-level security patches beyond October 2025, follow Microsoft’s ESU enrollment wizard. For consumer PCs this includes:

• Enroll via the Settings > Windows Update ESU prompt when available.
• Choose Windows Backup cloud sync, redeem Microsoft Rewards, or pay $30 for the year (region-specific rules may apply).

3. Use Microsoft accounts where required — and understand privacy tradeoffs​

Some free ESU options and EEA-specific arrangements require a Microsoft account and periodic sign-ins (e.g., once every 60 days). That requirement is a practical hurdle if you prefer local accounts for privacy or offline use. If you rely on the free options, ensure the account is connected and stays active.

4. Harden systems and minimize attack surface​

• Use a modern, updated browser (Edge, Chrome, Firefox) and enable features like site isolation and automatic updates.
• Maintain anti‑malware tools and enable Defender or another reputable AV product.
• Limit privileged account usage; run day-to-day tasks in standard user sessions.
• Keep critical applications (e.g., Office, Teams) patched and favor Microsoft 365 subscriptions where possible because Microsoft has committed to 3 years of Microsoft 365 updates on Windows 10 through Oct 2028.

5. Plan migrations and test drivers/apps​

Schedule a migration path to Windows 11, Linux, or newer hardware in your roadmap. Test drivers and critical apps against the target OS early — hardware vendors may cease releasing Windows 10 drivers after 2025, causing future compatibility problems.

---

Risks, trade-offs, and unanswered questions​

A symbolic vs. practical end-of-life​

The extension of Edge/WebView2 updates blurs the calendar date’s impact: October 14, 2025 will still mark the end of Windows 10 support, but it will not instantly make devices “unsafe” in the browser context. That makes the EoL date more symbolic for everyday web use, but it does not remove structural risks tied to OS-level flaws, driver bugs, or firmware vulnerabilities that Edge cannot address.

Vendor-specific policies cause fragmentation​

Microsoft’s explicit promise for Edge does not bind Google, Mozilla, or other vendors. If Chrome or other Chromium-based browsers decide to change their Windows 10 support policies, Windows 10 users may find their browser choices narrowing over time. Historical precedent (Chrome dropping Windows 7/8.1 support in 2023) shows vendors can and do stop supporting older OSes when it makes sense for their release engineering. Users relying on a single vendor expectation may find themselves exposed if vendor policies shift.

Privacy and the Microsoft account gating​

Some “free” ESU paths require Microsoft accounts or cloud backup. For users and organizations that avoid cloud accounts or prefer local-only setups, the practical cost of staying on Windows 10 becomes higher — either you pay the $30 fee or accept an account connection. Microsoft’s approach effectively pushes identity-based enrollment, raising policy and privacy trade-offs.

Unknowns about long-term driver and firmware updates​

Even with Edge/WebView2 updates, critical devices can be rendered unstable by unpatched drivers or UEFI/firmware vulnerabilities. Microsoft’s browser commitment does not extend to hardware vendor behavior, and vendors may reduce Windows 10 investments in driver quality over time. That will incrementally increase operational risk for older machines.

---

Who should upgrade now — and who can reasonably wait?​

Upgrade sooner if:​

• You run a business with compliance requirements, audited environments, or regulatory needs that mandate supported OS versions.
• Your machine needs drivers or peripherals whose vendors have announced Windows 10 deprecation.
• You handle sensitive data that cannot rely solely on browser-layer protections.

Safe to wait (short term) if:​

• You primarily use web-based apps that operate in Edge/WebView2 or hosted SaaS services that remain compatible.
• You enroll in Microsoft’s consumer ESU program (backup, Rewards, or $30 option) for the one-year extension through October 13, 2026.
• You accept the privacy/identity trade-offs associated with Microsoft Account enrollment for ESU and can keep your device’s non-browser layers mitigated via additional security controls.

---

Strategic takeaway: Edge updates soften, but don’t erase, the end-of-support cliff​

Microsoft’s decision to continue updating Edge and WebView2 on Windows 10 through October 2028 is a pragmatic concession to security and application continuity. It mitigates the most visible and immediate risk for consumers and many small businesses: a modern, secure web browsing experience and safer in-app web content. That decision lowers the urgency for users who only need a browser and cloud-based apps.
However, it does not turn October 14, 2025 into a non-event. The end of OS platform servicing still changes the long-term security and compatibility calculus: driver updates, firmware fixes, kernel vulnerabilities, and OS-level integration bugs will not be addressed unless you enroll in ESU (beyond the consumer year) or migrate to Windows 11 or another supported OS. The Edge commitment buys time — meaningful time — but it is a bridge, not a destination.

---

Final recommendations (concise checklist)​

• Ensure Microsoft Edge auto-updates are enabled and verify you are on Windows 10 version 22H2 to receive the Edge/WebView2 assurances.
• If you can’t upgrade to Windows 11, enroll in the consumer ESU path that suits you (Windows Backup, Microsoft Rewards, or pay $30) to obtain OS-level security updates through Oct 13, 2026. Consider EEA-specific rules if you are in the European Economic Area.
• For businesses, create a prioritized migration plan that accounts for drivers, firmware, and compliance; use Edge/WebView2 maintenance as a stopgap, not a permanent solution.
• Harden systems with modern AV, least-privilege accounts, and strong backup strategies even if you remain on Windows 10 temporarily.

Microsoft’s Edge commitment changes the practical risk profile for many Windows 10 users, but it does not eliminate the need for careful planning and eventual migration. Treat Edge/WebView2 updates as an important safety net — and use the breathing room they provide to migrate thoughtfully, test thoroughly, and minimize long-term risk.

---

Source: myhostnews.com Windows 10: Edge updated until 2028 despite end of support