BleepingComputer.com: Tcp/ip Protocol Driver Service Failed To Start

My laptop was surfing very nicely via my wireless network a couple of days ago. Yesterday, I couldn't get it to connect. I tried repairing the connection, rebooting the router, etc.

Today, I tried a wired connection which failed as well. Further investigation revealed this entry in the event log:
"The TCP/IP Protocol Driver service failed to start due to the following error:
The system cannot find the file specified.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp"

The EventID is 7000 if that helps anyone. The link was no help to me.

I have googled to exhaustion, but haven't found a solution. How do I fix this? How do I determine what file is missing, find it, and restore it?

I need to use that computer to do some work for a client, so need to fix this ASAP. Please help me.

Laz

I take it this is everytime you start your laptop up? Try and start the service manually if that doesn't work then you may have to re-install Windows onto your laptop. It is not usual for the TCP/IP service to fail.

Hello,

Are you on XP? If so, you can go to control panel, and select network connections, right click on the adapter that is causing you problems, select properties. on the new window that has opened, go through the list and see if internet protocol tcp/ip is there, if it isn't there, click install select protocol then select internet protocol tcp/ip from the list and install it. reboot and see if it all works.

What security set up are you running, it might be prudent to post a hijackthis log in bleeping computers forum, just to be sure.

Hope this helps

REALLY REINSTALLING TCP/IP
Complete destruction and restoration of dead TCP/IP stack
Recovery from fatal failure or partial or complete corruption of TCP/IP.
For virus related problems, please consult tcpip.sys to ensure it is not a corrupt version before following these steps.

This solution is an alternative to reinstalling by partial method or by using winnt /unattend which I very much wanted to avoid.

Here is the hardcore method when nothing else is working. I have cobbled together these suggestions through various forums to offer them here as a concise solution. There are no guarantees! Back up anything relevant and set a system restore point to cover your ass. I discovered this method after all other solutions failed.


Related error messages:
"TCP/IP network transport is not installed" error message from active sync
TCP/IP driver missing from devmgmt.msc showing hidden devices
ipconfig produces immediate failure message :
Windows IP Configuration
An Internal error occured: The request is not supported.
Please contact Microsoft Product Support Services for further help.
Additional information: Unable to query host name.
"the specified device instance handle does not correspond to a present device" message regarding DHCP service in services.msc
net start tcpip >>> fails with system error 2, The system cannot find the file specified
ping error: "Unable to contact IP driver, error code 2"
Repair Local Area Connection: Failed to query TCP/IP settings of the connection. Cannot proceed.
"Tcp/ip Protocol Driver Service Failed To Start, system cannot find the file specified"
"The TCP/IP Protocol Driver service failed to start due to the following error: The system cannot find the file specified"


Failed repair methods:
netsh int ip reset resetlog.txt >>> no effect
non-full reinstall of TCP/IP using only the have disk method. >>> no effect
netsh Winsock reset >>> no effect
http://www.snapfiles.com/get/winsockxpfix.html >>> no effect
reinstalling network card >>> no effect

MY SOLUTION:::

Step #1
Full uninstall of TCP/IP ... no bullbleep.
----------------------------------------------------------------------
These steps are copied from http://support.microsoft.com/kb/325356
11. Locate the Nettcpip.inf file in %winroot%\inf, and then open the file in Notepad.
12. Locate the [MS_TCPIP.PrimaryInstall] section.
13. Edit the Characteristics = 0xa0 entry and replace 0xa0 with 0x80.
14. Save the file, and then exit Notepad.
15. In Control Panel, double-click Network Connections, right-click Local Area Connection, and then select Properties.
16. On the General tab, click Install, select Protocol, and then click Add.
17. In the Select Network Protocols window, click Have Disk.
18. In the Copy manufacturer's files from: text box, type c:\windows\inf, and then click OK.
19. Select Internet Protocol (TCP/IP), and then click OK.
Note This step will return you to the Local Area Connection Properties screen, but now the Uninstall button is available.
20. Select Internet Protocol (TCP/IP), click Uninstall, and then click Yes.
RESTART

