Closing the last browser window does not always mean every browser process should exit.
Modern browsers can deliberately keep processes active for background apps, extensions, notifications, synchronization, or faster startup.
Microsoft Edge, for example, has a documented background mode that can keep Edge processes and background apps running after the last browser window is closed. [R1]
Google Chrome also supports a background mode in which background apps can continue running after Chrome is closed. [R4]
The first question is:
Are the remaining browser processes doing expected background work, or are they consuming resources abnormally?
Confirm what is still running
Open Task Manager with Ctrl + Shift + Esc after closing the browser.
Check whether browser processes remain and whether they are using meaningful CPU, memory, disk, or network resources.
A browser process that remains present but is almost idle is different from one that continues consuming substantial CPU or several gigabytes of memory.
For Microsoft Edge, Microsoft recommends using the browser's own Task Manager with Shift + Esc to identify which tab, extension, subframe, or utility process is responsible for high CPU or memory usage. [R3]
Do not assume that every remaining browser process is a performance problem.
Background mode may be intentional
Microsoft Edge has a setting named Continue running background extensions and apps when Microsoft Edge is closed.
Microsoft documents that when Edge background mode is enabled, Edge processes can remain active after the final browser window closes, together with background apps and the current browsing session. [R1]
Chrome provides a comparable background-mode capability. Google's Chrome policy documentation states that background apps and the current browsing session can remain active after Chrome is closed when background mode is enabled. [R4]
This behavior can support notifications or applications that need to keep working without an open browser window.
Edge also has Startup Boost
Microsoft Edge has a separate feature called Startup Boost.
Microsoft documents that Startup Boost can start Edge processes when you sign in to Windows and can restart them in the background after the last browser window closes. [R2]
Its purpose is to make Edge launch faster.
That means an Edge process remaining in Task Manager after the window closes is not automatically evidence of a stuck browser.
Background mode and Startup Boost are separate features, so inspect both when diagnosing Edge.
What if the browser is using too many resources?
That is a different problem.
If Edge continues using excessive CPU after all windows have been closed, Microsoft's troubleshooting guidance specifically recommends turning off the setting that allows background extensions and apps to continue running. [R3]
Microsoft also recommends using Edge's Browser Task Manager to identify an extension or other browser process responsible for excessive CPU or memory. [R3]
A problematic extension may therefore be the real cause even when the overall process appears under the browser's name.
The useful finding is:
“This browser remained active after its windows were closed and continued to consume substantial resources.”
not simply:
“The browser still has processes.”
Should I disable background mode?
If you do not need browser-based notifications, background extensions, or other browser activity after closing the final window, disabling background mode is a reasonable and reversible change.
For Edge, the control is available under its System and performance settings. [R1] [R3]
For Chrome, background behavior is likewise controlled by the browser's background-mode setting. [R4]
The trade-off is that background applications or notifications relying on the browser may no longer continue after you close it.
Should I disable Startup Boost too?
Only if your concern is specifically that Edge keeps core processes ready in the background or starts them at Windows sign-in.
Microsoft states that Startup Boost is intended to improve browser launch speed by starting Edge processes at OS sign-in and keeping/restarting them in the background. [R2]
Turning it off may reduce background presence, but Edge may take slightly longer to open.
So background mode and Startup Boost solve different problems and should be changed separately.
What if the browser still remains after both settings are off?
Then do not immediately start deleting processes, files, or Registry entries.
Check whether:
- an extension is consuming resources;
- another application is using browser components;
- a browser update is pending;
- the process disappears after a short delay;
- the browser is actually hung rather than intentionally backgrounded.
If the process is consuming abnormal CPU or memory, use the browser's own task manager or diagnostic tools to isolate the responsible component. [R3]
What should I do now?
- Close all browser windows normally.
- Open Task Manager and confirm which browser processes remain.
- Check whether they are mostly idle or are materially using CPU, memory, disk, or network resources.
- For Edge, inspect Startup Boost and Continue running background extensions and apps when Microsoft Edge is closed separately.
- For Chrome or another browser, check its own background-app or system settings rather than assuming the controls are identical.
- If resource use is high, use the browser's own task manager where available to identify tabs, extensions, or utility processes.
- Disable background mode if you do not need background browser functionality.
- Disable startup/preloading features only if you accept the possible trade-off of slower browser launch.
- Close the browser again and verify whether the processes and resource use now stop as expected.
- If excessive resource use persists, investigate the specific extension, browser component, or update state instead of applying system-wide cleanup.
The goal is to distinguish normal browser background behavior from unnecessary or abnormal resource use, then change only the browser feature responsible.