>windows

File: svchost.png (185KB, 788x1410px) Image search: [Google]

185KB, 788x1410px

>>60505696
shh

>>60505807
1703/15063 uses 1 service host per-service. Which is honestly an improvement, previously if one service shit the bed it took down the whole group in the service host. Hence why wincucks had to have the print spooler service by itself since forever.

>>60505807
Need to install Windows on newly built PC, how do I prevent and avoid the svchost virus?

>>60508429
Delete SysWOW64

>>60508429
>1703/15063 uses 1 service host per-service. Which is honestly an improvement, previously if one service shit the bed it took down the whole group in the service host. Hence why wincucks had to have the print spooler service by itself since forever.
I hope you are joking... It's normal just check what user the process is running under if it's service it won't run under your name

>>60508467
Not joking that much since buying Kaby Lake / Ryzen like someone who wants a good processor means I'm forced to use a bad version of Windows or else forsake security updates for all time

>>60508445
>system32
ftfy
system32 is for 64-bit binaries on 64-bit machine
syswow64 is for 32-bit binaries on 64-bit machine

>>60505807
Seems legit. I know from using Windows XP and seeing a few svchosts in my day.

>>60509271
why they never renamed system32 to system64 and added a link from system32 to system64 for the compatibility layer, I'll never understand.

>>60509271
How about Windows RT, it also have sysWOW64