Well, I think it's game over, and I should reinstall, and on a new drive. I ran the fixlist, and rebooted. I installed the available updates. 8 of 11 supposedly installed successfully, but there was no restart request. I couldn't run sfc until I rebooted. After the reboot, I'm getting a 0x6b BSOD. I've tried Startup Repair. It says it fixes something and to restart, but I'm back to the BSOD. Even if I can get back into Windows, it seems like there may be too many problems for this OS install to work through.
[SOLVED] 7x64 failed updates
- Thread starter codypeak
- Start date
Try to backup your important data. If this fails due to the BSOD, restore the COMPONENTS hive with the backup made in message #103 and try to backup your important data again.
In case the COMPONENTS hive has been restored, we can attempt to do a new repair if you like.
In case the COMPONENTS hive has been restored, we can attempt to do a new repair if you like.
Startup Repair failed to effect any changes, twice. System Restore from RE both reported as failed in RE, and reported as successful once it booted back into Windows. This is consistent with the messaging in the KB article here https://support.microsoft.com/en-us...when-you-try-to-restore-a-windows-7-based-com .
So, we are back in Windows now, I just don't know if any repair attempts will succeed. I don't mind trying though.
So, we are back in Windows now, I just don't know if any repair attempts will succeed. I don't mind trying though.
Correct
I did not. After the System Restore, I looked at the suggested troubleshooting/repair steps in the linked article for that error code, but I didn't go through with those procedures.
I have run SFC since then, though.
Uploaded
WeTransfer
WeTransfer
Step 1:
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
1. Download the file fixlist.txt and save it to your desktop.
2. Right-click on FRST64.exe and select "Run as administrator".
3. Press the Fix button.
4. The tool will now process fixlist.txt.
5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
7. Post the logfile Fixlog.txt as attachment in your next reply.
Step 2:
Check Windows Update again and report the result.
If it fails, run sfc /scannow again and attach the zipped cbs.log to your next reply.
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
1. Download the file fixlist.txt and save it to your desktop.
2. Right-click on FRST64.exe and select "Run as administrator".
3. Press the Fix button.
4. The tool will now process fixlist.txt.
5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
7. Post the logfile Fixlog.txt as attachment in your next reply.
Step 2:
Check Windows Update again and report the result.
If it fails, run sfc /scannow again and attach the zipped cbs.log to your next reply.
That didn't go too well, I'm afraid. During the reboot after 8 of 12 available updates supposedly installed successfully, another BSOD, same STOP code. I tried replacing the \components file from RE, but Windows didn't like that too much at first. Another 0x6B BSOD. This time I booted back into RE and tried a Repair, using the offered System Restore. That seems to have worked, but I have no idea what state this OS is in now, partly because that initial Repair offer of using System Restore doesn't say which one it uses. I will presume the latest.
If troubleshooting this is still interesting for you, I'm more than willing to continue. But I won't mind moving on either.
If troubleshooting this is still interesting for you, I'm more than willing to continue. But I won't mind moving on either.
Uploaded here:
WeTransfer
WeTransfer
This goes beyond my knowledge. Select "repair your computer" which hopefully launches Windows. Then backup all important data and perform a repair install.
Another option is to create a new thread in the forum section https://www.sysnative.com/forums/bsod-crashes-kernel-debugging/
Please note that there are still registry corruptions that need to be fixed.
Another option is to create a new thread in the forum section https://www.sysnative.com/forums/bsod-crashes-kernel-debugging/
Please note that there are still registry corruptions that need to be fixed.
Has Sysnative Forums helped you? Please consider donating to help us support the site!