It is not a problem so I think this is the best place for it: my EINSTEIN@HOME starts a dozen or so instances of conhost.exe running on my Windows7 box.
They can easily be killed but they do tend to slowly return.
It really bugged me that I couldn't find what was causing these. I thought I might have worms and viri but I don't. I checked.
As I said, it's no problem, I just thought it was worth mentioning so others don't worry.
"Process Explorer" from Sysinternals helped me track E@H as the source.
See http://answers.microsoft.com/en-us/windows/forum/windows_7-security/multiple-instances-dozens-of-conhostexe-running/6e8c045f-8738-4e20-87e2-56d4360f1bd3 for more.
Copyright © 2024 Einstein@Home. All rights reserved.
Multiple conhost.exe instances running in Windows 7.
)
As from http://boincfaq.mundayweb.com/index.php?language=1&view=584:
Conhost.exe is the console wrapper Windows uses for console based applications.
BOINC doesn't start it directly. When an application is launched, the Windows application loader determines what sub-system the application belongs to and then proceeds to launch the correct sub-system before launching the application.
In any case, it is a Windows thing. The science application would have to change its application type to a windowed application instead of a console application.
RE: As from
)
Cool. Thank you. Sorry, I searched for that sort of thing in the FAQ'a and fora once I'd tracked down who was starting the conhosts but I must have missed it.
Apologies for repeating information already available.