Sign in with
Sign up | Sign in
Your question

Can't delete device driver even in Safe Mode

Tags:
  • Microsoft
  • Device Driver
  • Windows XP
Last response: in Windows XP
Share
December 26, 2004 8:45:56 PM

Archived from groups: microsoft.public.windowsxp.general,microsoft.public.windowsxp.hardware (More info?)

How can I get rid of an old driver entry which is causing my Windows
Explorer to run slowly?

This is the background ... some time ago I put a (Hauppage) PCI
Television card into my PC but I later took it out.

More recently I noticed that Windows Explorer was running slow and
when I used Regmon (by System Internals) I saw Explorer was
repeatedly calling to a device number (8CAF7FD9-A83D-4D52-89F1-
D7F1D7E81CD) which turned out to refer to the old TV card.

By using Show Hidden Devices in Device Manager I saw the driver is
called "Microsoft TV/Video Connection". But my XP Pro (SP1) won't
let me uninstall it. Even in Safe Mode it prevents me and says:

"Failed to uninstall the device. The device may be
required to boot up the computer."

Device Manager points to C:\WINDOWS\System32\DRIVERS\NdisIP.sys
version 5.03.0000.0900. As soon as I delete this file, XP
immediately creates a new one.

How can I uninstall the driver entry from XP?

More about : delete device driver safe mode

Anonymous
December 26, 2004 8:45:57 PM

Archived from groups: microsoft.public.windowsxp.general,microsoft.public.windowsxp.hardware (More info?)

NdisIP.sys is Mocrosoft's driver for DirectShow or something like this.
It isn't part of the problem and there is no point in deleting it.
Moreover, as you see, it is protected, you can't delete it.
--PA

"Zak" wrote:
> How can I get rid of an old driver entry which is causing my Windows
> Explorer to run slowly?
>
> This is the background ... some time ago I put a (Hauppage) PCI
> Television card into my PC but I later took it out.
>
> More recently I noticed that Windows Explorer was running slow and
> when I used Regmon (by System Internals) I saw Explorer was
> repeatedly calling to a device number (8CAF7FD9-A83D-4D52-89F1-
> D7F1D7E81CD) which turned out to refer to the old TV card.
>
> By using Show Hidden Devices in Device Manager I saw the driver is
> called "Microsoft TV/Video Connection". But my XP Pro (SP1) won't
> let me uninstall it. Even in Safe Mode it prevents me and says:
>
> "Failed to uninstall the device. The device may be
> required to boot up the computer."
>
> Device Manager points to C:\WINDOWS\System32\DRIVERS\NdisIP.sys
> version 5.03.0000.0900. As soon as I delete this file, XP
> immediately creates a new one.
>
> How can I uninstall the driver entry from XP?
>
July 10, 2010 7:32:30 AM

NdisIp.sys causes lots of problems and can be disabled or removed. Amongst other things, it messed up my Skype and webcam setup, as well as causing my computer to freeze or slow down, even after completely removing Skype and the webcam . It uses an IP address to access video/graphics cards, but sometimes the computer thinks it should connect to the Internet, because of the IP address that is used. This is a stupid, screwed up effort by Microsoft, but they show almost no interest in solving it. According to Microsoft, it will go away after you reboot .... it very seldom does. It usually remains, in the form of a "ghost" device, and continues to cause problems. It is automatically installed when you add a webcam, or video capture card, or a digital camera, or after connecting your PC to a TV monitor, or if you use P2P networking. You cannot delete or disable it in Windows. The best way is to rename the file using a boot cd and by deleting all references to it from the KSCAPTOR.INF file: The correct fix is to edit the file \WINDOWS\INF\KSCAPTUR.INF and
comment out any rows containing "NDISIP" (insert a ";" before them). After this it will be harmless to connect a camera. In my KSCAPTUR.INF file there are 3 entries:

Code:
; Install NdisIP miniport
;HKLM,Enum\Root\NDISIP\0000,HardwareID,,"NDISIP"

; Install NdisIP miniport
;HKLM,%RunOnce%,"NDISIP0",,"rundll32.exe streamci,StreamingDeviceSetup

%NdisIP.DeviceId%,NDISIP,%NdisIP.GUID.BDANetInterface%,%17%\ndisip.inf,NdisIP.Reg"

;NdisIP.DeviceID="{48926476-2cae-4ded-a86e-73ddebed6779}"
;NdisIP.GUID.BDANetInterface="{9aa4a2cc-81e0-4cfd-802f-0f74526d2bd3}"
Related resources
July 11, 2010 10:39:29 PM

A most excellent reply, and entirely correct. Now I have one little question...

Do you suppose after 6 years, the OP will will come back to check if he's been answered?
July 12, 2010 9:16:02 AM

tigsounds said:
A most excellent reply, and entirely correct. Now I have one little question...

Do you suppose after 6 years, the OP will will come back to check if he's been answered?



I posted that solution so that other people, like me, who search the Internet for answers and keep landing on pages that pose the same question, but offer no solution, are spared the frustration. As far as this particular issue is concerned, I found this solution somewhere on the net and it worked for me, but I had to view about 40 pages where it was either left unanswered or debated without any firm advice or working solutions being given. Now, at least when someone lands here, they will have a better shot at fixing the problem.
July 12, 2010 3:44:30 PM

Yes, that is a great reason to reply to an old post. I've been there myself looking for an answer only to find hundreds of questions that matched mine and nobody ever left so much as a bread-crumb trail towards the answer. It's like when they learned what to do, they vanished.

I say again, A most excellent reply, and entirely correct- with a purpose.
:hello: 
!