Edge will move to updates every two weeks from August

Microsoft has accelerated Edge development. Starting with version 152, the Stable channel receives a new major version every two weeks instead of every four. Announced in June, the change took effect when Edge 152 entered Stable on August 27, 2026.

What actually changes

Major versions now arrive twice as often. Microsoft says each release carries a smaller set of changes, allowing features, platform improvements, and security work to reach users sooner. Release dates mark the beginning of a progressive rollout, so individual devices may update several days later.

The first releases

Edge 152 reached Stable on August 27 and Edge 153 followed on September 10, demonstrating the new two-week interval. Later releases have continued the cadence.

Home users

Updates remain automatic and normally require only a browser restart. Users can check through Help and feedback, then About Microsoft Edge. More frequent releases mean earlier access to fixes and features, with a smaller change set in each package.

Stable versus Extended Stable

The two-week schedule applies to Stable. Managed organizations that need longer validation windows can use Extended Stable, which remains on an eight-week cycle. It now receives every fourth Stable major version, such as 152, 156, 160, and 164. Both channels receive critical security updates; the primary difference is feature delivery speed.

Enterprise preparation

Organizations should adapt validation to smaller, more frequent changes. Microsoft recommends a Beta pilot group and early testing of internal web apps, extensions, enterprise policies, and authentication. Assisted support covers the current Stable version and the previous two, roughly six weeks in total.

WebView2 follows Edge

The WebView2 Runtime also moved to a two-week major cadence from version 152. IT teams should include Evergreen WebView2 applications in their compatibility testing.

Security servicing

The two-week cadence describes major releases. Microsoft can still issue critical security and servicing updates whenever needed, so automatic updates should remain enabled.

Conclusion

For most users the transition is transparent. Enterprises must adjust testing and communications: Stable favors faster innovation, while Extended Stable preserves a predictable eight-week window.