Microsoft has built a version of Edge that can install a security update while the browser stays open, keeping tabs and active work in place without asking the user to restart.
That capability is not available yet. Microsoft says its seamless-updates system is an early prototype, with no production release date. What Edge users can use now is Restart to update on idle, which still restarts the browser but waits until the computer is not being used.
According to Microsoft’s Oct. 15 Edge announcement, the prototype moves the browser, its supporting processes, and open tabs to the patched version in the background. Microsoft says the technology is not part of production Edge or Chromium today.
What Edge can do today
The difference between Microsoft’s prototype and its current update tools is fairly simple:
| Edge update feature | Available now? | Requires a restart? | Intended use |
|---|---|---|---|
| Seamless updates | ✖ No, prototype only | ✖ No | Apply a new browser version while work continues |
| Restart to update on idle | ✔ Yes, opt-in preview | ✔ Yes | Apply pending updates while the device is idle |
| Security Update Alerts | ✔ Yes | N/A | Show admins which managed Windows devices need security updates |
Restart to update on idle is off by default. Users can enable it from Settings > About Microsoft Edge. Microsoft says Edge waits until the device has been idle before warning that a restart is coming, applies the pending update, and then restores open tabs.
That does not guarantee every unfinished task survives. Microsoft warns that unsaved forms or work in web apps that do not save automatically can still be lost during the restart.
Organizations can configure the feature through the Edge management service. The same service includes Security Update Alerts, which can notify administrators when a newly released Edge version contains fixes at or above a chosen severity threshold.
The Monitoring dashboard shows the Edge versions running across managed devices, the CVEs addressed by an update, its severity, and which devices may still need it. Microsoft currently limits that monitoring data to Windows devices.
Version monitoring also has to be enabled before those device insights appear. Doing so requires diagnostic data from managed Edge installations, so administrators should account for that when configuring organizational telemetry policies.
How quickly a browser update reaches users
Microsoft calls the delay between a fix becoming available and the patched browser actually running the patch gap. A downloaded update does not close that gap if Edge stays open on the older version.
An attack Microsoft investigated in September illustrates the timing problem. Its Browser Vulnerability Research team said attackers combined V8 remote-code-execution flaws with sandbox escapes while targeting Chromium-based browsers.
Microsoft confirmed active exploitation on Sept. 1 and began rolling out Edge 152.0.4191.62 with the first fix on Sept. 2. After researchers identified an additional sandbox escape, Edge 152.0.4191.66 began rolling out Sept. 4. Chrome’s corresponding Stable update followed Sept. 8.
Browser makers have already been shortening release windows. Google moved to more frequent Chrome security updates earlier this year, while Microsoft moved Edge Stable to a two-week major-release cycle beginning with version 152.
Those faster schedules do not eliminate the final step on the device. A recent Chrome 154 security update bundled fixes for 108 vulnerabilities, but a patched browser version still has to reach and replace the vulnerable one before those fixes protect the user.
Microsoft can also move independently of Chromium when it believes Edge users need a fix sooner, as it did during the September attack campaign.
What IT teams should configure now
Administrators do not need to wait for restart-free updates to reduce the patch gap.
First, keep Edge Update enabled. Microsoft’s update policy documentation recommends Always allow updates, which permits both automatic periodic checks and manual update checks.
Edge updates also run on their own browser cadence rather than waiting for the broader Windows Patch Tuesday cycle. Teams should therefore monitor Edge versions directly instead of assuming normal Windows patch reporting confirms the browser is current.
For managed Windows fleets, the practical checklist is:
- Enable version monitoring in the Edge management service.
- Set Security Update Alerts to the severity threshold your organization uses for browser vulnerabilities.
- Identify devices running older Edge versions from the Monitoring dashboard.
- Enable Restart to update on idle where the risk of unsaved browser work is acceptable.
- Keep automatic Edge updates enabled rather than waiting for users to check manually.
- Verify the installed version at
edge://settings/helpwhen investigating a potentially exposed device.
Channel choice should not be used to postpone security fixes. Edge Stable now receives major releases every two weeks, while Extended Stable keeps an eight-week major feature cycle for managed environments. Microsoft says both channels continue to receive critical security updates between those feature releases.
Restart-free patching could eventually remove one of the last points of friction in browser updating, but organizations cannot deploy it yet. For now, the available controls are designed to shorten the gap: get the update onto the device, identify systems that are behind, and move unavoidable restarts into idle time.
Also read: If Edge is one of several browsers under evaluation, our AI browser comparison covers Edge, Chrome, Brave, Comet, and Dia.