Microsoft Edge release notes for Stable and Extended Stable Channels

These release notes provide information about new features and nonsecurity updates that are included in the Microsoft Edge Stable and Extended Stable Channels.

Subscribe via RSS | Previous Releases | Known Issues

Contents - August - September 2026

Version 153.0.4234.32: September 10, 2026 (Stable) - Main Release

Release Summary

Announcement

• Retiring Windows Information Protection (WIP) and Microsoft Defender Application Guard (MDAG) in Microsoft Edge. The WIP and MDAG code paths are being retired from Microsoft Edge, aligning Edge with the Windows platform. Windows deprecated both technologies and removed them in Windows 11, version 24H2.

  Only tenants that configured WIP or MDAG in Microsoft Edge are impacted by this change. Both features are off by default and require an admin to turn them on, so tenants that never enabled them are not affected. In practice this is a small, Windows 10 population. Both features were committed for Windows 10 only, and both are already unavailable on Windows 11, version 24H2.

  For organizations using WIP, use Microsoft Purview Information Protection, Microsoft Purview endpoint DLP, and Data Loss Prevention and also Intune app protection policies for data protections instead of WIP.

  For organizations using MDAG, use the built-in Microsoft Edge for Business security capabilities and Microsoft Edge browser natively supports hardware isolation instead. Also further, Microsoft Defender SmartScreen, Enhanced Security Mode, Data Loss Prevention, and website typo protection is available.

  This change rolls out through the normal Microsoft Edge release channels, and will reach general availability with Microsoft Edge Stable 154 around September 24, 2026.

• Deprecating the unload event. Microsoft Edge is changing the default behavior of the web platform unload event. As the rollout progresses, pages will no longer run unload event handlers unless the site explicitly permits them.

  • In Edge 152 and 153, unload handlers will stop firing by default for 60% of page loads unless the site explicitly enables them through Permissions Policy.
  • In Edge 154, the rollout will increase to 80% of page loads.
  • In Edge 155, the rollout will reach 100% of page loads.

  The unload event is not a dependable way to save data, perform cleanup, or report the end of a session because browsers and operating systems can suspend or terminate pages without firing it. It can also prevent pages from using the back/forward cache, which may make back and forward navigation slower.

  Web developers should migrate to lifecycle events and APIs designed for these scenarios. The long-term direction of the web platform is to remove support for unload.

Feature updates

• Tracking prevention when browsing InPrivate. Microsoft Edge is unifying the tracking prevention experience for non-InPrivate and InPrivate browsing windows. The toggle that allowed users to select “Strict” tracking prevention for InPrivate mode is removed. This toggle, previously in edge://settings/privacy/trackingPrevention and on the InPrivate new tab page (NTP), is no longer available. Microsoft Edge now uses the same tracking prevention setting as a normal browsing window when in InPrivate mode.

• Changes to local IP address detection for proxy auto-config (PAC) scripts. Microsoft Edge reports a local network address to proxy auto-config (PAC) scripts through the myIpAddress() and myIpAddressEx() functions. To choose that address, Microsoft Edge connects a UDP socket to a fixed destination address and reports the source address that the operating system selects for that route. Microsoft Edge now uses Chromium's default destinations for this lookup instead of Edge-specific ones: the default IPv4 destination changes from 20.76.201.171 to 8.8.8.8, and the default IPv6 destination changes from 2603:1020:201:10::10f to 2001:4860:4860::8888. The new values are the Google Public DNS addresses that Chromium uses by default. Microsoft Edge sends no packets to these addresses and uses them only so that the operating system selects a route and a source address, so no firewall change is needed.

  Because the destination is only a routing sentinel, any host route, policy-based route, or null route that matches it determines which network interface the lookup observes. On a device with more than one active connection, such as a VPN and Wi-Fi at the same time, a route covering the destination can cause a PAC script to receive an address from an unintended network. Organizations should review routes for both the previous and the new destinations. A route that directs the destination to a particular interface causes PAC scripts to observe that interface's address, while a route that leaves the destination unreachable causes Microsoft Edge to fall back to its other address-detection methods.

  Administrators who need the lookup to follow a particular network can set a destination that routes over it, using the new PacMyIpAddressIPv4ProbeAddress and PacMyIpAddressIPv6ProbeAddress policies.

• Fading tabs experience retired. The fading tab experience will be removed from the Microsoft Edge browser. The Fade inactive tabs setting will no longer be available in edge://settings/system/managePerformance and users will no longer see tabs fade. Note: This is a controlled feature rollout. If you don't see this change, check back as we continue the rollout.

• Summarize videos toggle in YouTube video menu. For eligible Microsoft Edge for Business users, the YouTube video hover overlay now includes a Summarize toggle. Selecting it opens Microsoft 365 Copilot Chat to summarize the video. Availability respects the organization’s Copilot page-context policy, user consent, and data loss prevention protections.

• Update to WebView2 DowngradeVersion policy. The DowngradeVersion policy allows admins to temporarily roll back specific applications to a previous WebView2 Evergreen Runtime version. The DowngradeVersion policy now allows admins to roll back up to four versions (N-1, N-2, N-3, or N-4), which aligns with the Microsoft Edge 2-week release cadence.

Policy updates

New polices

• HttpHeaderInjection - Configure HTTP Header Injection for specific URL patterns
• LaunchEdgeOnWindowsStartupEnabled - Launch Microsoft Edge on Windows startup
• PacMyIpAddressIPv4ProbeAddress - Set the IPv4 route-probe address for PAC scripts
• PacMyIpAddressIPv6ProbeAddress - Set the IPv6 route-probe address for PAC scripts

