I have a project that includes a GUI executable that launches several background processes that communicate with each other to divide data processing. Recently, I copied the GUI to another machine and recompiled the background executables to test them.

However, when I tried to attach to the launched processes in Visual Studio, I couldn’t find them in the list of processes or in the task manager. Eventually, I discovered that the processes were running under “session 0”, which is an isolation mode in Windows 10, and I needed admin permissions to debug them.

I want to run these executables in my user session, so I need to understand what might have caused them to run in session 0.

What could prompt an executable to run at that level?

Askify Moderator Edited question May 4, 2023