Generic Host Process for Win32 Servies?

Question

Something called 'Generic Host Process for Win32 Servies' is trying to access my computer, what is it and should I denie it access?

Note: No stupid answers!

Answer 1

Its probably OK. But sometimes virus deceives as it.



To be safe run a good program to check it...



I suggest..



Superantispyware. Finds viruses and spyware that are very very hard to find with no conflict to other antivirus software. http://www.superantispyware.com Update (manual) daily free.

Answer 2

You may have taken your machine out of default settings. You should not fiddle with your machine unless you are sure of what you are doing. A new machine should connect to the internet w/o a problem, other than some help from your ISP or Router manufacturer if you use a router. First, Maybe take your machine to a local MOM and POP service company for a FREE diagnostic check - "JUST say I can't connect to the Internet - is there something wrong with my machine." If it needs work it may cost you a nominal minimum fee to fix and save you a lot of time. If you "fiddled" with the machine, you probably voided the warantee by doing so. Having a good local service company will also come in handy later. So don't do things if you are not sure. Generally your machine manufacturer andyour ISP are the first to talk to for connection problems. Try to avoid creating additional problems.

Answer 3

It's a normal process....allow it

Services Reliability

The last area of reliability improvements is in the area of the services infrastructure. Prior to Windows 2000, some services shared a process with other services and some ran in their own process. Windows 2000 introduced the generic service host process, Svchost.exe. The goal was to reduce system resources by consolidating the various processes hosting built-in operating system services into a single process. Or, it could permit the system administrator to configure the system to run certain services in their own processes, which would prevent one service from corrupting the private memory of other unrelated services (this capability is not documented or supported yet).

If you look at the Windows XP process list in Task Manager , you will notice at least four Svchost.exe processes: two running under the SYSTEM account (sometimes referred to as LocalSystem) and two running under two new service accounts: NETWORK SERVICE and LOCAL SERVICE.



One of the two Svchost processes running under SYSTEM hosts the bulk of the services, 29 of them in total. The second one hosts a single service, Remote Procedure Call (RPCSS). The reason this service needs to be in a separate process is that user-written DLLs are loaded into this process. By having RPC running in its own process, these DLLs cannot adversely affect the operation of the other built-in operating system services. The Svchost process running under NETWORK SERVICE hosts a single service, the DNS Client. The Svchost process running LOCAL SERVICE hosts the TCP/IP NetBIOS Helper, Remote Registry, Simple Service Discovery Protocol, and Web Client services.

The reason for the two new service accounts is to improve system security by reducing the privileges that services run with. LOCAL SERVICE is a built in account that doesn't need a password to log on. The account has only a few privileges, and is not a member of the local administrators group. So, if a service that is running under this account is compromised, it cannot take down the whole machine. LOCAL SERVICE also has no network credentials, so attempts to access a machine on the network will connect with the null session. The NETWORK SERVICE account has the same set of privileges as LOCAL SERVICE, but has access to the machine's credentials for outbound connections, similar to the SYSTEM account.



here is another good link

http://www.wilderssecurity.com/archive/index.php/t-15463.html