Im in XP x64 atm so cant check service names, If anyone is going to tweak network services, please attempt it in a VMware or similiar, first. Messing with your actual host install is a bad idea, if you dont know how to revert things back to default, alas backup is handy:
(if u just skipahead, you miss out probably, plz read
)
0: First, a reminder when messing around in registry and you know you will do something windows doesnt expect per se, i always unload/disable any thing on startup from run and runonce and whatnot registry keys as well as from startup folders. Also remember the hidden systemprofile. In addition, to tweaking network services, i would like to point out one other important thing that should be checked into before u get to that:
Task scheduler in vista. It contains a lot of program/task schedules,
that i *of all my heart and mind strongly suggest* you look into 1st.
I dont even know where to begin with that, but like disable and delete the bloody:
customer improvement experience program
trancient multi monitor manager (i have multiple monitors, and they worked just fine, its a laptop external monitor thingie tbs.)
The all upnp services (doesnt mean upnp wont work)
bluetooth unloaderloader service, as well as for wireless
disk defragging service
and boatload of totally other crap.
This is important: *EVERYTHING* is *connected* *somehow*, and if you tweak something, read:
do any action that disables something that something else relies one and when that tries to operate, and get answear it cant coz the service/program/task isnt available, isnt running, is deleted or whatnot, you end up getting system delays, event log errors, and all things could really,really crash and burn, and before you know it, you are thinking you need to reinstall. It's vitally important that anyone going about doing tweaking know their stuff, because unless you take precautions, as in backup, and you are prepared and have the time to fix the system, you should not be messing with services etc that could break functionality that you actually need. Either you are ALL-IN or you should stick with just disabling stuff that windows actually provides an option for. Going about in registry and services.msc for that matter, isnt to be taken lightly. And Vista is so bloated, it can quickly become a headache to keep it all together.
Enough bloated talk:
...
I'm simply saying im not responsible, lol, and take you PREcautions, being sorry afterwards isnt going to help. Having said all that :
Please read all of the following first before you start messing about on anything:
1: simply start services.msc on vista
2: Find f.ex network list service, and take note of the actual service name.
3: Start Regedit
4: F3 and input service name. Should start search under currentcontrolset (not 001 or 002, just "currentcontrolset) btw.
5: Export the registry key and check that it contains the service as original.
6: rinse and repeat for remaining network services, this is very important. you need this incase you make a total mess, or simply to be safe for that matter.
7: Now that all backup is done. You should check on your network adapter, that you UNCHECK things like iPv6 and everything except tcpipv4. The reason WHY you should to that, is because you are going to tell windows then, to not need any other network service, for the time being. This is good as you prevent, at least in theory, windows to access/start other things. And windows like to do things we dont want it to do, lol.
8: Now lets see, i have to think, hmm.. the utterly crappy IpV6, this is a whole other story as well. Crap.
Ah yes. You need to add to registry a Dword 32bit key, Called DisabledComponents.
Look just google "ipv6 vista" and disabledcomponents. It's a bitmap key and i believe the value should be 255, but dont take my word for it.
Im having a hangover, so bare with me lol =)
You see vista is so-called-made-for-the-future-and-is-by-default-enabled-for-all-such-new-s***-that-most-people-dont-actually-use.
But could perhaps use. Ipv6 is strongly built into vista and cant be taken away/disabled lightly. you need to also disable AFTERWARDS some of the network devices, under device manager, network devices, not your network card tho lol, so that you minimize ipv6 things.
Now i have long since realized this is too complicated to undertake explaining it all here, so should probably start another post and take more time to build the answear...
Anyway, you should by now have all things disabled in network, and removed dependencies, make sure in registry keys you have f.ex the RPC service standing and its a *empty* line beneath it, alas memory is failing me at this point but not all services dont necessarily have it. But its a crucial windows service anyway. dont mess with it. *period*.
Now check back on, enable, network lan on network card under network connections. you shouldnt need the new services, just keep printer/file sharing and sharing for microsoft network. Pain in the arse to explain this without reference lol =))))
all the network services you disabled, should not start even if set to manual.
However, do not panic if they do start, it simply means you have missed a service.
I think i failed utterly at explaining this, and feel i have forgotten something =(.
ANYWAY!
You would have at least managed to get a bit faster startup-time of vista, since you not having such network service on automatic, and they wont startup automatic before they are needed (they shouldnt be needed if u have disabled/removed all dependencies needed)
. IF all services start anyway before you have accessed lan, you have missed something. and of course, network connections service shouldnt be on auto.
I think you also need to disable something else not directly thought of as network. I just cant remember atm.
TranceEnergy, on May 20 2008, 05:58 PM, said:
Frontpage
Forums
Tutorials
Members
Calendar
Subscription
Donate
Links
Contact 
Help
Back to top