A laptop displays a Microsoft Edge update and security check in a bright modern office.
Microsoft's roadmap now lists a plan for Edge to finish installing updates without interrupting people who are using the browser. Roadmap item 581801, titled "Microsoft Edge: Smarter and faster update application," says Edge can apply pending updates when the browser is idle. It also says Microsoft has updated the RelaunchNotification policy so organizations can manage those idle restarts. The item is marked In development, with general availability targeted for January 2027, for Worldwide (Standard Multi-Tenant) customers.

This is a plan, not a shipped feature. Microsoft says its roadmap gives estimated release dates for commercial features and that all of the information is subject to change. Still, it addresses a real problem for IT teams: a browser can download a security fix but keep running the old version for days while the user ignores the restart prompt.

A laptop displays a Microsoft Edge update and security check in a bright modern office. The problem: the update is downloaded but not running​

Edge, like most Chromium-based browsers, usually downloads updates in the background. It runs the new version only after the browser relaunches. Microsoft's support documentation says today, many browsers – including Edge – wait for you to manually close and restart your browser to apply updates.

That waiting period matters for security. The Defense Information Systems Agency (DISA) Security Technical Implementation Guide for Edge includes a rule saying users must be required to restart the browser to finish installation of pending updates and prevent users from continually using an old/vulnerable browser version. If a fix has been downloaded but isn't running, the browser is still unpatched.

The roadmap item is meant to shorten that period without forcing a restart in the middle of a video call.

What the roadmap item says​

The roadmap entry makes two specific claims:

  • Idle update application: Edge can apply pending updates when the browser is idle.
  • Admin control: Microsoft has updated the Relaunch Notification policy so organizations can manage idle restarts.

It does not provide:

  • The idle threshold for the managed or enterprise version
  • New policy values, a schema, or ADMX changes
  • A minimum Edge build
  • Rollout timing within January
  • Any measurement of how much "smarter" or "faster" the process is

The roadmap also lists Web as the platform. Don't treat that as a statement about which desktop operating systems will support the feature. The existing relaunch policies are documented for Windows and macOS only.

Section summary: Microsoft has said it intends to let admins control idle restarts through RelaunchNotification. It has not published the policy changes or other details yet.

The consumer version that already exists​

Microsoft already ships a consumer feature that does something similar. Its support page describes Restart to update on idle - a new opt-in feature that relaunches your browser when you are away from your computer to apply pending updates.

Here is how that feature works, according to Microsoft:

  1. If the device is idle for 15 minutes with no active wake locks, the feature displays a notification informing you of a pending browser relaunch.
  2. Upon displaying the notification, the feature starts a 5-minute countdown for Edge to relaunch.
  3. If you continue to be idle with no active wake locks during this time, the browser relaunches to apply the pending update.

To turn it on:

  • In Edge, go to Settings > About Microsoft Edge. You can also go to edge://settings/help.
  • Turn the toggle On for Restart to update on idle (Instant update if you are in a version earlier than Edge 156).
  • Turn the same toggle off to disable the feature.

WindowsForum's earlier coverage noted a gap for businesses. Microsoft's Edge blog said organizations could configure the feature through policy, but the support documentation said Restart to update on idle currently does not have an associated group policy. That coverage also noted that Restart to update on idle does not function when an InPrivate browsing window is open.

The new roadmap item looks like Microsoft's answer to that gap, delivered through an existing policy instead of a new one. That is a reasonable reading, not something Microsoft has confirmed. Don't assume the managed version will use the same 15-minute threshold and 5-minute countdown until Microsoft publishes the policy details.

How Edge relaunch policies work today​

The idle-restart controls will be added to existing relaunch policies, so it helps to know the current settings. Microsoft's policy index lists five policies in the Relaunch group: RelaunchFastIfOutdated, RelaunchNotification, RelaunchNotificationPeriod, RelaunchWindow and UpdateOnZeroWindowEnabled.

PolicyWhat it does todaySupported versions
RelaunchNotificationSets whether the restart prompt is "Recommended" (1) or "Required" (2)Windows/macOS 77+
RelaunchNotificationPeriodSets how long the notification period lasts, in millisecondsWindows/macOS 77+
RelaunchWindowMoves the end of a required notification period into a set time windowWindows/macOS 93+
RelaunchFastIfOutdatedShortens the notification period when the running version is oldWindows/macOS 141+
UpdateOnZeroWindowEnabledRelaunches in the background when all windows are closedSee Microsoft's policy documentation

