Microsoft is developing a way for Edge to install a new browser version while users continue working. In an October 15 announcement, the company demonstrated a prototype designed to preserve open tabs and ongoing activity during an update.
The approach could reduce the delay between a security fix becoming available and users actually receiving its protection.
A prototype, rather than a released feature
Microsoft says the experimental system moves the browser and its supporting processes to a newer version without requiring the usual relaunch. Its demonstration included keeping an unfinished form open during the transition.
However, the company explicitly describes the technology as early development work. It is not currently part of production Edge code or Chromium, so users should not expect this behavior simply by installing the latest browser update.
An existing option updates Edge during inactivity
Users can already enable a separate feature called “Restart to update on idle.” This option still restarts the browser, but waits until the device is inactive before applying a pending update and restoring tabs.
Microsoft’s support documentation says the feature is disabled by default. Users can find it under Settings, then About Microsoft Edge, or by entering edge://settings/help in the address bar.
The documented process checks for 15 minutes of inactivity, then displays a five-minute countdown before restarting, provided the relevant conditions remain satisfied.
Restoring tabs does not guarantee that every unfinished task survives. Microsoft warns that unsaved documents or incomplete forms may lose content. The feature also does not operate in InPrivate browsing mode.
Organizations can track update gaps
For managed Windows devices, the Edge management service provides a dashboard showing browser versions and update status. Administrators can identify devices running older releases and recommend a restart or configure one during inactivity.
Security alerts can also be filtered by severity. The dashboard includes information about addressed vulnerabilities and the devices that may require an update.
These controls give IT teams a way to prioritize deployment rather than relying solely on individual users to notice an update prompt. They are separate from the experimental technology that would eventually allow an update while active work continues.
