How to Optimize Microsoft Edge on Windows 11 Multi-Session AVD Hosts

By David, 2026-10-09

On a Windows 11 Enterprise multi-session host, Edge is often the biggest process tree on the machine. Every signed-in user runs their own copy, with its own renderer processes, cache and background tasks. Twenty users with fifteen tabs each is three hundred tabs on one VM. That's why Edge tuning comes up whenever someone sizes a pool. The usual question is which settings are worth it, and whether anyone actually caps Edge's memory.

This guide covers the policies that matter on a shared host, what each one costs your users, and a starting baseline. It also covers how Atlas AVD applies them.

The short version: turn off startup boost and background mode on every multi-session host; they cost memory for users who aren't even using Edge. Turn on sleeping tabs with a shorter timeout than the two-hour default. Use efficiency mode only with always active, because a VM never runs on battery. Treat a memory limit as a per-user guardrail, not a sizing tool: when Edge hits it, it discards tabs.

Why Edge needs its own tuning on multi-session

On a laptop, Edge's defaults trade a little memory for speed: it pre-launches at sign-in and keeps running after you close it. On a multi-session host those choices multiply by the number of users:

• Each user gets their own browser instance. Policies are machine-wide (they live under HKLM\SOFTWARE\Policies\Microsoft\Edge), but their effect is per user, and so is the memory they save.
• Background work runs for everyone signed in. Startup boost starts Edge processes for every user at sign-in, whether or not they open Edge.
• The disk cache lives in the profile. With FSLogix, each user's cache ends up in their profile container, which grows it and slows sign-in.

Every setting below is a Microsoft Edge policy, set with Group Policy, Intune's settings catalog, or the registry. The Microsoft Edge policy reference documents each one.

The settings, by impact

1. Turn off startup boost

Startup boost starts Edge processes when the user signs in to Windows and restarts them in the background after the last window closes. On a personal laptop that makes Edge open instantly. On a multi-session host it means every user carries Edge processes all day, including the ones who work entirely in a line-of-business app. Set StartupBoostEnabled to 0. This is the closest thing to a free win in this guide.

2. Turn off background mode

Background mode keeps Edge processes running after the user closes the last window, so extensions and notifications keep working. Few session users need that. Set BackgroundModeEnabled to 0, so closing Edge actually frees its memory.

3. Turn on sleeping tabs, with a shorter timeout

Sleeping tabs freeze background tabs after a period of inactivity. A sleeping tab keeps its place and its content; it just stops using CPU and gives back most of its memory until the user returns to it.

The default timeout is two hours, which is long for a shared host. SleepingTabsTimeout accepts a fixed set of values in seconds: 30, 300, 900, 1800, 3600, 7200, 10800, 21600 and 43200. 1800 (30 minutes) is a sensible default for knowledge workers. Use 900 on dense pools, and 3600 for users who keep many reference tabs open. Sites that must never sleep, such as a softphone, a dashboard on a wall screen or a web app that holds a live session, go in SleepingTabsBlockedForUrls.

4. Efficiency mode: only "always active" does anything on a VM

This is the setting most people turn on and then find does nothing. Efficiency mode throttles tabs the user isn't interacting with and puts background tabs to sleep sooner. But its default modes wait for the device to unplug from power or run low on battery, and a virtual machine has no battery. EfficiencyModeOnPowerEnabled doesn't help either: Microsoft documents that it has no effect on a device without a battery.

To make it work on a session host, set both:

• EfficiencyModeEnabled = 1
• EfficiencyMode = 0, which is AlwaysActive

Microsoft's own Windows Desktop Optimization Tool sets EfficiencyMode to 0 in its Edge settings for the same reason. Efficiency mode is more aggressive than sleeping tabs alone, so test it with your line-of-business web apps before rolling it out.

5. Limiting Edge's memory: how it works, and when to use it

TotalMemoryLimitMb caps the memory a single Edge instance may use. It's the least widely used of these settings, and it helps to know exactly what it does before turning it on:

• The cap applies to each user separately. It limits one Edge instance, and on a multi-session host every user runs their own. A 2 GB cap on a host with 20 users bounds Edge at roughly 40 GB in the worst case; it doesn't divide the host's memory between users.
• Hitting the cap discards tabs. It doesn't put them to sleep. A discarded tab frees its memory completely and reloads when the user clicks back to it, so a half-filled web form in a background tab can lose its input.
• The minimum is 1024 MB. Smaller values are rounded up.
• It's a target, not a guarantee. Microsoft notes the browser may still run above the limit at times.
• It's mandatory-only. Users can't override it, and it can't be set as a recommended value.

When it's worth it: dense pooled hosts where one user's fifty-tab session can starve everyone else, or hosts that show memory pressure at peak despite sleeping tabs. Start at 3 or 4 GB per user and come down only if monitoring says you need to. A 2 GB cap is tight for users of heavy web apps such as Dynamics, Salesforce or Power BI. The AVD sizing guide covers measuring per-user memory before you pick a number.

6. Keep the cache out of the profile container

Every user's Edge cache lands in their FSLogix profile container unless you do something about it. Two options, which work well together:

