Microsoft is shifting its desktop browser to a biweekly release schedule, aligning with Chrome and Firefox, reducing update support windows and affecting enterprise deployment strategies.
Microsoft Edge 152 is beginning to reach Stable users on 27 August 2026, and with it Microsoft is formally moving its desktop browser to a two-week major-release cycle. The change marks the start of a short but significant industry overlap: Firefox 155 is due on 1 September and Chrome 153 on 8 September, meaning the three browsers that dominate desktop will all have abandoned the four-week cadence they adopted in 2021 within a 12-day span.
For most consumers, nothing needs to be done. Edge will update automatically as the rollout expands. Microsoft has said the change affects the release calendar rather than the enterprise controls used to manage deployment, so existing Group Policy settings, update preferences and admin tools remain in place. The practical difference is that users and IT teams will now see smaller updates more often, rather than larger monthly bundles.
The timing matters most for organisations. Under the previous schedule, the three most recent Edge Stable releases covered roughly 12 weeks of support. With a two-week cadence, that same three-release window shrinks to about six weeks. Microsoft is steering enterprises towards a clearer channel choice: Stable for teams that can validate browser changes quickly, and Extended Stable for environments that need a longer eight-week interval.
Microsoft also moved WebView2 onto the same rhythm. Version 152 is the last major WebView2 release to follow the old four-week pace, while version 153, expected in the week of 10 September, will be the first on the new two-week schedule. That matters because WebView2 is embedded in many Windows applications, including enterprise software and Microsoft’s own apps. The SDK will no longer ship on a fixed monthly timetable, but only when there are new features, fixes or security updates to deliver.
The broader rationale is security and alignment. Chromium-based browsers inherit a patch cycle that is driven in large part by Google’s upstream work, so a four-week stable release could leave a gap between a Chromium fix and its arrival in Edge. Microsoft’s shorter cycle reduces that exposure window. Google has already taken Chrome to a two-week major cadence, and Mozilla is now doing the same for Firefox, albeit as an experiment rather than a permanent commitment.
Mozilla has framed Firefox’s move carefully. Its release notes and developer communications say Firefox 155, scheduled for 1 September, is the first version on the new two-week rhythm, while the Extended Support Release track stays on its annual cycle. Mozilla has said the aim is to deliver fixes and completed features sooner without forcing developers to rush work, and it will watch the effect on quality, workload and user experience before deciding whether to make the change permanent.
Disclaimer: This content is intended for informational purposes only. Readers are advised to exercise their own judgement, conduct due diligence, or consult a qualified expert before acting on any information provided.
