So i know conhost process is fine and to do with the console/cmd process.
However I run process lasso and have Wow set to use only physical processors on my hyperthreaded system. This has the effect that all child processes that wow spawns are only set to physical only processors (wowbrowserproxy.exe etc).
Over the last few days I've seen a (new) conhost.exe process pop up sometimes that is also using only physical cores implying that wow launched it.
I have a lot of conhosts.exe running all the time - most are set to use all 8 cores but thought it was interesting that one wasn't and wow is the only process I lock down to physical (4) only.
However I run process lasso and have Wow set to use only physical processors on my hyperthreaded system. This has the effect that all child processes that wow spawns are only set to physical only processors (wowbrowserproxy.exe etc).
Over the last few days I've seen a (new) conhost.exe process pop up sometimes that is also using only physical cores implying that wow launched it.
I have a lot of conhosts.exe running all the time - most are set to use all 8 cores but thought it was interesting that one wasn't and wow is the only process I lock down to physical (4) only.