RelaunchNotification. If the policy isn't configured, Edge shows a recycle icon in the menu bar. Set to Recommended (1), it shows recurring prompts that users can dismiss and defer. Set to Required (2), it shows recurring warnings that the browser will restart automatically when the notification period ends. The user's session is restored after the restart.

On Windows, the policy is under Administrative Templates/Microsoft Edge/Relaunch. The registry value is RelaunchNotification (REG_DWORD) under SOFTWARE\Policies\Microsoft\Edge. It supports dynamic policy refresh.

RelaunchNotificationPeriod. If not set, the default period of 604800000 milliseconds (one week) is used. In Microsoft Edge the app menu changes to indicate that a relaunch is needed once one third of the notification period passes. This notification changes color once two thirds of the notification period passes, and again once the full notification period has passed.

RelaunchWindow. This policy defers the end of a required notification period into a time window you choose. Microsoft's example starts at 2:15 with a 240-minute duration. Microsoft also warns that setting this policy can delay software updates. The roadmap doesn't say how idle restarts will interact with it.

RelaunchFastIfOutdated. If the running version has been outdated for longer than the number of days you set, the RelaunchNotificationPeriod policy is overridden to 2 hours.

A documentation inconsistency to check​

The RelaunchFastIfOutdated page says if the RelaunchNotification policy is set to 1 ('Required'), a browser relaunch will be forced at the end of the period. However, RelaunchNotification's own mapping lists Recommended as 1 and Required as 2. That mapping is also published on the ADMX reference site, which lists Recommended (1) = Recommended... Required (2) = Required.

Use 2 for Required. If you're editing registry values by hand, a wrong number here is easy to miss.

Section summary: Admins can already control prompts, deadlines, restart windows and faster relaunches for outdated versions. The roadmap item adds idle restarts to that set, through RelaunchNotification.

What admins can do now​

None of these steps configure the new feature, because Microsoft hasn't published those settings. They will help you prepare.

  1. Check your current settings. Open edge://policy on a managed device and confirm what RelaunchNotification and RelaunchNotificationPeriod are set to. A blog post on Intune configuration recommends the same check: If the policies show up here, they're active.
  2. Consider your compliance requirements. If you follow the DISA STIG, RelaunchNotification must already be set to Required. Idle restarts could let you shorten the notification period without more complaints from users. Wait for the actual policy behavior before you change your baseline.
  3. Review your RelaunchWindow settings. If you push restarts into an overnight window, find out whether idle restarts will override, complement or conflict with that window once Microsoft documents it.
  4. Test on a pilot group. When the policy changes reach the Microsoft Learn documentation and the ADMX templates, deploy them to a pilot ring first. Pay attention to users who often seem idle while working, such as people watching dashboards, presenting, or running long uploads.
  5. Use the consumer toggle to test the general behavior. Unmanaged or lightly managed test devices can show you roughly how idle detection works. The enterprise version may still behave differently.

Open questions​

Microsoft's roadmap item is short, and several things are still unknown:

  • What counts as idle? The consumer feature checks device idle time and wake locks. Microsoft hasn't said whether the managed version will use the same signals.
  • Can admins set the timing? The roadmap only says organizations can manage idle restarts. It doesn't say whether that means a simple on/off setting or adjustable thresholds.
  • Will Recommended mode use idle restarts? In Recommended mode, users can defer restarts. It's unclear whether idle restarts will apply only under Required.
  • What about kiosk and shared devices? On devices where nobody is logged in to take over, an idle restart could be very useful or could cause problems, depending on the setup.

Microsoft also hasn't backed up the "smarter and faster" headline with any measurements. What the item describes is a change in timing: Edge would relaunch while you're away, not while you're working.

Bottom line​

Edge already knows when it needs a restart. The roadmap item says Microsoft wants it to restart when you aren't using it, and to give admins control over that through a policy they already manage. If the feature ships in January 2027 as planned, admins will have another option besides nagging users for a week or forcing an overnight restart. Until Microsoft publishes the policy details, treat this as a plan, keep your current RelaunchNotification settings, and remember that Required is value 2.

 

References

  1. Microsoft Edge: Smarter and faster update application Microsoft 365 Roadmap 2026-11-19T23:37:54.702214Z
  2. Microsoft Copilot Roadmap | Microsoft 365 microsoft.com
  3. Automatically update Microsoft Edge when your device is idle support.microsoft.com