Microsoft Edge moving to a 2-week release cycle starting with Edge 152

Starting August 27, 2026, Microsoft Edge Stable channel will shift to a 2-week release cycle for faster, smaller updates. Extended Stable remains on an 8-week cycle. No admin changes are needed; organizations should prepare for more frequent updates and consider pilot testing on Beta.

[What and Why:]

Starting with Microsoft Edge 152 (Stable on August 27), Edge will move to a 2-week release cycle. This change enables faster delivery of security updates and platform improvements, while reducing the size and complexity of individual updates. For organizations, this means more predictable validation cycles with smaller, more frequent changes. For organizations that prefer a more deliberate pace, Extended Stable remains unchanged in timing. 

[Rollout Schedule:]

• General Availability (Worldwide):  We will begin rolling out in late August 2026 and expect to complete by late August 2026.
• First release under the new cadence: Edge 152 (August 27, 2026)

[Impact on Your Organization:]

Who is affected: Organizations using Microsoft Edge Stable channels

Platforms/Services: Microsoft Edge (Windows, macOS, Linux, mobile)

What will happen:

• The Stable channel (the default release channel for most organizations, delivering new features and fixes regularly) will move from a 4-week to a 2-week release cycle.
• Each release will contain smaller feature updates and faster delivery of security and platform fixes.
• The Extended Stable channel (an optional channel designed for organizations that need more time to validate updates) will continue to update every 8 weeks.
• Extended Stable updates will be published every fourth release (for example, versions 156, 160, 164).
• There's no change to existing admin policies or management tools.
• Updates continue to deploy automatically based on your configured update settings.

Screenshot: Edge Stable updates every 2 weeks, with Extended Stable on an 8‑week cycle for slower change:

[Action Required/Recommendations:]

No action is required to receive this update.

We recommend:

• If using Stable channel: prepare for more frequent updates and adjust validation cadence
• If using Extended Stable channel: no changes required
• Establish a pilot group on the Beta channel for early testing
• Update internal documentation or helpdesk guidance

Learn more: Faster updates, enterprise-friendly schedule: the new Microsoft Edge release cycle | Microsoft Edge Blog

[Compliance considerations:]

No compliance considerations identified, review as appropriate for your organization.