Re: how to remove from registery

From: Dan (dmbren_at_verizon.net)
Date: 11/10/04 

Date: Wed, 10 Nov 2004 03:00:44 GMT

Very complete and useful. Thanks.

Don Burn wrote:
> 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.
>
>

Relevant Pages

  • Re: i am trying to create a xp component for a driver
    ... A possible problem with the INF import was the need to parse special ... registry for the driver to work properly. ... driver is installed the inf file is no longer necessary. ...
    (microsoft.public.windowsxp.embedded)
  • Re: Reading writing INF files
    ... InstallHinfSection Executes a specified section in a specified INF ... an INF file or, if a key is specified, the first line that matches the key. ... SetupGetBinaryField Retrieves binary data from a field in a specified ... SetupInstallFileEx Installs a specified file into a specific target ...
    (microsoft.public.dotnet.framework)
  • Re: Bad INF, how to clean registry now?
    ... Windows 2k/XP/2k3 Filesystem and Driver Consulting ... Delete the files copied by the INF from the system. ... >> your device identifier will determine the OEM* name of your inf file. ... >> Don Burn (MVP, Windows DDK) ...
    (microsoft.public.development.device.drivers)
  • Re: Purging System of Driver Junk
    ... > Removing all traces of a driver from a system ... > When testing a device install developers want to cleanup the system ... Delete the files copied by the INF from the system. ... > your device identifier will determine the OEM* name of your inf file. ...
    (microsoft.public.development.device.drivers)
  • Re: how to remove from registery
    ... Delete the files copied by the INF from the system. ... > your device identifier will determine the OEM* name of your inf file. ... If your device has a unique class, delete the registry entry in ... if you specify more than one device in the inf, ...
    (microsoft.public.development.device.drivers)