[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1133
  • Last Modified:

SteadyState hangs upon autoupdate

Testing Steadystate prior to deploying it.
Did a fresh install of Windows XP on Thursday and installed Steadystate to return the system upon reboot and told steadystate  to automatically update windows. Worked perfectly on Thursday. Late Friday afternoon I noticed that the PC was installing windows updates and that steadystate had rebooted. All weekend long the computer is stuck at a screen saying " The system is currently being updated and will reboot when completed" with no HD activity
Thinking the system hung, I hard booted the PC... same message again with no HD activity.
All the user accounts are disabled until the updates are complete so I can't log in

Anyone else run into this? It's almost as if the autoupdate is looking for user input to continue but of course no one can login as the accounts are disabled. Strange indeed
0
huntleyj
Asked:
huntleyj
  • 3
  • 2
1 Solution
 
nobusCommented:
try a system restore to a prior date :
windows could not start because the following file is missing or corrupt:  \WINDOWS\SYSTEM32\CONFIG\SYSTEM
http://support.microsoft.com/kb/307545
----------------------------------------------------------------------------------------------
An easier way is to boot from a Bart PE CD (or UBCD4Win CD) and use the file manager for manipulating files. Here  the procedure :
1. rename c:\windows\system32\config\SYSTEM to c:\windows\system32\config\SYSTEM.bak
2. Navigate to the System Volume Information folder.
it contains some restore {GUID} folders such as "_restore{87BD3667-3246-476B-923F-F86E30B3E7F8}".
The restore points are in  folders starting with "RPx under this folder.
3. In such a folder, locate a Snapshot subfolder. This is an example of a folder path to the Snapshot folder:  C:\System Volume Information\_restore{D86480E3-73EF-47BC-A0EB-A81BE6EE3ED8}\RP1\Snapshot
4. From the Snapshot folder, copy the following file to the c:\windows\system32\config folder
 _REGISTRY_MACHINE_SYSTEM
5. Rename _REGISTRY_MACHINE_SYSTEM to SYSTEM
6. Exit Bart PE, reboot and test

Use a fairly recent restore point from at least a day or two prior to problem occurring .

** you can add the other hives also with this procedure

http://www.nu2.nu/pebuilder/       BARTPE
http://www.ubcd4win.com/            UBCD4WIN
0
 
huntleyjAuthor Commented:
Ended up booting to last known good and manually installing the windows updates
0
 
nobusCommented:
excuse me, my answer DOES WORK
you probably never tried it !
0
 
huntleyjAuthor Commented:
From the link you provided-
Warning Do not use the procedure that is described in this article if your computer has an OEM-installed operating system. The system hive on OEM installations creates passwords and user accounts that did not exist previously. If you use the procedure that is described in this article, you may not be able to log back into the recovery console to restore the original registry hives.
It is a OEM installed OS
Also system restore is turned off on all my systems. So the SVI folder is useless in this case.
Don't take it personal dude. Your fix just didnt work for me although it may for the next guy.
0
 
nobusCommented:
>>  Also system restore is turned off on all my systems.   <<  then you should tell me, dude ! i can't know without info
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now