Windows 10 launches extra thread when running an executable

Mystere · 31 Mar 2015

catalincocis said:

I used Visual Studio 2008.

VS 2008 is no longer in Mainstream support, and will be completely end of lifed by 2018. I wouldn't expect much, if any traction on a VS2008 issue in Windows 10.

catalincocis · 01 Apr 2015

Dude said:

And this is a preview OS....Give feedback to MS

How should I? Do they have an official way or just the Windows Feedback app which they'll probably never read?

SergeyN · 17 Aug 2015

Hi

Windows uses some tracing mechanics which internally uses a threadpool. It looks like it is created even before kernel32.dll gets loaded. I'll let you know if I find out more.

Update:
threadpool is used not only for tracing subsystem, but it is also used to parallelize static imports (i.e. - the dlls your app depends on). Looks like it's the new default to have a few threads hanging around even if you don't use any multithreading in your applications at all.

LMiller7 · 17 Aug 2015

Some DLLs create their own worker threads and this may be what is observed. If the thread does not access anything that is not private to the DLL there is no possibility of conflict.