succesfull uninstallation of TCP/IP will remove numerous keys from the registry including
HKLM/system/CurrentControlSet/services/tcpip
HKLM/system/CurrentControlSet/services/dhcp
HKLM/system/CurrentControlSet/services/dnscache
HKLM/system/CurrentControlSet/services/ipsec
HKLM/system/CurrentControlSet/services/policyagent
HKLM/system/CurrentControlSet/services/atmarpc
HKLM/system/CurrentControlSet/services/nla
These represent various interconnected and interdependant services.

For good measure you should delete the following keys before reinstalling TCP/IP in step #2
HKLM/system/CurrentControlSet/services/winsock
HKLM/system/CurrentControlSet/services/winsock2

Step #2
Reinstall of TCP/IP
----------------------------------------------------------------------
Following the above substep #13, replace the 0x80 back to 0xa0, this will eliminate the related "unsigned driver" error that was encountered during the uninstallation phase.

Return to "local area connection"> properties > general tab > install > Protocol > TCP/IP

You may receive an "Extended Error" failure upon trying to reinstall the TCP/IP, this is related to the installer sub-system conflicting with the security database status.

to check the integrity of the security database
esentutl /g c:\windows\security\Database\secedit.sdb

There may be a message saying database is out of date
first try the recovery option
esentutl /r c:\windows\security\Database\secedit.sdb

this did not work for me, I needed the repair option
esentutl /p c:\windows\security\Database\secedit.sdb

rerun the /g option to ensure that integrity is good and database is up to date.

Now return to the "local area network setup"
choose install > protocol > tcp/ip and try again

reboot.
worked for me.

Replacing the tcpip.sys worked for me. Found the problem PC had a WINLOGON hook infection. After fixing that, and finding no networking services, I discovered that tcpip.sys has been modified that very day. Replaced it with a copy from a good XP machine and all is well now....

ricroz, on Dec 12 2007, 07:20 AM, said:

Thanks for the tip, that really saved me some hassle.

In my case, Windows noticed I'd replaced it (from my working machine) and wanted to restore it, and asked for the XP SP2 CD. That worked and after a reboot, seems okay now. Think I'll go run a virus check on it now ...

Thanks again.

Edit: yep was a virus, "Heur.Worm" running as a fake csrss.exe

This post has been edited by aaardvark: 29 June 2008 - 07:44 AM

ricroz, on Dec 11 2007, 09:20 PM, said:

I had the same problem after installing norton 2009 and found this solution by a google search - many thanks for this , it saved me a lot of hassle

Hi, I'm new here.

I tried the solution posted for reinstalling tcp/ip

everything went ok

but it did not fix the problem, I still do not have tcp/ip running, what can you suggest i do?

thnak alot!

@hublerb,

I had this problem after an unsuccesfull install/uninstall of AVG 8 antivirus. I couldn't get TCP/IP back to work.

The approach hublerb posted solved it ... so thanx a lot.

Arjan

Hi guys and girls

I too got the message:

"The TCP/IP Protocol Driver service failed to start due to the following error: The system cannot find the file specified"

After discovering this thread (thanks) and reading arjan09's comments - I decided to try a shortcut for starters and completely uninstalled my AVG 8.5 using the Control Pane Add/Remove applet.

Rebooted - VOILA! - I was cruising again!

Thanks!

hublerb, on Apr 2 2007, 09:50 PM, said:

Does anybody know if this will work on vista?

MyPcBytes, on Jan 13 2010, 04:57 PM, said:

it does NOT work on vista.
i tried a few steps like changing the nettcpip.inf (but to do so, you have to do the following)
(I stole this from another website)
To take ownership of the file, you’ll need to use the takeown command. Here’s an example:

takeown /f C:\Windows\System32\en-US\winload.exe.mui

That will give you ownership of the file, but you still have no rights to delete it. Now you can run the cacls command to give yourself full control rights to the file:

cacls C:\Windows\System32\en-US\winload.exe.mui /G geek:F

Note that my username is geek, so you will substitute your username there.
this will let you overwrite the nettcpip.inf file - however, when you go to UNINSTALL, the uninstall option is still not available for either IPV4 or IPV6!
wish there was another fix!!!

ricroz, on Dec 11 2007, 02:20 PM, said:

this works on a vista computer even if you get the file from an xp computer.

Just commenting on hublerb's posting to reinstall tcp/ip....that did the trick, and it ended up being easier than i thought. Thanks!

Does it work with Xp Pro?