Re: Trying to remove corrupt registry key



On Tue, 8 Nov 2005 09:14:36 -0000, "Jody Flett" <nwes@xxxxxxxxxxxxxxxxxxxxxxxx> wrote:

>I have a registry key on my Windows 2000 Server that appears to be corrupted
>and cannot be removed. It appears as greyed out when looking through
>regedt32 and I cannot modify the permissions to the key or remove it or
>modify it. I also cannot delete it if I delete the parent key.
>
>I have tried starting regedt32 in the system context by using the at command
>and this still does not allow me to do anything with the key.
>
>I need to get rid of this registry key, does anyone have any suggestions on
>how to do this?
>
>Thanks
>
>Jody
>
Please specify the full key.

Jerold Schulman
Windows Server MVP
JSI, Inc.
http://www.jsiinc.com
http://www.jsifaq.com
.



Relevant Pages

  • Re: Secondary DNS and PIX
    ... in SBS SP1 you can substitute Windows Server SP2 and Exchange SP2 for the earlier versions, you do not need to back out of current levels. ... Change the value of the DisableTaskOffload registry key to ...
    (microsoft.public.windows.server.sbs)
  • Re: Secondary DNS and PIX
    ... WINDOWS SERVER 2003 FOR SMALL BUSINESS SERVER, ... Windows SBS 2003 SP1 is available. ... Change the value of the DisableTaskOffload registry key to ...
    (microsoft.public.windows.server.sbs)
  • Re: SMTP authentication for BT Yahoo and OE 6
    ... I follow the backup plan (I have Windows XP) I get to the directory: ... I select the registry key, ... > Outlook Express Does Not Save the Mail Server Logon Password ...
    (microsoft.public.windows.inetexplorer.ie6_outlookexpress)
  • Cant Access Registry
    ... I have designed a software audit tool which loops through ... registry key but the problem is that on every pc but the ... Windows 2000 to Windows 2003 Server. ...
    (microsoft.public.vb.general.discussion)
  • RE: Reserved Ports
    ... installation that breaks the Cluster Service in Windows Server 2003. ... If you need Lotus Domino Server to co-exist with Cluster Services, ... The workaround is to delete the following registry key: ... Windows 2000 MCSE + MCDBA ...
    (microsoft.public.windows.server.clustering)