Microsoft is changing the Edge Stable channel release cadence starting with Edge 152, the next release. From this release onward, Stable versions will ship every 2 weeks instead of every 4 weeks, delivering smaller, more frequent updates.
- This change applies to the default Stable channel across Windows, macOS, Linux, and Mobile.
- Extended Stable, the slower-cadence channel for managed environments, is not affected and keeps the existing 8-week cadence.
This change affects release cadence and version numbering only. It does not change how updates are deployed, does not require new policies, and does not affect the Extended Stable schedule beyond the version-number alignment.
Timeline
- Scheduled for Microsoft Edge release 152.
- The rollout to the Beta channel was scheduled for CW 32/2026 (last week).
- The rollout to the Stable and Extended Stable channels is scheduled for CW 35/2026.
How does this affect your organization?
For organizations on the Stable channel, Microsoft Edge releases will now land twice as often as before. Each release carries roughly half the feature content of a previous 4-week release, so the overall pace of change over time stays similar. Individual updates are smaller and arrive more frequently. This is intended to shorten the delivery time for security and platform fixes and to make each update easier to validate.
The Extended Stable channel keeps its 8-week release cycle. Under the new numbering, Extended Stable will pick up every fourth Stable release, for example versions 156, 160, 164,….
- Stable channel: default channel for most organizations, moving from a 4-week to a 2-week release cycle
- Extended Stable channel: optional channel for organizations that need longer validation windows, continuing on an 8-week cycle, now aligned to every fourth Stable release
Existing update policies, management tools, and configured update settings continue to apply, and updates continue to deploy automatically based on those settings. Organizations that currently rely on the Stable channel for validation cycles should review whether their testing and change-management processes are set up for a 2-week rhythm rather than a monthly one.
Microsoft also mentions using Edge Enterprise Preview, generally available since June, as a recommended path for piloting Beta releases.
