Re: how to remove from registery

From: Harry Potter (hpotter_at_azkabar.com)
Date: 11/10/04 

Date: Tue, 9 Nov 2004 19:21:09 -0800

hummm... what do you mean, I did say thank you 2wice... when I said "simple"
I meant it with a quote in an opposite way not the real simple way.... I did
say it's because you went through the pain yourself... didn't I.... I even
said that I need to know how I should change the security of ENUM and
Microsoft haven't even made that easy
So I guess you got me completely wrong here... I'm sorry... didn't mean
that:-(
so indeed it was extremely complete and useful.... and THANK YOU.
So I would appreciate if you can also tell me how to change the security...
I'm still in the process of pulling my teeth out with the registry clean up.

"Dan" <dmbren@verizon.net> wrote in message
news:wvfkd.55751$fF6.23985000@news4.srv.hcvlny.cv.net...
> 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: Group Policy Deletion
    ... Removing the .inf file won't remove the entry because the entry itself is ... stored in a security settings file in SYSVOL. ... policy setting and let that propagate. ...
    (microsoft.public.win2000.group_policy)
  • Help with .inf security templates
    ... security templates .INF file applied to it. ... am unable change Local Security Ploicies. ...
    (microsoft.public.win2000.security)
  • Re: Corrupted security zones
    ... | I have a problem that occurred last week; I cannot open Access daabases, ... | get an error message saying Internet Explorer security Zone manager is ... You can't just state "...3 different spyware scanners find nothing, ... Right-Click on the INF file and choose "Install". ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Rights to System Services
    ... a new security template from your settings. ... templates and then save a new *.inf file after you configure the service. ... > not on the server that I'm running the GPO Editor that I have to go to a ... > Active Directory Users and Computers (so I can access the GPO Editor) and ...
    (microsoft.public.win2000.group_policy)