Tasker’s Puzzle: Edge and Other Processes

The Windows Task Manager is an important tool for gathering a summary of your system performance, so it’s crucial that this tool does its job properly. You may have noticed that some processes get sorted underneath program headings that they shouldn’t, such as Microsoft Edge.

Let’s have a look at why this error occurs, and how we might fix it.

Why Do Unrelated Processes Appear as Microsoft Edge Processes?

It’s not entirely clear what the source of this error is. Using Edge more will increase the likelihood of running into this issue, but it can happen regardless of whether Edge is currently in use or not.

Some users speculate it may have to do with how Edge handles sandboxing , as well as how it handles additional processes that it generates.

Regardless of the cause, it can create a huge headache when browsing through processes. Thankfully, it’s fixable.

How to Restore Process Titles to Their Original Names

There are two fixes for this issue. The first, and easiest, is to reboot your system. This will restore your process names, but it can be very inconvenient. A more permanent solution is within the Edge settings menu.

Open Edge, navigate to Settings, then System and performance, and disable both Startup boost and Continue running background extensions and apps when Microsoft Edge is closed.

You may need to restart to restore the process names, but with these two settings turned off, Edge will no longer mess with process names.

Power Tools add-on for Google Sheets, Lifetime subscription

Should I Stop Using Edge to Prevent This Bug?

Click here

As long as the above settings are switched off, you shouldn’t have to worry about your processes being listed under the wrong program label.

Considering this bug can, very rarely, occur with other Microsoft programs as well, the most permanent fix available might be to wait for Microsoft to address and patch this bug in a future update.

Turning Off a Few Settings Fixes Mislabeled Process Names

It’s a relief that mislabeled process names can be fixed so easily with a few settings. However, if you’re someone who likes to have those settings enabled, it’s not an ideal fix.

Hopefully, Microsoft can tackle this issue in a future update, and correct this rather annoying oversight.

Let’s have a look at why this error occurs, and how we might fix it.