Phil,
After quite a while at beating my head against the nearest fixed object, I
was able to edit the registry.
I had a parallel install of 2K in a WIN2K dir, opened regedt32 highlighted
HKLM & loaded the various registry hive files in the c:\WINNT\System32\config
dir until I found the ...\Winlogon\Userinit key... which takes some looking
since it's not the full path as in the article. I noticed that the Reg_SZ
value was "C:\Windows\System32\userinit.exe" instead of "C:\WINNT\..." which
is where the system was foobaring. I corrected that key and re-booted to the
regular OS and it logged back into the system fine.
After I logged in locally, I verified the rest of the registry for other
references to the Windows directory instead of WINNT, and found 4 other
references that had been changed during the Windows Update. I changed those
as well, re-booted to the domain, and all was well with the world.
The issue was not quite what the article said, and the editing the
registry via the network only works if: a) the system actually connects to
the network at some point (mine never did) and b) the system is set up to
allow remote access to the registry and other system files (which this
workstation is not.)
Some other DOS-based NTFS registry editors (wich shall not be mentioned
due to their 3rd-party, non-MS nature) can also do the same thing without
having a parallel install and nerves of steel in modifying registry hives for
secondary installs.
Thanks again for the pointer since it did get me to the right spot, but
it's not your fault that their suggestions on how to get to the registry when
you can't log into the system are bogus. I didn't want to backup the config
dir, wipe it out, then copy the contents of the c:\WINNT\repair dir to the
config dir since that would wipe out all of my SW registry hooks.
Todd
--
Warning Chef Not found: [B]ork [B]ork [B]ork ?
"Phil" wrote:
> I experienced the exact same issue last night - here is a link to the fix:
>
> Unable to Log on if the Boot Partition Drive Letter Has Changed
> http://support.microsoft.com/?id=249321
>
>
> "Random Confusion" wrote:
>
> > Last night I installed the 8 latest updates for Windows 2000 on my unit:
> >
> > Security Update for Windows 2000 (KB896423)
> > Security Update for Windows 2000 (KB899588)
> > Windows Malicious Software Removal Tool - August 2005 (KB890830)
> > Cumulative Security Update for Internet Explorer 6 Service Pack 1 (KB896727)
> > Security Update for Windows 2000 (KB893756)
> > Security Update for Windows 2000 (KB899587)
> > Update Rollup 1 for Windows 2000 Service Pack 4 (KB891861)
> > Security Update for Windows 2000 (KB901214)
> >
> > The unit shut down and re-booted normally, but when I attempted to log into
> > the system, it comes back to the CTRL+ALT+DEL screen pre-login (which was set
> > to NOT show for users logging into the system originally.)
> >
> > No matter what user account for the domain (domain admin, admin, user, power
> > user, guest, etc) or on the local box (admin only, no local user accounts,
> > but they were attempted anyway) all return to the same login screen again.
> > Safe mode returns the same results for logging in as administrator on the
> > local box.
> >
> > A parallel install of W2K that was already residing on the box for testing
> > purposes almost a year ago but never updated, logs in fine locally. This is
> > therefore not hardware related and isolated to the active W2K install and a
> > result of the latest windows update (and the insistant install/"update" of
> > the windows update software.)
> >
> > Any help with how to correct this without re-imaging the system will be
> > greatly appreciated, and I have halted the updating of any other units in the
> > domain until this is resolved (this was the first unit on the domain updated.)
> >
> > Todd
> >
> > --
> > Warning Chef Not found: [B]ork [B]ork [B]ork ?
Similar Threads
Linear Mode
