Reply #2 Top

Quoting Neil, reply 1
The dwm runs under dwm.exe not svchost.

Why is it then threaded under svchost?

+1 Loading…
Reply #3 Top

frode789...Wow...I like that...what are you using to view your running processes?

Reply #5 Top

Quoting frode789, reply 2



Quoting Neil Banfield,
reply 1
The dwm runs under dwm.exe not svchost.




Reduced 79%

Original 756 x 98

Why is it then threaded under svchost?

That means it was started by that process, not that it is part of it.

Reply #6 Top

Quoting Neil, reply 5

Quoting frode789, reply 2


Quoting Neil Banfield,
reply 1
The dwm runs under dwm.exe not svchost.




Reduced 79%

Original 756 x 98

Why is it then threaded under svchost?

That means it was started by that process, not that it is part of it.

 

Gah. Too bad, now I have no idea what the problem is. Oh well, I'll install WB again and see what happens. Thanks.

Reply #7 Top

CarGuy1: Be sure to take a look at some of the other Sysinternals apps, too. I've got them on every one of my computers -- they are just too useful. Tcpview is another great one, as is psexec :)


Mike

Reply #8 Top

Quoting milksama, reply 7
CarGuy1: Be sure to take a look at some of the other Sysinternals apps, too. I've got them on every one of my computers -- they are just too useful. Tcpview is another great one, as is psexec


Mike

I will...thanks.