Re: how to remove from registery by Don
Don
Tue Nov 09 18:33:11 CST 2004
This is my standard notes on the subject:
Removing all traces of a driver from a system
When testing a device install developers want to cleanup the system so
they can try reinstalling the device, unfortunately this is something
Microsoft hasn't provided an easy way to do. The steps needed are:
1. Delete the files copied by the INF from the system.
2. Delete the INF and corresponding PNF files for the device, from the
inf directory off of the system root. Note, this file is named OEM*.INF and
OEM*.PNF if your driver is not signed. Searching the OEM*.INF files for
your device identifier will determine the OEM* name of your inf file.
3. If your device has a unique class, delete the registry entry in
HLKM\System\CurrentControlSet\Control\Class corresponding to the device
class you created for device. Note the key is named for the GUID of the
class.
4. If your device has a CoInstaller, delete the registry entry in
HLKM\System\CurrentControlSet\Control\CoDeviceInstallers corresponding to
the device class you created for device. Note the key is named for the GUID
of the class.
5. Delete the registry entries in HLKM\System\CurrentControlSet\Enum
corresponding to the device you specified in the inf file. For PCI devices
this is under the PCI key, for legacy devices this is under the Root key.
Note: if you specify more than one device in the inf, you will have an entry
for each device type the system has seen. DELETING THIS KEY REQUIRES
CHANGING ITS SECURITY FIRST.
6. Delete the registry entry in
HLKM\System\CurrentControlSet\Services corresponding to the driver you
specified in the inf file. Note this is the standard cleanup one would have
done in the pre-PNP days.
7. Reboot the system, now that was easy and intuitive wasn't it.
--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply
"Harry Potter" <hpotter@azkabar.com> wrote in message
news:uc5KhtrxEHA.3908@TK2MSFTNGP12.phx.gbl...
> ok, I found there copy of my driver name under registery
> HKEY_LOCAL_MACHINE\System\ControlSet001\Enum\Root\MYDriver there is 001,
> 002,003,004,005 sub keys and set of values in each the same exist on
> HKEY_LOCAL_MACHINE\System\ControlSet002\Enum\Root\MYDriver
> HKEY_LOCAL_MACHINE\System\ControlSet\Enum\Root\MYDriver
>
> when I try to delete it won't let me, I tried to delete also at
safemode...
> Any idea, anyone?
>
> "Dan" <dmbren@verizon.net> wrote in message
> news:neckd.54289$fF6.23364566@news4.srv.hcvlny.cv.net...
> > Actually, I didn't answer your question. After deleting the driver and
> > rebooting, uninstall the ethernet adapter, then re-install it. That will
> > remove *most* of those annoying miniport entries.
> >
> > Harry Potter wrote:
> > > I have a buggy IM installed on my machine (obviously mine)... it seems
> that
> > > it is partially installed and now no matter how many times I say no to
> > > digital signature it still try to install it.... anyhow.... how can I
> remove
> > > it from my registry... it seems that it tries to install four miniport
> IM
> > > filters ( I know why)... when I go through my
computer->hardware->device
> > > manager... I see that there are 4 miniport driver installed under my
> network
> > > with yellow sign beside it... if I try uninstall it from there I get
the
> > > error that it may require reboot before uninstall but reboot doesn't
> help...
> > >
> > > so again, how and where in registry/directories should I do the
> cleanup... &
> > > is there anyway to test the driver before installing it, I test by
> > > installation...
> > > I've already located some of the IM under a directory in
> > > HKEY_LOCAL_MACHINE\System\currentControlSet\Services but not so sure
if
> I
> > > can delete them... Last ime I did I ended up with formatting my hard &
> > > hart:-)
> > >
> > > thank you for your feedbacks.
> > >
> > >
> >
>
>