Obsoleted policies

• CollectionsServicesAndExportsBlockList - Block access to a specified list of services and export targets in Collections (obsolete)
• EdgeCollectionsEnabled - Enable the Collections feature (obsolete)
• RelatedWebsiteSetsEnabled - Enable Related Website Sets (obsolete)
• RelatedWebsiteSetsOverrides - Override Related Website Sets (obsolete)

Back to top

Version 152.0.4191.53: August 27, 2026 (Stable) - Main Release

Release Summary

Announcements

• Deprecating the unload event. Microsoft Edge is changing the default behavior of the web platform unload event. As the rollout progresses, pages will no longer run unload event handlers unless the site explicitly permits them.

  • In Edge 152 and 153, unload handlers will stop firing by default for 60% of page loads unless the site explicitly enables them through Permissions Policy.

  • In Edge 154, the rollout will increase to 80% of page loads.

  • In Edge 155, the rollout will reach 100% of page loads.

  The unload event is not a dependable way to save data, perform cleanup, or report the end of a session. Browsers and operating systems can suspend or terminate pages without firing it, and this can prevent pages from using the back/forward cache, which may make back and forward navigation slower.

  Web developers should migrate to lifecycle events and APIs designed for these scenarios. The long-term direction of the web platform is to remove support for unload.

• Microsoft Edge has completed the move to a 2-week cadence for updates. We have adopted a new, 2-week release cycle for major versions. For more information, see Faster updates, enterprise-friendly schedule: the new Microsoft Edge release cycle - Microsoft Edge Blog.

Feature Updates

• Automatically unsubscribe users from notifications sent by scam and malicious sites. Microsoft Edge now helps further protect users from malicious web notifications. When a notification leads users to a site that Microsoft Defender SmartScreen blocks as a scam, phishing, or malware page, Edge automatically stops that source from sending users further notifications. Edge lets users know when this happens. Users can review and restore any of these sites anytime under edge://settings/privacy/sitePermissions/allPermissions/notifications. Note: This is a controlled feature rollout. If you don't see this change, check back as we continue the rollout.

• Sign in to Edge with an Apple account. Users can now sign in to Microsoft Edge using an Apple account in addition to the Microsoft account from the profile menu and Edge sign-in screen. Available for Windows and macOS devices. Admins can control availability to this feature using the NonMicrosoftAccountSignInEnabled policy. Note: This is a controlled feature rollout. If you don't see this change, check back as we continue the rollout.

• Real-time video translation retirement. Real-time video translation is being retired through a gradual rollout. Availability may vary across environments during the rollout. The LiveVideoTranslationEnabled policy will be deprecated in a future update.

• Enhanced Key Icon with Credential Details, Copy Actions, and Notes. The key icon in Edge's address bar now lets users click into any saved credential to view a detailed panel. From there, users can copy a username, reveal and copy a password, and add personal notes to each login. Keep track of security questions, account purpose, or recovery details right alongside credentials, without opening Settings or the full password manager. Note: This is a controlled feature rollout. If you don't see this change, check back as we continue the rollout.

• Drop is retired. We're simplifying Microsoft Edge. Drop is retired in Microsoft Edge version 152.

• New Copilot Cowork policy. Copilot Cowork may perform tasks such as creating tabs, taking screenshots, and interacting with web pages. Admins can now control availability of this feature using the CopilotCoworkToolActionsEnabled policy, which corresponds to the Allow Cowork to take actions on your behalf setting in edge://settings/ai. This policy applies only when Cowork Browsing is enabled at the tenant level in the M365 admin center.

• Clarification of WebView2 DowngradeVersion policy. The DowngradeVersion policy allows admins to temporarily roll back specific applications to a previous WebView2 Evergreen Runtime version (N-1 or N-2). The policy requires an exact 4-part numeric WebView2 Runtime version, for example 151.0.2178.0. Admins can find the exact 4-part version number in the Microsoft Edge release notes for Stable Channel. Major-version-only values are not supported. If no exact matching folder is found, the policy has no effect and the runtime defaults to the BrowserExecutableFolder policy or the Evergreen runtime, which is the default auto-updating runtime.

• Update for LocalNetworkAccessRestrictionsTemporaryOptOut policy. The planned removal of the LocalNetworkAccessRestrictionsTemporaryOptOut policy has been updated. The policy is now scheduled for removal after Microsoft Edge version 156; previously it was version 152.

• Updated Copilot policy. Admins can now control availability of the video transcription feature using the EdgeEntraCopilotPageContext policy, which corresponds to the Allow Copilot to transcribe your video setting in edge://settings/ai.

Policy Updates

New policies

• CopilotCoworkToolActionsEnabled - Allow Cowork to take actions on your behalf
• UpdateOnZeroWindowEnabled - Controls background automatic relaunch when all browser windows are closed
• BackForwardCacheForWebSocketsAllowed - Allow Back/Forward Cache for WebSockets

Additional policy changes

• ShowHistoryThumbnails - Policy removed

Version 152.0.4191.77: September 10, 2026 (Extended Stable) - Update 3

Release Summary

Version 152.0.4191.66: September 4, 2026 (Stable) - Update 2

Release Summary

Version 152.0.4191.62: September 2, 2026 (Stable) - Update 1

Release Summary

Back to top

See also

• All the security updates are listed in Release notes for Microsoft Edge Security Updates.
• Archived release notes for Microsoft Edge Stable Channel are located in Archived release notes for Microsoft Edge Stable Channel.
• Microsoft Edge Enterprise landing page.
• Explore all previous releases.

To understand Microsoft Edge channels, see the Overview of the Microsoft Edge channels.