D Docfxit Contributor Joined Feb 22, 2015 Posts 248 Sep 19, 2020 #1 Windows Resource Protection found corrupt files but was unable to fix some of them. running Window 7 Ultimate sp1 32bit Please help me fix this OS. Thank you, Docfxit Attachments CBS.7z 44.7 KB · Views: 1 SFCFix.7z 461 bytes · Views: 1
Windows Resource Protection found corrupt files but was unable to fix some of them. running Window 7 Ultimate sp1 32bit Please help me fix this OS. Thank you, Docfxit
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,616 Sep 20, 2020 #2 Hello and welcome, Follow the instructions below please. 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. Open the file, then copy and paste its content in your next reply. Attachments SFCFix.zip 2.5 KB · Views: 2
Hello and welcome, Follow the instructions below please. 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. Open the file, then copy and paste its content in your next reply.
D Docfxit Contributor Joined Feb 22, 2015 Posts 248 Sep 20, 2020 #3 Thank you for helping me resolve this issue. Attachments SFCFix.txt 9.8 KB · Views: 2
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,616 Sep 20, 2020 #4 Do you have any additional languages installed for Windows ? If so, which ones ?
D Docfxit Contributor Joined Feb 22, 2015 Posts 248 Sep 20, 2020 #5 Hi Peter, I do not have any additional languages installed. Only English. Thank you, Docfxit
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,616 Sep 20, 2020 #6 Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine. Download the Farbar Recovery Scan Tool and save it to your Desktop: 32-bit: Downloading Farbar Recovery Scan Tool Download the attachment fixlist.txt and save it to your desktop. Right-click on FRST.exe and select "Run as administrator". Press the Fix button. The tool will now process fixlist.txt. 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. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from. Post the logfile Fixlog.txt as attachment in your next reply. Attachments fixlist.txt 205 bytes · Views: 1
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine. Download the Farbar Recovery Scan Tool and save it to your Desktop: 32-bit: Downloading Farbar Recovery Scan Tool Download the attachment fixlist.txt and save it to your desktop. Right-click on FRST.exe and select "Run as administrator". Press the Fix button. The tool will now process fixlist.txt. 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. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from. Post the logfile Fixlog.txt as attachment in your next reply.
D Docfxit Contributor Joined Feb 22, 2015 Posts 248 Sep 20, 2020 #7 That's really nice of you to fix this for me. Thank you, Docfxit Attachments Fixlog.txt 3.3 KB · Views: 1
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,616 Sep 20, 2020 #8 Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine. Download the attachment fixlist.txt and save it to your desktop. Right-click on FRST.exe and select "Run as administrator". Press the Fix button. The tool will now process fixlist.txt. 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. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from. Post the logfile Fixlog.txt as attachment in your next reply. Attachments fixlist.txt 662 bytes · Views: 2
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine. Download the attachment fixlist.txt and save it to your desktop. Right-click on FRST.exe and select "Run as administrator". Press the Fix button. The tool will now process fixlist.txt. 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. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from. Post the logfile Fixlog.txt as attachment in your next reply.
D Docfxit Contributor Joined Feb 22, 2015 Posts 248 Sep 20, 2020 #9 Just to set your mind at ease. I have no need for any language except U.S. English. Thanks, Docfxit Attachments Fixlog.txt 6 KB · Views: 1
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,616 Sep 21, 2020 #10 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. Open the file, then copy and paste its content in your next reply. Attachments SFCFix.zip 2 KB · Views: 2
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. Open the file, then copy and paste its content in your next reply.
D Docfxit Contributor Joined Feb 22, 2015 Posts 248 Sep 21, 2020 #11 I think it did exactly what you wanted. Thanks, Docfxit Attachments SFCFix.txt 8.7 KB · Views: 1
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,616 Sep 21, 2020 #12 Run the command sfc /scannow in an elevated command prompt and report the result. If it fails attach the file cbs.log to your next reply.
Run the command sfc /scannow in an elevated command prompt and report the result. If it fails attach the file cbs.log to your next reply.
D Docfxit Contributor Joined Feb 22, 2015 Posts 248 Sep 21, 2020 #13 I am getting: Windows Resource Protection found corrupt files but was unable to fix some of them. Attachments CBS.7z 45 KB · Views: 1
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,616 Sep 22, 2020 #14 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. Open the file, then copy and paste its content in your next reply. Step 2: Run the command sfc /scannow in an elevated command prompt and report the result. If it fails attach the file cbs.log to your next reply. Attachments SFCFix.zip 2 KB · Views: 1
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. Open the file, then copy and paste its content in your next reply. Step 2: Run the command sfc /scannow in an elevated command prompt and report the result. If it fails attach the file cbs.log to your next reply.
D Docfxit Contributor Joined Feb 22, 2015 Posts 248 Sep 22, 2020 #15 Sorry. That didn't fix it. Windows Resource Protection found corrupt files but was unable to fix some of them. Attachments SFCFix.txt 9.1 KB · Views: 1 CBS.log 1,021.9 KB · Views: 1
Sorry. That didn't fix it. Windows Resource Protection found corrupt files but was unable to fix some of them.
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,616 Sep 22, 2020 #16 Well, there were 7 corruptions and 5 are fixed. 2 corruptions remaining. Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine. Download the attachment fixlist.txt and save it to your desktop. Right-click on FRST.exe and select "Run as administrator". Press the Fix button. The tool will now process fixlist.txt. 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. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from. Post the logfile Fixlog.txt as attachment in your next reply. Attachments fixlist.txt 122 bytes · Views: 2
Well, there were 7 corruptions and 5 are fixed. 2 corruptions remaining. Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine. Download the attachment fixlist.txt and save it to your desktop. Right-click on FRST.exe and select "Run as administrator". Press the Fix button. The tool will now process fixlist.txt. 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. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from. Post the logfile Fixlog.txt as attachment in your next reply.
D Docfxit Contributor Joined Feb 22, 2015 Posts 248 Sep 22, 2020 #17 You are really great for helping me get this fixed. Thank you, Docfxit Attachments Fixlog.txt 1.3 KB · Views: 1
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,616 Sep 23, 2020 #18 Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine. Download the attachment fixlist.txt and save it to your desktop. Right-click on FRST.exe and select "Run as administrator". Press the Fix button. The tool will now process fixlist.txt. 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. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from. Post the logfile Fixlog.txt as attachment in your next reply. Attachments fixlist.txt 264 bytes · Views: 2
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine. Download the attachment fixlist.txt and save it to your desktop. Right-click on FRST.exe and select "Run as administrator". Press the Fix button. The tool will now process fixlist.txt. 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. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from. Post the logfile Fixlog.txt as attachment in your next reply.
D Docfxit Contributor Joined Feb 22, 2015 Posts 248 Sep 23, 2020 #19 Thank you for working on this for me. Docfxit Attachments Fixlog.txt 2.2 KB · Views: 1
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,616 Sep 23, 2020 #20 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. Open the file, then copy and paste its content in your next reply. Step 2: Run the command sfc /scannow in an elevated command prompt and report the result. If it fails attach the file cbs.log to your next reply. Attachments SFCFix.zip 983 bytes · Views: 1
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. Open the file, then copy and paste its content in your next reply. Step 2: Run the command sfc /scannow in an elevated command prompt and report the result. If it fails attach the file cbs.log to your next reply.