Please help!!!I'm Desperate!!!

From: knsa (knsa73@hotmail.com)
Date: 07/21/02


From: "knsa" <knsa73@hotmail.com>
Date: Sun, 21 Jul 2002 09:15:18 -0700


There's ways of getting in, such as doing a second install
of Win2K to the same system so that you can access and
copy your data off. However, this approach doesn't really
let you use your machine again, until you resinstall your
apps. A technique that might work (provided your wife
didn't update the emergency repair info) would be to boot
the machine with your Win2K cd, choose the repair option
on the main screen, R again to access the repair process,
M to manually direct the repair and...dammit where's the
option to recover the SAM?! (Sorry I was doing this
proceedure on a Thinkpad here, just so that I could give
you accurate directions). Looks like you'd need access to
the Recovery Console in order to move the repair copy of
SAM from \system32\repair over to the system32\config
directory. This used to be an option on NT 4.0's
automated recovery options, but apparently not anymore.
Nonetheless, doing a scondary install of win2k (to a
different directory!) and then booting into that option
will allow you to specify a new admin password for that
installation, which will then allow you to copy the file
over to the correct location of your older one. Confusing
isn't it? But free.

Another option would be ERD commander (written by
Winternals.com). The boot CD will allow you to load the
security hive and reset the local administrator's
password, WITHOUT requiring you to provide the current
password in order to do it. Basically the app looks like
a buffed-up version of Microsoft's Recovery console
without the imposed limits on reading an NTFS-formatted
drive's directory structure, and allows files to be
written to removeable media without requiring a
permissionos through the implementation of the Security
Policy object. All you do is boot off the
CD...run "loadreg"...and then type
pass "administrator "password". All just as neat as you
could wish...except that the program costs $399! Kinda
sad when a company knows it's got you by the throat, isn't
it?



Relevant Pages

  • Re: Repeated Boot
    ... I didn't recommend the recovery console, I recommended you do a repair ... install, that doesn't require the recovery console, please follow the steps ... >> actual XP CD as opposed to a recovery CD, boot with the XP ...
    (microsoft.public.windowsxp.accessibility)
  • Re: No boot and no administrator password!
    ... At the Recovery Console, have you tried just leaving the password blank and ... > installations to repair. ... >>Try a Repair Install instead of Recovery Console. ... >>actual XP CD as opposed to a recovery CD, boot with the XP ...
    (microsoft.public.windowsxp.accessibility)
  • Re: REGISTRY_ERROR
    ... Rather than the Recovery Console, see if you can do a Repair Install as ... actual XP CD as opposed to a recovery CD, boot with the XP ...
    (microsoft.public.windowsxp.accessibility)
  • Re: Starting WinXP Pro & Taskbar Problems
    ... WinXP will be restored & hence you won't have to re-install them. ... install of XP, reinstall program, then restore data. ... Due to some reasons, Win2K Pro got corrupted ... Select 'r' at the first screen to start repair. ...
    (microsoft.public.windowsxp.general)
  • Re: Help! User Interface Failure!
    ... It's not possible to do a repair with the OEM Restore CDs. ... Even Recovery Console procedure might not help here ... You may need to perform a Repair install. ... When I right clicked on GinaDLL, ...
    (microsoft.public.windowsxp.general)