MarMax Contributor Joined Dec 8, 2023 Posts 578 Location SoCal Jan 7, 2024 #181 The system has been running for three hours now and it's still on the black screen with the mouse cursor which is active. Minimal hard disk activity but the system is running and probably does not know there is a video driver problem. Should I proceed with the restore like last time or do you suggest something else?
The system has been running for three hours now and it's still on the black screen with the mouse cursor which is active. Minimal hard disk activity but the system is running and probably does not know there is a video driver problem. Should I proceed with the restore like last time or do you suggest something else?
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 13,709 Jan 7, 2024 #182 If you press the NumLock or CapsLock key, does the corresponding led on the keyboard lit or goes off ? Try pressing the ALT-F4 key to activate the Windows shutdown window, then press Enter to confirm. If this doesn't work try to restore the system as you did earlier.
If you press the NumLock or CapsLock key, does the corresponding led on the keyboard lit or goes off ? Try pressing the ALT-F4 key to activate the Windows shutdown window, then press Enter to confirm. If this doesn't work try to restore the system as you did earlier.
MarMax Contributor Joined Dec 8, 2023 Posts 578 Location SoCal Jan 7, 2024 #183 The NumLock and CapsLock key lights go on and off when pressed. I tried Alt-F4 and Enter and it did not shut down. I'll restore it back to where we were last time.
The NumLock and CapsLock key lights go on and off when pressed. I tried Alt-F4 and Enter and it did not shut down. I'll restore it back to where we were last time.
MarMax Contributor Joined Dec 8, 2023 Posts 578 Location SoCal Jan 7, 2024 #184 I've got a couple more restore points after the 1/5/2024 10:29:43 AM restore point. One is an Automatic Restore Point (Type - System) at 1/6/2024 12:19:05 PM and the most recent is a Windows Modules Installer (Type - Install) at 1/6/2024 4:18:44 PM. Should I use one of the more recent restore points?
I've got a couple more restore points after the 1/5/2024 10:29:43 AM restore point. One is an Automatic Restore Point (Type - System) at 1/6/2024 12:19:05 PM and the most recent is a Windows Modules Installer (Type - Install) at 1/6/2024 4:18:44 PM. Should I use one of the more recent restore points?
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 13,709 Jan 7, 2024 #185 Best to use the one closest to the time the system worked normally.
MarMax Contributor Joined Dec 8, 2023 Posts 578 Location SoCal Jan 7, 2024 #186 OK, I'll use the most current. Also, once it's back up and running and after the KB4048957 update we can't run the sfc /scannow where it repairs system files. This seems to be when the video driver gets messed up.
OK, I'll use the most current. Also, once it's back up and running and after the KB4048957 update we can't run the sfc /scannow where it repairs system files. This seems to be when the video driver gets messed up.
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 13,709 Jan 7, 2024 #187 OK.
MarMax Contributor Joined Dec 8, 2023 Posts 578 Location SoCal Jan 7, 2024 #188 A very interesting thing happened. I tried three different restore points and received a message that each failed. But when I exited the repair menu the system restarted and seems to be back. I have no idea what caused this. Upon completion of startup I received the message that the 1/6/2024 12:19:05 PM restore point completed successfully. Should I run the KB4048957 update again? And then what since the sfc /scannow will put it back to the black screen?
A very interesting thing happened. I tried three different restore points and received a message that each failed. But when I exited the repair menu the system restarted and seems to be back. I have no idea what caused this. Upon completion of startup I received the message that the 1/6/2024 12:19:05 PM restore point completed successfully. Should I run the KB4048957 update again? And then what since the sfc /scannow will put it back to the black screen?
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 13,709 Jan 7, 2024 #189 No. Lets have a look with sfc first. SFC VerifyOnly 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 commands into it, press enter after each Code: sfc /verifyonly Wait for this to finish before you continue Code: copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt" This will create a file, cbs.txt on your Desktop. Please attach this to your next post. Note: if the file is too big to upload to your next post please upload via a service such as Gofile or WeTransfer and just provide the download link.
No. Lets have a look with sfc first. SFC VerifyOnly 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 commands into it, press enter after each Code: sfc /verifyonly Wait for this to finish before you continue Code: copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt" This will create a file, cbs.txt on your Desktop. Please attach this to your next post. Note: if the file is too big to upload to your next post please upload via a service such as Gofile or WeTransfer and just provide the download link.
MarMax Contributor Joined Dec 8, 2023 Posts 578 Location SoCal Jan 7, 2024 #190 sfc /verifyonly ran successfully. CBS.log file is attached. Attachments cbs.zip 112.2 KB · Views: 1
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 13,709 Jan 8, 2024 #191 Don't install KB4048957 yet. 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.
Don't install KB4048957 yet. 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.
MarMax Contributor Joined Dec 8, 2023 Posts 578 Location SoCal Jan 8, 2024 #192 The sfc/ scannow ran to 100% complete but it still has the "Windows Resource Protection found corrupt files but was unable to fix some of them." I'm attaching the CBS file in case I get the black screen on reboot. Attachments CBS.zip 334 KB · Views: 1
The sfc/ scannow ran to 100% complete but it still has the "Windows Resource Protection found corrupt files but was unable to fix some of them." I'm attaching the CBS file in case I get the black screen on reboot.
MarMax Contributor Joined Dec 8, 2023 Posts 578 Location SoCal Jan 8, 2024 #193 Rebooted and the system came up fine. So it looks like the black screen issue is caused by completing the KB4048957 update. What's next?
Rebooted and the system came up fine. So it looks like the black screen issue is caused by completing the KB4048957 update. What's next?
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 13,709 Jan 9, 2024 #194 Rebooted and the system came up fine. Click to expand... Great, I was expecting that. 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. 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.
Rebooted and the system came up fine. Click to expand... Great, I was expecting that. 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. 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.
MarMax Contributor Joined Dec 8, 2023 Posts 578 Location SoCal Jan 9, 2024 #195 Both completed but the sfc / scannow found errors that could not be fixed. Hopefully the computer will reboot OK. I'm attaching the files. Attachments SFCFix.txt 297.1 KB · Views: 1 CBS.zip 413.1 KB · Views: 2
Both completed but the sfc / scannow found errors that could not be fixed. Hopefully the computer will reboot OK. I'm attaching the files.
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 13,709 Jan 10, 2024 #196 Looking good. All corruptions were fixed except one. Next fix. 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 attachment 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. 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. Attachments SFCFix.zip 136.8 KB · Views: 3
Looking good. All corruptions were fixed except one. Next fix. 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 attachment 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. 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.
MarMax Contributor Joined Dec 8, 2023 Posts 578 Location SoCal Jan 10, 2024 #197 Peter, there is no link associated with the SFCFix.zip file.
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 13,709 Jan 10, 2024 #198 Correct, its the attachment you need.
MarMax Contributor Joined Dec 8, 2023 Posts 578 Location SoCal Jan 10, 2024 #199 I'm attaching the SFCFix.txt file. It has this line: "PowerCopy:: directive failed to complete successfully." Do you still want me to run the sfc /scannow? Attachments SFCFix.txt 3.1 KB · Views: 1
I'm attaching the SFCFix.txt file. It has this line: "PowerCopy:: directive failed to complete successfully." Do you still want me to run the sfc /scannow?
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 13,709 Jan 10, 2024 #200 Restart the machine and perform step 1 again. If successful proceed with Step 2.