Archived from groups: microsoft.public.win2000.general,microsoft.public.win2000.registry,microsoft.public.win2000.setup (
More info?)
Dave,
Maybe double rebooting is not such a bad deal after all! As I got the
details of the registry mod from my predecessor, this problem has been going
on for quite some time so I do not have a whole lot of confidence in the
backup registry being any better. My main concern being driver
re-installation and downtime. Seems like in this situation leaving well
enough is the preferred course, but I am putting your notes into the system
log book for future reference.
Thanks for all the insight and details!
Don
"Dave Patrick" <mail@Nospam.DSPatrick.com> wrote in message
news:edIX2AuPFHA.3076@tk2msftngp13.phx.gbl...
> You might want to restore the system hive to a know good previous state.
>
> You can replace registry hives from within the recovery console.
>
> You can try using the most recent backup found in;
> %windir%\repair\regback
>
> or use the original-as-installed system hive from;
> %windir%\repair\system
> to
> %windir%\system32\config\system
> You'll need to reinstall the device drivers for any hardware added since
the
> original OS install.
>
> To start the Recovery Console, start the computer from the Windows 2000
> Setup CD or the Windows 2000 Setup floppy disks. If you do not have Setup
> floppy disks and your computer cannot start from the Windows 2000 Setup
CD,
> use another Windows 2000-based computer to create the Setup floppy disks.
> Press ENTER at the "Setup Notification" screen. Press R to repair a
Windows
> 2000 installation, and then press C to use the Recovery Console. The
> Recovery Console then prompts you for the administrator password. If you
do
> not have the correct password, Recovery Console does not allow access to
the
> computer. If an incorrect password is entered three times, the Recovery
> Console quits and restarts the computer. Note If the registry is corrupted
> or missing or no valid installations are found, the Recovery Console
starts
> in the root of the startup volume without requiring a password. You cannot
> access any folders, but you can carry out commands such as chkdsk,
fixboot,
> and fixmbr for limited disk repairs. Once the password has been validated,
> you have full access to the Recovery Console, but limited access to the
hard
> disk. You can only access the following folders on your computer: drive
> root, %systemroot% or %windir%
>
> You can also try an in-place upgrade.
>
> How to Perform an In-Place Upgrade of Windows 2000
>
http://support.microsoft.com/support/kb/articles/Q292/1/75.ASP
>
> What an In-Place Windows 2000 Upgrade Changes and What It Does Not Change
>
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q306952
>
> Be sure to apply these to your repair install before connecting to any
> network.
>
>
http://download.microsoft.com/download/E/6/A/E6A04295-D2A8-40D0-A0C5-241BFECD095E/W2KSP4_EN.EXE
>
http://www.microsoft.com/technet/security/bulletin/MS03-043.mspx
>
http://www.microsoft.com/technet/security/bulletin/MS03-049.mspx
>
> --
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
>
http://www.microsoft.com/protect
>
> "Don" wrote:
> |
> | Dave,
> |
> | Ouch!! And I am now officially way out of my knowledge comfort zone!
> |
> | I did some searches at MSDN on damaged subkeys and did not find anything
> | that was relevant.
> |
> | The obvious questions are:
> |
> | 1) Is this a problem? If so how big?
> |
> | 2) How do I go about repairing this?
> |
> | 3) Is it likely there are other damaged service subkeys? If so, what
is
> | the best course of action?
> |
> |
> | Any references you can point me to or good keywords for MSDN searches
will
> | be GREATLY appreciated!
> |
> | Thanks for all the help!!
> |
> | Don
>
>