The dependency service or group failed to start

You'll probably think I shouldn't complain about this, because my Dell
Vosto laptop connects perfectly via my Netgear router. But the icon in
the System Tray has a red cross through it, and the message it displays
is: Connection Status Unknown: The Dependency Service or Group Failed to
Start.

I use Trend Micro Internet Security for anti-virus and firewall, so
tried turning them off. Still no good. I've gone into the Network and
Sharing Center, where it says Network Discovery and File Sharing are
both switched off. When I try to switch them on I merely get the same
message (The Dependency Service or Group Failed to Start).

So: how do I start them? Or do I just say what the hell, at least I'm
connected?

If you are a home user in the United States, go to Trend Micro Home User
Support ...

http://esupport.trendmicro.com/suppo...o?locale=en_US

On that page, in a yellow box, you will see a link about the detection of a
trojan ... follow that and see if it gives you any help ... it did not help
me. I had already clicked on the message box that said to delete the
"infected" files, which, upon restart, promptly deleted my NLA Service
(among other things). I started getting the same thing you did ...
dependency failed to start ... fortunately for me, I was just about to
install Service Pack 1 and Windows Update was still working ... how, I have
no idea, but it did. When Service Pack 1 completed installation, all was
well.

Thanks for that. I don't have any quarantined filed available to be
restored through Trend Micro, so I probably deleted them, like you. I'll
have a look at SP1. All best.

I had the same issue and as it is a corrupt TCP/IP Stack

To fix, you will need to run a command prompt as administrator
Start > All Programs > Accessories > Command Prompt (Right-Click and
Run as Administrator)
At the command Prompt type : netsh winsock reset

Ignore all errors, restart your computer and networking should work

[BarryJG]

I'm replying to an old posting, but I want to thank Rbatrack for his solution to the problem. The wireless connection on my Gateway laptop with Windows Vista operating system was red x'd out and I got the same message "The dependency service or group failed to start". When I tried connect I kept getting the message "Start DHCP client Service". But it wouldn't start. I was thinking I might have to reinstall Windows. I did a search on "dependency service or group failed to start" and along with several other links that didn't help, I found this topic on this forum.
I tried the solution above from Rbatrack and it worked! I'm connected!

[yazeed16]

Your are The MAN...

My father's laptop was having the same issue and i did everything i know, and i was so close to format his laptop. But thank god i found your post it solved the issue.

If you don't mind i want to copy your solution and post it in my blog with reference to you and to this forum.

[wallaroo]

I tried this twice and it didn't work for me - anyone got any other ideas??

[Alterhit]

I never post anywhere on technical help forums but that reply about the command prompt was soo good and fixed everything that I have to take my hat off to the author. Cheers man.

[tsisante00]

Click the start button, search for cmd. Right click, run as Admin.
1) netsh winsock reset
2) netsh int ip reset
3) net localgroup administrators localservice /add
4) net localgroup administrators networkservice /add
5) exit
Then reboot.

did it for me.

[silentspeaker]

Thank you so much, you are all life savers, literally. I have been fighting with my computer for over 2 weeks now and was about to pay to try and get it fixed or be forced to reinstall the operating system but thanks to your suggestions the problem is solved. THANK YOU SO MUCH!

[insomnai]

Dear lord, I've been struggling with a laptop with this issue for a short time, tried alsorts. Inplace upgrade, netsh winsock reset, reinstalling the device drivers thinking it might show up as faulty, chkdsk to see if drive was on its way out, memcheck, grrrr. None of it worked.

Until the magic that is "tsisante00" showed up. 3 things which I completely forgot to do. reset the ip, adding permissions to localservice and networkservice.

Noob mistake.

Cheers my good man and Happy New Year!

[yardheater]

After reading the previous threads and trying all manner of fixes including long chat sessions with microsoft (which seem to have made matters worse) I still can't solve the problem. I have tried system restore but it will only go back as far as the last attempt to install SP1, which was the cause of the problem in the first place. If anyone has any further ideas I would be eternally grateful. One thing that I have noticed is that when attempting to add localgroup administrators networkservice, cmd came up with 'no network service found'. Any suggestions?

[Lemog]

You can try this and see if that is helping you or not. Just go to Start>Run and type in services.msc afterward press Enter. After that you will see find Print Spooler on the left of the window. You will have to right click on that and select Properties from there. Go to Recovery tab and modify three drop-down boxes and that will restart the Service. Confirm that two text boxes underneath say 1 within them. Click Ok till you go back to the Services window. Once you have done this then it will reset if your Print Spooler craps out.

[sunrisetraveler]

Hats off tsisante00 for that! Cheers!

[Rehd]

Thank you .. this work, saved me a complete reload.. Thank you very much..!!!

[onlythistime]

Hurray!!

Thank you "tsisante00"

I had this problem from couple of days, The suggestion from tsisante00 helped.

There was one problem though in the beginning, while trying the
"netsh int ip reset"
command it would display following message.
"The requested command requires elevation"
the solution to that is to right click your command prompt(cmd) and select RUN AS ADMINISTRATOR
then type in the three magic lines one after the another to get a successful result. Do not forget to reboot after entering all the commands.

Cheers to all once again.