• Cap it. DiskCacheSize sets a target size in bytes; 262144000 is 250 MB.
• Exclude it. An FSLogix redirections.xml can exclude cache folders such as AppData\Local\Microsoft\Edge\User Data\Default\Cache and Code Cache from the container. Paths are relative to the profile root. An exclusion doesn't remove data already in a container, and Microsoft warns that exclusions can break applications, so test with your own sites first.

If profiles are already slow to load, the FSLogix troubleshooting guide covers finding what's inside them.

7. Quiet the first run

HideFirstRunExperience = 1 and AutoImportAtFirstRun = 4 skip the welcome flow and the "import from another browser" step. On pooled hosts, where a user's first launch can happen on any host, this saves a few clicks every time. ShowRecommendationsEnabled = 0 turns off feature tips and promotional notifications.

What about hardware acceleration?

On a host without a GPU, Edge already falls back to software rendering, and turning off hardware acceleration can move more work onto the CPU rather than less. Leave it at the default unless you're chasing a specific rendering problem. Then test the change on one host before rolling it out to a pool.

A starting baseline

For a pooled Windows 11 multi-session host running knowledge workers:

Measure before and after. Edge's own task manager (Shift+Esc inside Edge) shows memory per tab and per extension, and Task Manager's Users tab on the host shows the total per user. Compare a busy hour on a host with the baseline against one without it; one host per pool is enough for a first test.

The most common mistake isn't a wrong value. It's setting these on the golden image with gpedit and then losing them on the next image rebuild. Set them as policy (Group Policy, Intune or your management tool) so they survive. The golden image management guide covers what belongs in the image and what doesn't.

How Atlas AVD applies these

Atlas AVD writes Edge policy to session hosts as they're provisioned, from the same screens you use to build the pool.

The Microsoft Edge template. Atlas ships a built-in Microsoft Edge Group Policy template next to Google Chrome. It covers the settings in this guide:

• sleeping tabs, with 15-minute, 30-minute and 1-hour timeouts;
• efficiency mode, kept always active;
• a per-user memory limit of 2, 3 or 4 GB;
• startup boost and background mode turned off;
• a 250 MB disk cache;
• the first-run, import and recommendation prompts.

To use it:

1. Open Host Pools, pick the pool, and find the Group Policy (ADMX) panel.
2. Select Microsoft Edge and choose Assign.
3. Choose Configure and enable the policies you want. Enable one timeout and one memory limit. Each choice is its own policy, so the value you see is exactly the value Atlas writes.

The full catalog lives under Security → Group Policy. Enabled policies are applied to the pool's session hosts at provisioning time. New hosts get them as they're added, and existing hosts get them the next time they're re-imaged or replaced. Group Policy (ADMX) templates are part of the Professional plan.

Edge First Run Disable. In Settings → Provisioning & Deployment → Optimization & Automation, the Optimization Modules list under Global WDOT Optimization includes Edge First Run Disable, which is on by default. It hides the first-run experience and turns off background mode on every new session host. A host pool can override the global setting on its Optimize tab.

The rest of the browser baseline. The same provisioning step can block third-party cookies in Edge and Chrome (Block Third-Party Cookies), push managed bookmarks, and force-install extensions across every pool (Global Browser Extensions), so a new host comes up with the browser your users expect.

FAQ

Do sleeping tabs work on Windows 11 multi-session?

Yes. Sleeping tabs are a per-user browser feature and work the same on multi-session as on a single-user PC. Set them by policy so every user gets the same timeout, and exempt sites that must stay live with SleepingTabsBlockedForUrls.

Why doesn't efficiency mode do anything on my session hosts?

Its default modes wait for the device to go on battery, which a VM never does. Set EfficiencyModeEnabled to 1 and EfficiencyMode to 0 (AlwaysActive). EfficiencyModeOnPowerEnabled has no effect on devices without a battery.

Is limiting Edge's RAM with TotalMemoryLimitMb common?

It's the least used of these settings, and best kept as a guardrail rather than a first step. The limit applies to each user's Edge instance, the minimum is 1024 MB, and when Edge reaches it, it discards background tabs, which reload when the user returns to them. Turn off startup boost and background mode and turn on sleeping tabs first. Add a cap of 3–4 GB only where hosts still show memory pressure.

Does the memory limit cap Edge for the whole host?

No. It caps one Edge instance, and on a multi-session host each signed-in user has their own. The worst case for the host is roughly the number of users times the limit.

Should I disable hardware acceleration on AVD?

Usually not. Hosts without a GPU already render in software, and turning acceleration off can raise CPU use. Change it only to fix a specific rendering problem, and test on one host first.

Does the Windows Desktop Optimization Tool optimize Edge?

Partly. Its Edge settings, an advanced optimization you opt into, turn off startup boost and background mode, hide the first-run experience, turn off recommendations, and set efficiency mode to always active. They don't configure sleeping tabs, a memory limit or the disk cache, so set those separately.

Policy names, values and behavior are taken from Microsoft's Edge policy documentation as of October 2026. Edge changes often; check the policy reference for the version you deploy.