[SOLVED] First Post - Windows 7 Update Failure

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 attachment 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.

Step 2:
Perform the instructions in message #108 again.
 

Attachments

Great. Restart the computer.
Run the command sfc /scannow in an elevated commandprompt and report the result.
If it fails, copy the file C:\Windows\Logs\CBS\cbs.log to your desktop.
Zip the copied file and attach the zipped cbs.log to your next reply.
 
The sfc scan ran to 100% but there was an error. I'm attaching the Command Prompt screen grab and the cbs log file. I'll wait until I hear back from you before restarting.
 

Attachments

  • SFC_Scan_ScreenGrab_01052024.jpg
    SFC_Scan_ScreenGrab_01052024.jpg
    62.1 KB · Views: 2
  • CBS.zip
    CBS.zip
    495.2 KB · Views: 1
A lot of system files are damaged. This is the first fix to replace them.

Step 1:
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.
  • Download the file SFCFix.zip and save it on your desktop.
  • Save any work you have open, and close all programs.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
    1p8eDnI.gif
  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Attach that file to your next reply.

Step 2:
Restart the computer.
Run the command sfc /scannow in an elevated commandprompt and report the result.
If it fails, copy the file C:\Windows\Logs\CBS\cbs.log to your desktop.
Zip the copied file and attach the zipped cbs.log to your next reply.
 
There is a new problem now. I'm typing this from my Win10 laptop. The Win7 office PC on the last restart finished with a dark screen with the mouse pointer in the center. The computer seems to be running fine but there is a video problem and no screen display. I can power it off with the OFF switch and power it back on. When powered on it will show the initial Windows screen and logo but then switches to the dark screen.

I can start it with a Windows 7 Professional installation CD and get to the Command Prompt if that helps. I've powered it off and on several times and aside from no video it seems to be running.
 
Pressing and holding the F8 key on power up does not go to safe mode. I have a Microsoft natural keyboard. Is there another way to power up in safe mode?
 
Also repeatedly pressing the F8 key does not work. Should I start up with the Windows installation CD and go to a command prompt and run a command like this "bcdedit /set {default} safeboot network"?
 
OK, I tried the command prompt safeboot network and it still has the same dark screen with the mouse pointer in the center. It does not appear I have a way to get into safe mode with video.
 
I'm thinking the only option left is to pull the video card and use the VGA connection on the mother board for video. I'm going to wait until I hear back from you first. Thank you.
 
OK, I did not wait. I did a system restore which seems to have worked. Screen Grab attached. I'm assuming you want me to follow the Post #165 instructions.
 

Attachments

  • SystemRestoreSG_01062024.jpg
    SystemRestoreSG_01062024.jpg
    23.6 KB · Views: 1
I'm going to wait since the SFCfix.zip link from Post #165 does not download the file. It just sends me to wetransfer.com. With all that's transpired I am going to wait for your reply before the next move. The computer seems to be up and running with the 1/5/2024 10:29:43 AM restore point. I believe this was just before the kb4048957 update ran successfully.
 
Great that Windows is running normally again. The date and time of the restore suggests were are back at post #142.
Check that KB4048957 is installed successful.
 
OK, I ran the Post #108 instructions again (KB4048957) and it installed successful. Can I mess anything up by running a fixlog we've already run or by running the SFCFix.zip in Post #165? It seems like I'm at Post #163 at this point. It was after I followed the Post #163 instructions that the next restart had the black screen.

So in-between Post #163 and post #165 the black screen happened so I was not able to do what you provided in Post #165.
 
Please do following only:

Run the command sfc /scannow in an elevated commandprompt and report the result.
If it fails, copy the file C:\Windows\Logs\CBS\cbs.log to your desktop.
Zip the copied file and attach the zipped cbs.log to your next reply.
 
CBS log is attached. It sounds like some system changes will take effect the next reboot. I'll wait to hear back from you before doing a restart.
 

Attachments

Allow the system to restart if the SFC /SCANNOW command requires that.
After the restart run the command sfc /scannow in an elevated commandprompt again.
If it fails, copy the file C:\Windows\Logs\CBS\cbs.log to your desktop.
Zip the copied file and attach the zipped cbs.log to your next reply.
 
OK, I've restarted and it's now sitting on the same black screen as the last time. I'm replying via the laptop. Last time I let it sit for about 2 hours and it still had the black screen so I powered off. I'm going to leave it alone the rest of the day and see what happens. I can hear the hard disk so it's doing something. Last time after two hours there was no hard disk activity.

Either we are repeating the exact same steps as before or the restart process takes hours. If it does not restart properly we'll need to try something different for the step in Post #163 and subsequent restart.
 
No problem. I wander why the black screens appears. We were repairing system files, no drivers.
Report the result.
 
You must log in or register to reply here.
Back
Top