Microsoft Edge Shows Off Restart-Free Updates, but There’s a Catch

Microsoft wants to fix one of the most annoying parts of browser security: having to stop what you’re doing and restart to finish an update.

In an October 15 blog post, Microsoft’s Rob Franco and Arunesh Chandra outlined a working Microsoft Edge prototype that moves the browser to a newer version while your tabs and work stay open. The goal is to apply security updates without a restart prompt—or eventually even an update button.

The catch? It’s still a prototype, not a feature you can switch on today. Microsoft says the technology is early in development, isn’t in production code, and isn’t part of Chromium.

There are practical changes available now, though. Edge’s “Restart to update on idle” option can apply pending updates while you’re away, while Security Update Alerts help businesses identify browsers that need important fixes.

Microsoft Edge wants to update without stopping your work

The idea behind seamless updates is straightforward: keeping your browser secure shouldn’t mean choosing between restarting and finishing what you’re doing.

Microsoft uses an expense report as an example. You’ve gathered receipts, filled out the form, and then notice an update is waiting. Restarting at that moment is hardly appealing.

With the prototype, Edge transitions the browser, its supporting processes, and open tabs to the updated version while keeping the form open and the work in place.

Microsoft’s demonstration uses an Update button to show when the process starts. The longer-term ambition is to remove that step entirely, allowing updates to take effect in the background while you keep working. The company says that could allow protection to become active within minutes of an update becoming available.

That’s the proposed experience—not a shipping guarantee or an announced release timeline.

It also addresses a different kind of browser improvement from the features in our previous coverage of Microsoft Edge’s Copilot expansion across desktop and mobile. Rather than adding another tool to the browser, this work aims to make essential maintenance less disruptive.

Why restart-free browser updates are difficult

A modern browser isn’t a single process that can simply swap itself out while everything else carries on.

As Microsoft explains in the announcement, the browser must coordinate multiple connected processes and move them safely to a new version without disrupting the user’s work. Keeping an open tab visible is only part of the challenge; preserving what’s happening inside it matters, too.

That’s why the distinction between a working demonstration and a production feature is important. Microsoft is sharing the prototype early to make the idea tangible and invite other browser developers to explore similar approaches.

The company hasn’t announced when seamless updates might reach Edge users or whether they’ll appear in a public preview first.

Restart to update on idle is available now

You don’t need to wait for the prototype to get some of the benefits of less disruptive updates.

“Restart to update on idle,” previously called “Instant Updates,” can restart Edge when your device is idle, apply a pending update, and restore your open tabs. Microsoft’s browser security team lists it as an option users can enable through the About Microsoft Edge page.

To find it:

1. Open Microsoft Edge.
2. Select the three-dot menu.
3. Go to Help and feedback > About Microsoft Edge.
4. Look for the “Restart to update on idle” toggle and enable it.

You can also open edge://settings/help to check your update status. If Edge asks you to restart to finish an update, that restart is still necessary to activate the updated version.

The important difference is that idle updating still restarts the browser. It moves the interruption away from active use rather than eliminating it.

And restored tabs shouldn’t be confused with guaranteed preservation of everything entered into a page. Microsoft’s enterprise documentation explicitly warns that forced idle restarts may cause the loss of entered content, so save unfinished work rather than relying on tab restoration alone.

The real problem is the patch gap

Microsoft’s broader goal is to reduce the “patch gap”: the time during which a fix exists but the browser you’re actually running remains vulnerable.

There are two parts to that problem:

• A Chromium fix must be integrated, tested, and shipped in an Edge release.
• That release must then reach your device and become the version you’re running.

Downloading an update doesn’t necessarily close the second gap if the browser still needs a restart.

Microsoft’s Browser Vulnerability Research team recently described attacks against Chromium-based browsers that exploited this timing. Attackers can examine publicly available security-related code changes, work out the underlying flaw, and target browsers that haven’t received or activated the fix. The researchers say AI-assisted analysis could shorten the time needed to develop those attacks.

We’ve covered the urgency of browser patching before, including an emergency Edge security update in our Microsoft weekly roundup. The new update work targets the recurring problem behind those alerts: a released fix doesn’t help until it’s running on the device.

Edge can ship urgent fixes without waiting for Chrome

Microsoft also makes clear that being built on Chromium doesn’t mean Edge must always wait for Chrome’s corresponding release.

In its recent security research post, Microsoft described independently isolating and backporting Chromium fixes during an actively exploited attack campaign. One additional fix began rolling out in Edge on September 4, with Chrome’s corresponding Stable update following on September 8.

That example isn’t proof that Edge will always receive every security fix first. It shows Microsoft can accelerate individual fixes when it determines that urgent protection is needed.

The same research post says Edge may ship critical security updates before the corresponding CVE information is published. In other words, waiting for a detailed vulnerability announcement before updating can leave you behind a fix that’s already available.

Security Update Alerts give businesses a clearer view

For IT teams, the immediate news is Security Update Alerts in the Microsoft Edge management service.

Admins can set a minimum severity threshold and receive dashboard alerts and email notifications when a newly released update includes fixes meeting or exceeding that level. The experience also highlights updates addressing zero-day vulnerabilities.

The Monitoring dashboard provides details including:

• The Edge version released and its release date.
• The highest severity of the vulnerabilities addressed.
• The CVEs fixed in the release.
• How many managed devices may need updating, broken down by channel.
• The latest available version across Edge channels.

From there, admins can recommend a restart or configure automatic restarts when devices are idle. Microsoft’s documentation currently defines the managed idle period as 20 minutes without user input and says tabs are restored after the restart. It also warns that entered content may be lost.

According to the October 15 announcement, Security Update Alerts are available now for managed Windows devices without additional licensing. Microsoft’s documentation confirms that the dashboard’s monitoring data is currently limited to Windows devices and requires version monitoring to be enabled.

What’s available today—and what isn’t?

The announcement covers three separate capabilities, and they shouldn’t be lumped together:

Capability	What it does	Availability
Seamless updates	Transitions Edge to a newer version while open work continues, without a browser restart prompt	Early working prototype; not shipping
Restart to update on idle	Restarts Edge during device idle time, applies an update, and restores tabs	Available now
Security Update Alerts	Helps admins identify important security releases and managed Windows devices that may need updating	Available now

Microsoft’s existing guidance remains to keep automatic updates enabled, apply updates promptly, and restart when required. The seamless prototype doesn’t change that advice yet.

We’ve previously covered security improvements such as passkey saving and syncing in Microsoft Edge. This announcement tackles a more basic requirement: making sure browser security fixes actually reach the people who need them, without asking them to abandon what they’re doing.