Can not delete registry keys

  • Thread starter Thread starter John W Mitchell
  • Start date Start date
J

John W Mitchell

I am trying to remove any and all referrences to the ESS
Allegro ES1989S audio card from my registry. There are
some keys that I can not delete. Can some one shed some
light on how I may delete these keys. It gives the message
"can not delete 'key name' error deleting key".
Thanks
 
John W Mitchell wrote in
I am trying to remove any and all referrences to the ESS
Allegro ES1989S audio card from my registry. There are
some keys that I can not delete. Can some one shed some
light on how I may delete these keys. It gives the message
"can not delete 'key name' error deleting key".
Thanks
Click to expand...

OS?
Try using regedt32.exe and the Security menu to grant sufficient
permissions to delete it.

Otherwise say more. Fully qualified registry path for example.
Consult the vendor for specific instructions?
 
John W Mitchell wrote in
I am trying to remove any and all referrences to the ESS
Allegro ES1989S audio card from my registry. There are
some keys that I can not delete. Can some one shed some
light on how I may delete these keys. It gives the message
"can not delete 'key name' error deleting key".
Thanks
Click to expand...

OS?
Try using regedt32.exe and the Security menu to grant sufficient
permissions to delete it.

Otherwise say more. Fully qualified registry path for example.
Consult the vendor for specific instructions?
 
I've got the same problem.
HKLM\SYSTEM\CurrentControlSet\Service\ScanMail_Monitor\Perf
ormance

I've used REGEDIT32 on the bad key and get "unable to
display security information".

I tried to set it at the ScanMail_Monitor key, and told it
to propagate down, no luck. The message is "Registry
Editor could not set security in the key currently
selected, or some of its subkeys."

I also tried to rename the ScanMail_Monitor key. That also
fails.

Does anyone know of any Reg. repair/diagnostic tools?
Any other ideas (without restoring the whole server and/or
registry)?

Matt
 
I've got the same problem.
HKLM\SYSTEM\CurrentControlSet\Service\ScanMail_Monitor\Perf
ormance

I've used REGEDIT32 on the bad key and get "unable to
display security information".

I tried to set it at the ScanMail_Monitor key, and told it
to propagate down, no luck. The message is "Registry
Editor could not set security in the key currently
selected, or some of its subkeys."

I also tried to rename the ScanMail_Monitor key. That also
fails.

Does anyone know of any Reg. repair/diagnostic tools?
Any other ideas (without restoring the whole server and/or
registry)?

Matt
 
Matt Klett wrote in
I've got the same problem.
HKLM\SYSTEM\CurrentControlSet\Service\ScanMail_Monitor\Perf
ormance

I've used REGEDIT32 on the bad key and get "unable to
display security information".
Click to expand...

For that section of the registry either you are: not Permiited and/or
the Owner of the key; the key is being held open by a process (is
there a "Scanmail Service" running?); or there is registry corruption
(slim). I think that covers almost all cases.
I tried to set it at the ScanMail_Monitor key, and told it
to propagate down, no luck. The message is "Registry
Editor could not set security in the key currently
selected, or some of its subkeys."

I also tried to rename the ScanMail_Monitor key. That also
fails.
Click to expand...

Did you Take Ownership (from an administrator account) and propogate
first? Then alter the ACE and propogate. (possibly disabling
Inherit from above in the process). This only for a key with subkeys
you intend to delete.
 
Matt Klett wrote in
I've got the same problem.
HKLM\SYSTEM\CurrentControlSet\Service\ScanMail_Monitor\Perf
ormance

I've used REGEDIT32 on the bad key and get "unable to
display security information".
Click to expand...

For that section of the registry either you are: not Permiited and/or
the Owner of the key; the key is being held open by a process (is
there a "Scanmail Service" running?); or there is registry corruption
(slim). I think that covers almost all cases.
I tried to set it at the ScanMail_Monitor key, and told it
to propagate down, no luck. The message is "Registry
Editor could not set security in the key currently
selected, or some of its subkeys."

I also tried to rename the ScanMail_Monitor key. That also
fails.
Click to expand...

Did you Take Ownership (from an administrator account) and propogate
first? Then alter the ACE and propogate. (possibly disabling
Inherit from above in the process). This only for a key with subkeys
you intend to delete.
 
I think that covers almost all cases.

I've got another idea. I remember a software company publishing a source
(OSDN) that allowed a coder to create a key that in only accessible by a
special call to he registry, something to do with DBCS-SBCS misconversion.
Once the program created the key I was unable to delete it in ANY way, I had
to see how he did it and undo it with the same call.

Should it become corrupted in the same way, you can forget the key there.
Unless it is bothering you enough to search the web, apply coding knowledge
(if you have any, it's in Delphi) and try to unscrew it.

But I think you have to know HOW it was created.
 
I think that covers almost all cases.

I've got another idea. I remember a software company publishing a source
(OSDN) that allowed a coder to create a key that in only accessible by a
special call to he registry, something to do with DBCS-SBCS misconversion.
Once the program created the key I was unable to delete it in ANY way, I had
to see how he did it and undo it with the same call.

Should it become corrupted in the same way, you can forget the key there.
Unless it is bothering you enough to search the web, apply coding knowledge
(if you have any, it's in Delphi) and try to unscrew it.

But I think you have to know HOW it was created.
 
Not recommended, but you'll likely need to first take ownership of the key
with regedt32.exe
 
Not recommended, but you'll likely need to first take ownership of the key
with regedt32.exe
 
Ndi wrote in
I've got another idea. I remember a software company publishing
a source
(OSDN) that allowed a coder to create a key that in only
accessible by a special call to he registry, something to do with
DBCS-SBCS misconversion. Once the program created the key I was
unable to delete it in ANY way, I had to see how he did it and
undo it with the same call.

Should it become corrupted in the same way, you can forget the
key there.
Unless it is bothering you enough to search the web, apply coding
knowledge (if you have any, it's in Delphi) and try to unscrew it.

But I think you have to know HOW it was created.
Click to expand...

Interesting. Personally I think such a developer should be shot.
;-)

OTOH if it was done with a documented API call I guess it's "legal"
(but perhaps "immoral") <S>
 
Ndi wrote in
I've got another idea. I remember a software company publishing
a source
(OSDN) that allowed a coder to create a key that in only
accessible by a special call to he registry, something to do with
DBCS-SBCS misconversion. Once the program created the key I was
unable to delete it in ANY way, I had to see how he did it and
undo it with the same call.

Should it become corrupted in the same way, you can forget the
key there.
Unless it is bothering you enough to search the web, apply coding
knowledge (if you have any, it's in Delphi) and try to unscrew it.

But I think you have to know HOW it was created.
Click to expand...

Interesting. Personally I think such a developer should be shot.
;-)

OTOH if it was done with a documented API call I guess it's "legal"
(but perhaps "immoral") <S>
 
Back
Top