I posted the following below in another thread under Diagnostic policy service not running. Sounds related --------Came across several postings about this and related. Forgive me for not being more articulate with communicating techincal terms, but I will try and keep it short. I will check to see if it helps or anyone needs more info. First I read in a thread posting the problem could have something to do with group policy on my computer "Local Service" not being established. The thread, as I remember, refered to a "netsh command" under the CMD prompt to establish the "Local Service" group ( for the newby I guess, many services belong to this group) exsisted. I found out that I received an error because my group did. Probably good to check any way. Next, the thread, not sure if it was the same one fore mention, (I have been spending quit a bit of time trying to solve this problem with out crashing my computer. So fellow newbys beware!) I ran a pre-exsisting snap-in console "Comexp.msc" and checked the security settings for "my computer". If needed I will go into more details about securty settings for any that may need or want. But I prefer at this point you try looking into other threads on that subject if you are that new. Started this task because of frustration with vista. But, don't want to seem basis about software. Since the economy is bad, freely shared info to solve problems (whether good or bad) I think is the solution to many problems.
I tried the various methods listed - none actually worked for me but then I had a "once in a lifetime" piece of lateral thinking:
If Vista is complaining about not being able to start a service then maybe it's been disabled. So I looked in Services (Admin Tools) and clicked the Startup Type column so they were sorted and easy to see which ones were disabled.
Sure enough, there was Network Location Awareness marked as Disabled (it was that I was having trouble with). I changed it to Auto and everything now works. Of course I could have changed to Manual and started it when needed.
Problem: Dependency service or group failed to start
To solve this, you can check the service COM+ Event System. If this service is disable or stop, we cannot start any other services, and we often see the problem above.
If after starting that service, the problem appears again, you can find the other way.