Windows Server 2008 R2 Standard - Nothing Launching after update
- Thread starter Joshza
- Start date
zcomputerwiz
Windows Update Expert
Sorry about that. It's a built in device that would allow remote control of the system before Windows boots.
Not all servers have them, and in those that do it may or may not be enabled, licensed, or configured.
Not all servers have them, and in those that do it may or may not be enabled, licensed, or configured.
In a nutshell, I'm not sure. I can get to the physical machine, if needs be as it is around 200m from my house and involves a 5 minute walk in the dark with a torch - not very high tech but entirely plausible.
So far I've only ever connected using Remote Connection when not accessing the machine directly.
So far I've only ever connected using Remote Connection when not accessing the machine directly.
zcomputerwiz
Windows Update Expert
OK, good to know :)
If you wouldn't mind, schedule a disk check for the next reboot and physically watch the machine to verify that it does indeed run on the next reboot.
If you wouldn't mind, schedule a disk check for the next reboot and physically watch the machine to verify that it does indeed run on the next reboot.
zcomputerwiz
Windows Update Expert
Have you ever booted the Windows Recovery Environment before?
Hi
I've tried windows recovery.
The Windows Memory Diagnostic, Standard (runs for about 20 minutes) and extended (about 5 hours) shows no problems though after reboot doesn't show a log as it says it will do - though no normal server dialogues seem to work.
Also cannot restore to an earlier image etc as they don't seem to exist.
Thanks
I've tried windows recovery.
The Windows Memory Diagnostic, Standard (runs for about 20 minutes) and extended (about 5 hours) shows no problems though after reboot doesn't show a log as it says it will do - though no normal server dialogues seem to work.
Also cannot restore to an earlier image etc as they don't seem to exist.
Thanks
zcomputerwiz
Windows Update Expert
From an elevated command prompt, try running chkdsk without any parameters (read only mode).
chkdsk
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
chkdsk
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
- Click on the Start
button and in the search box, type Command Prompt
- When you see Command Prompt on the list, right-click on it and select Run as administrator
- When command prompt opens, copy and paste the following command into it, then press enter
chkdsk
- Right-click on the Command Prompt window and click Select All, this will invert all of the colours by selecting the text, now press enter. All of this text is now copied.
- Paste (Ctrl+V) it into your next post please.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\administrator.ROCKSTOCK> chkdsk
The type of the file system is NTFS.
WARNING! F parameter not specified.
Running CHKDSK in read-only mode.
CHKDSK is verifying files (stage 1 of 3)...
198400 file records processed.
File verification completed.
703 large file records processed.
0 bad file records processed.
0 EA records processed.
159 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
262526 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 3)...
198400 file SDs/SIDs processed.
Security descriptor verification completed.
32064 data files processed.
CHKDSK is verifying Usn Journal...
537130520 USN bytes processed.
Usn Journal verification completed.
Windows has checked the file system and found no problems.
314468351 KB total disk space.
44809828 KB in 152715 files.
103804 KB in 32065 indexes.
0 KB in bad sectors.
802643 KB in use by the system.
65536 KB occupied by the log file.
268752076 KB available on disk.
4096 bytes in each allocation unit.
78617087 total allocation units on disk.
67188019 allocation units available on disk.
C:\Users\administrator.ROCKSTOCK>
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\administrator.ROCKSTOCK> chkdsk
The type of the file system is NTFS.
WARNING! F parameter not specified.
Running CHKDSK in read-only mode.
CHKDSK is verifying files (stage 1 of 3)...
198400 file records processed.
File verification completed.
703 large file records processed.
0 bad file records processed.
0 EA records processed.
159 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
262526 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 3)...
198400 file SDs/SIDs processed.
Security descriptor verification completed.
32064 data files processed.
CHKDSK is verifying Usn Journal...
537130520 USN bytes processed.
Usn Journal verification completed.
Windows has checked the file system and found no problems.
314468351 KB total disk space.
44809828 KB in 152715 files.
103804 KB in 32065 indexes.
0 KB in bad sectors.
802643 KB in use by the system.
65536 KB occupied by the log file.
268752076 KB available on disk.
4096 bytes in each allocation unit.
78617087 total allocation units on disk.
67188019 allocation units available on disk.
C:\Users\administrator.ROCKSTOCK>
zcomputerwiz
Windows Update Expert
The process I'd like to try is backing up the Software hive and then replacing the current copy from the Windows Recovery Environment.
How familiar are you with using the command line? We would be using it in the recovery environment to find the Windows drive and then rename the current software hive.
How familiar are you with using the command line? We would be using it in the recovery environment to find the Windows drive and then rename the current software hive.
zcomputerwiz
Windows Update Expert
OK, first run REGBACK and export the software hive as before:
Export SOFTWARE Hive
Please download RegBak (by AceLogix Software) from the link below and save it to your Desktop.
Next, reboot into the Windows Recovery Environment and choose View Advanced Options for System Recovery and Support, then Command Prompt.
Your Windows drive letter may be different in the recovery environment.
In the command prompt window, type diskpart and then press enter.
Next, type list vol and then press enter.
This should list all volumes on the computer. You should be able to identify your Windows drive, it is usually the largest and shows boot under info.
Make note of the drive letters, then type exit and then press enter.
Type the drive letter that may be the Windows drive (for example, C:) and then press enter.
Type dir windows\system32\config and then press enter.
If the output is a list that includes COMPONENTS, SOFTWARE, SOFTWARE.NEW, SYSTEM, etc. this is the correct drive.
Type cd windows\system32\config and then press enter.
Type ren SOFTWARE SOFTWARE.OLD and then press enter.
Type ren SOFTWARE.NEW SOFTWARE and then press enter.
Type EXIT and then press enter.
Exit the recovery environment. This should restart the machine.
If you encounter a problem let me know right away.
Export SOFTWARE Hive
Please download RegBak (by AceLogix Software) from the link below and save it to your Desktop.
- Right-click on regbak.zip then select Extract all... and extract the files to your Desktop
For 32-bit (x86) editions of Windows, double-click on regbak.exe
For 64-bit (x64) editions of Windows, double-click on regbak64.exe
- Without changing any options, click Next. RegBak will now backup all of your registry hives.
- Navigate to C:\Windows\RegBak\{Date}\ and copy the SOFTWARE file (it has no extension) to your Desktop
- Rename the SOFTWARE file to SOFTWARE.NEW
- Copy the SOFTWARE.NEW file to C:\Windows\System32\Config\
Next, reboot into the Windows Recovery Environment and choose View Advanced Options for System Recovery and Support, then Command Prompt.
Your Windows drive letter may be different in the recovery environment.
In the command prompt window, type diskpart and then press enter.
Next, type list vol and then press enter.
This should list all volumes on the computer. You should be able to identify your Windows drive, it is usually the largest and shows boot under info.
Make note of the drive letters, then type exit and then press enter.
Type the drive letter that may be the Windows drive (for example, C:) and then press enter.
Type dir windows\system32\config and then press enter.
If the output is a list that includes COMPONENTS, SOFTWARE, SOFTWARE.NEW, SYSTEM, etc. this is the correct drive.
Type cd windows\system32\config and then press enter.
Type ren SOFTWARE SOFTWARE.OLD and then press enter.
Type ren SOFTWARE.NEW SOFTWARE and then press enter.
Type EXIT and then press enter.
Exit the recovery environment. This should restart the machine.
If you encounter a problem let me know right away.
I have a Raid 5 setup so not sure if this is the issue with your instructions.
As per list vol c is the boot drive.
I created and placed the SOFTWARE.NEW file in config.
When I launch system recovery and go to the command prompt it opens on X:\Windows\System32. (Not C:)
If I CD to X:\Windows\System32\Config the folder does not show the file SOFTWARE.NEW - the files SOFTWARE and SOFTWARE.LOG do show. ( I went back and double checked on the server after a restart and the SOFTWARE.NEW folder is definitely there.
If I go to C:, it exists but calling dir returns: "Volume in drive C is Sytem Reserved" "Volume Serial Number is 7CFE-314E". I can only see C:\
Under X: I assumed maybe it is "hiding" non-standard files and tried ren SOFTWARE SOFTWARE.OLD anyway just in case, but it returns "The process cannot access the file because it is being used by another process."
Any ideas?
Thanks,
As per list vol c is the boot drive.
I created and placed the SOFTWARE.NEW file in config.
When I launch system recovery and go to the command prompt it opens on X:\Windows\System32. (Not C:)
If I CD to X:\Windows\System32\Config the folder does not show the file SOFTWARE.NEW - the files SOFTWARE and SOFTWARE.LOG do show. ( I went back and double checked on the server after a restart and the SOFTWARE.NEW folder is definitely there.
If I go to C:, it exists but calling dir returns: "Volume in drive C is Sytem Reserved" "Volume Serial Number is 7CFE-314E". I can only see C:\
Under X: I assumed maybe it is "hiding" non-standard files and tried ren SOFTWARE SOFTWARE.OLD anyway just in case, but it returns "The process cannot access the file because it is being used by another process."
Any ideas?
Thanks,
zcomputerwiz
Windows Update Expert
X: is a ramdrive for the Windows Recovery Environment.
The volume name "System Reserved" indicates that C: is most likely the 100-300mb System partition.
Which volume was the largest? Run diskmgmt.msc in Windows and see what your C: drive shows for size, this should provide direction for which volume to choose when in the recovery enviroment :)
The volume name "System Reserved" indicates that C: is most likely the 100-300mb System partition.
Which volume was the largest? Run diskmgmt.msc in Windows and see what your C: drive shows for size, this should provide direction for which volume to choose when in the recovery enviroment :)
I'm more confused than before now. C: drive always showed on the file explorer as did the D: drive for our data. The C drive has the windows system on it. If I look at disk Management I now see an E: and F: drive which I don't recall from before. If I check in Windows Explorer it also shows those two drives - E: and F: (in addition to C: and D:). If you click on either E or F it wants to know if I must format them (I said no and then it gives an error)?
Looking at Disk Management, E and F both sit in Disk0 which appears to mirror the structure of Disk1 (except for the unallocated portion?). I've attached screenshots in the hope of explaining my ramblings.
A last aside which may explain the weird structure. Previously I mentioned the system is a RAID5 system. A month or two ago one drive failed and I replaced it with a new one which it then rebuilt and said all is fine, maybe it was not? I did the rebuild using the Intel Rapid Storage application which always monitored the drives. It doesn't anymore as it also refuses to launch following the failed windows update.
Looking at Disk Management, E and F both sit in Disk0 which appears to mirror the structure of Disk1 (except for the unallocated portion?). I've attached screenshots in the hope of explaining my ramblings.
A last aside which may explain the weird structure. Previously I mentioned the system is a RAID5 system. A month or two ago one drive failed and I replaced it with a new one which it then rebuilt and said all is fine, maybe it was not? I did the rebuild using the Intel Rapid Storage application which always monitored the drives. It doesn't anymore as it also refuses to launch following the failed windows update.
Attachments
zcomputerwiz
Windows Update Expert
Be sure you have a good backup of any data on that system. My suspicion is that one drive that was previously part of the array is showing up as a non-raid disk. Disk failures in a RAID 5 array can cause data loss and recovery (if possible) is usually expensive and time consuming.
Once you are in the recovery environment, follow the same instructions as before.
After running the list vol command, take note of the volumes that are 299GB in size - like your C: drive when in Windows. There may be more than one (e.g. D:, F:).
Change to that drive ( type D: and press enter for example) and then change directories to \windows\system32\config\ (cd windows\system32\config) then check if SOFTWARE.new is present (dir software.new).
If it is, continue with the renaming of the old software hive and the new software hive as in the previous instructions.
If you get an error message for either command, try the other drive.
Let me know how that goes or if you have questions.
Once you are in the recovery environment, follow the same instructions as before.
After running the list vol command, take note of the volumes that are 299GB in size - like your C: drive when in Windows. There may be more than one (e.g. D:, F:).
Change to that drive ( type D: and press enter for example) and then change directories to \windows\system32\config\ (cd windows\system32\config) then check if SOFTWARE.new is present (dir software.new).
If it is, continue with the renaming of the old software hive and the new software hive as in the previous instructions.
If you get an error message for either command, try the other drive.
Let me know how that goes or if you have questions.
zcomputerwiz
Windows Update Expert
OK, turns out there is a simpler way to do this using regbak.
Make sure that you have your known good backup before continuing.
SOFTWARE Hive Replacement with RegBak
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
Make sure that you have your known good backup before continuing.
SOFTWARE Hive Replacement with RegBak
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
- Close all open programs and save all your work. You will need to reboot the machine during this process.
- Double click on regbak64.exe to launch RegBak. Press Yes on the UAC prompt that will appear
- Click New Backup to open the new backup window. Leave the backup path as the default.
- Click Click here to view details and uncheck all options except for C:\Windows\System32\config\SOFTWARE. Press OK
- Click Start to create a backup.
- Once the backup is done, click Close to return to the main RegBak screen. You have now backed up the registry. Close RegBak
- Open RegBak again. Highlight the backup in the list (it should be the only one), and press Restore. Click Start. RegBak will reboot your computer to complete the restore process.