Re: W2K continually reboots (Just before log in) After updates?

I don't think that (one of) the user profiles is causing this, you should load the System Hive and change the Auto Reboot behaviour and see if you can get an actual bugcheck error message/code to work with. The hive will be in the %systemroot%\system32\config folder. The hive you want to load is the SYSTEM hive (without an extension).

Change the value data in the AutoReboot value to 0 (zero), instead of
1, in the following key:

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CrashControl

This disables the Automatically Reboot option. After you follow these steps, you may be able to gather information from the STOP error message and resolve the problem that prevents the computer from starting.

*ControlSetNNN note*

You will notice that on a dormant NT system the registry has no
CurrentControlSet key, it only has ControlSetnnn keys (ControlSet001,
ControlSet002...) The CurrentControlSet key is created from one of the
numbered keys when the computer reboots. To determine which Control Set
will load when computer boots look at the
HKEY_LOCAL_MACHINE\SYSTEM\Select key. The numbers there indicate which
Control Set will be loaded depending on which boot option is chosen.
Edit the AutoReboot value in the appropriate Control Set.

John

Wideawake wrote:

OK - so I managed to get Bart PE working on the W2k machine by using another OEM (I had forgotten about an old IBM laptop) for the Bart PE Build.

When I try to enter the registry editor I get the following error:-

The remote user profile located c:\documents and settings\administrator.pc46\ntuser.dat could not be loaded

Does this imply this is corrupt?

I now intend to follow your suggestion of mounting on another PC and load the system hive - but feel I may encounter a similar problem?


"John John" wrote:


I beleive that the IASTOR is a mass storage/RAID device driver (or a SATA driver). You can't do registry work from the Recovery Console or from DOS. You could do it by connecting to the machine over the network or by mounting the disk in another Windows 2000/XP machine and using the registry editor's "Load Hive" feature to load the System Hive of the broken installation. If you do it with a Windows 2000 machine you have to use Regedt32 to do it.

John

Wideawake wrote:


Managed to uninstall the last hotfix - using your suggestions, appears to run the batch fine.

However does not solve the problem - machine still reboots continually (incidently the update was KB931768)

Could residual information be retained in registry from this update? causing the problem?

I followed your suggestion for Barts PE (after locating the registry editor plugin) - interesting tool, however, I think I have a problem with this as well!! I believe you can only build from a copy of XP :-

"Why can't Windows 2000/NT4 be used to build BartPE? Is there a reason for this?

Yes, that kernel does not support the "/minint" switch and therefore cannot boot from read only media... Also the layout.inf does not contain required information"

I do have a versions of XP - but they are all Dell OEM (Pre-installed), after the Barts PE disk is created, (which appears to be succesfull), if I use on the W2k machine (Non Dell) I get an error relating to IASTOR.sys which appears to be a dell driver.

Any other way of using a registry editor from recover console or DOS?

Thanks

"John John" wrote:



You can use a Bart's PE disk with a registry editor plugin to change the auto reboot behaviour.

To uninstall hotfixes from the Recovery Console navigate to the hotfix's spuninst directory and use the BATCH command to process the uninstall routine. Example:

cd %systemroot%\$NtUninstallKBnnnnnn$\spuninst

(or simply: cd $NtUninstallKBnnnnnn$\spuninst )

then issue:

batch spuninst.txt

If the batch command fails try:

batch spuninst.bat

John

Wideawake wrote:



I have three machines experiencing the same problem - not sure if related to recent windows updates.

These machines reboot just prior to windows log in.
They cycle endlessly - rebooting.

I think their "system failures" settings are set to reboot on system crash - so I am not sure if a BSOD is displayed or not. That may give me a clue to reason for crash.

My first step was to try to amend the "system failure" settings - but as mentioned I can not boot into safe mode to amend , is there a way to amend the system failure settings via recovery console?

Or does anyone have any other solutions?

My next step - would be to remove any recently applied updates, again via recovery console? Is this possible? And would the updates be easily identified? (As I do not have a list of all updates that were automatically applied prior to the problem)

Thanks - sorry for multiple questions in one post!! (This is my first post)





.

Relevant Pages

  • Re: W2K continually reboots (Just before log in) After updates?
    ... You could do it by connecting to the machine over the network or by mounting the disk in another Windows 2000/XP machine and using the registry editor's "Load Hive" feature to load the System Hive of the broken installation. ... To uninstall hotfixes from the Recovery Console navigate to the hotfix's spuninst directory and use the BATCH command to process the uninstall routine. ... These machines reboot just prior to windows log in. ... My next step - would be to remove any recently applied updates, ...
    (microsoft.public.win2000.general)
  • Re: Emegrncy help needed please
    ... Windows said it had downloaded an update and will restart my ... these messages until the process finishes or letting it reboot and ... again afterwards (or have the hassle of managing updates manually) ... Unfortunately - I believe the registry entries I can give you only work ...
    (microsoft.public.windowsxp.general)
  • Re: New Blaster Style Problem
    ... The only thing I clicked was the blue link at the bottom ... updates should give some protection or we will have to ... >> did not completely load. ... >> with F. I did and was told it would happen on reboot. ...
    (microsoft.public.security)
  • RE: Mysterious reboot
    ... hardware in a very long time. ... filesystems weren't unmounted correctly upon reboot, ... No crashes. ... CPU load was over 8 at some points. ...
    (freebsd-questions)
  • Re: The GPL 3.0 fiasco will make OpenSolaris #1
    ... Paul Floyd wrote: ... >> config, or admin skills. ... I have a LAMP server that sat at a constant load of>10 for the better ... one reboot, and it's performance was little affected by the load. ...
    (comp.unix.solaris)