Need Help with Corrupt Files and System Update Readiness Tool (SURT) ...

Cfguy

New member
Joined
Apr 18, 2022
Posts
4
Hi All,



I need some help preparing for an upgrade of my HP 500-164 PC from Windows 7 x64 to Windows 11.



When I originally purchased my HP 500-164 (back in 2013), it came with Windows 8 installed, and I was, and am, still using Windows 7 x64 on all of my PCs. At the time, I used Paragon disk cloning software to clone one of my other Windows 7 x64 PCs (a Dell Inspiron 560 Pentium), and then updated the device drivers for the HP 500-164, and all worked basically well for the past eight years, until more and more software became "incompatible" with Windows 7. I realize I must finally upgrade- know that the Dell Inspiron 560 will not handle Windows 11, as it is very slow with Windows 7 x64 now, and is used on my home network as primarily a "file server" with external hard drives attached to it. However, the HP 500-164 is still working great with Windows 7 x64 (as my primary PC) and I have purchased a Windows 10 Pro usb drive from Amazon, which I believe will allow me to then upgrade to Windows 11, once installed. I really want to do an "upgrade" install, as I have many programs on my HP 500-164 that I would not want to have to re-install.



My first problem is that when I run sfc /scannow on the HP 500-164 (I have run it several time now), I receive the error " Windows Resource Protection found corrupt files but was unable to fix some of them." (A copy of my most recent CBS.log file results is attached as file "2022-08-04 CBS Scannow Results (HPDesktop).txt."



When I had posted before, I had read that Windiws 7 x64 systems were unable to run the DISM (or "System Update Readiness tool") that might help fix some Windows corruption errors; however I was referred to the "System Update Readiness tool" (SURT) that would work on Windows 7 machines, and followed the steps to download SURT files. I clicked on Microsoft Update Catalogue link (TinyURL: https://tinyl.io/6l6T) and, navigated to the title that best described my computer: System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [October 2014], and clicked the "download" box. A pop up box appeared with a listing of 32 files. I downloaded each one, numbered them (as part of filename), and put them through a virus checked (just to be sure). All came out fine; however when I clicked on the first file, it was a ".cab" file and my default "zip" program handler popped up, so I chose to "unzip", and was left with just one text file that, when opened, contained just a bunch of what looks like jargon. It looks like the 32 files that I downloaded are all either ".cab" files or ".exe" files, and after my experience clicking the first [.cab] file, I did not proceed any further.



I am confused as to what I am supposed to do at this point. Do I first extract all of the ".cab" files, and then run each of the ".exe" files that remain? Or do I extract the ".cab" files and then run the ".exe" files in the order in which they are posted on the System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [October 2014]? Or, do I do something completely different than the aforementioned two choices?



Also, if I do successfully run all of the SURT files, do I then run another "sfc /scannow" to ensure that all the previous corrupted files are now fixed, and the system is ready to be updated to Windows 10/11? What do I do if another "sfc /scannow", after having successfully run all the SURT files still shows "unfixable corrupt files"?



Any help and advice would be greatly appreciated.



Thanks so much for your help.

-Cfguy
 

Attachments

Hello and welcome,

Make sure to have a backup of all your important data, if not already done.

My first problem is that when I run sfc /scannow on the HP 500-164 (I have run it several time now), I receive the error " Windows Resource Protection found corrupt files but was unable to fix some of them."
Lets concentrate on that first.
It looks like the log was edited. Please do not edit any logs provided.

Follow the instructions below please.

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
    myjIXnC.png
    SFCFix and move the executable to your desktop.
  • 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.
    1p8eDnI.gif
  • 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:
Restart the computer.
Run the command sfc /scannow again in an elevated commandprompt and report the result.
If it fails attach the file cbs.log to your next reply. If the file is too large to upload zip it first and attach the zipped cbs.log.
 

Attachments

Hi Paul,



Apologies for my delayed reply, and also apologies for the cbs.txt file I attached to my previous post that lead you to question if I had edited the log file in any way. I actually did not change any of the original content, I just tried to add a title and scan date as the very first line, for my reference. What happened is I used "control" "A" to copy all of the original text of the cbs.log file and paste it into an .rtf file, so that I could use a larger font to make a "title" for the document that contained the PC's name and date of the scan. However, upon trying to upload it here to the forum, I learned that the forum does not accept .rtf attachments, so I went back into the .rtf file and again used "control" and "a" to select all the text and pasted it into a .txt file so that I would be able to upload it to the forum. However, I won't do this again as it didn't work out very well the first time, and I do understand the need for uploaded log files without any type of changes, so from this point on it is strictly virgin log files that will be posted. Much simpler process, as well.



I want to thank you for all of your help, and to let you know that I carefully followed all of the instructions in your reply to my post.



Below are the contents of the "SFCFix.txt" file that was on my desktop, after dragging and dropping the "SFCFix.zip" file onto the "SFCFix.exe", and agreeing to participation, as it requested:



SFCFix version 3.0.2.1 by niemiro.

Start time: 2022-08-09 18:27:30.448

Microsoft Windows 7 Service Pack 1 - amd64

Using .zip script file at E:\Cfguy's Desktop\SFCFix.zip [0]









PowerCopy::

Successfully took permissions for file or folder C:\Windows\winsxs\x86_microsoft-windows-grouppolicy-gptext_31bf3856ad364e35_6.1.7600.16385_none_372622adf05a6587\gptext.dll

Successfully took permissions for file or folder C:\Windows\winsxs\x86_microsoft-windows-g..policy-admin-gpedit_31bf3856ad364e35_6.1.7601.23932_none_d0ab6b01dc595145\gpedit.dll

Successfully took permissions for file or folder C:\Windows\winsxs\x86_microsoft-windows-fde_31bf3856ad364e35_6.1.7601.17514_none_aa136561b9ed4ae4\fde.dll

Successfully took permissions for file or folder C:\Windows\winsxs\x86_microsoft-windows-fdeploy_31bf3856ad364e35_6.1.7601.17514_none_e1bcfc28af006dea\fdeploy.dll



Successfully copied file C:\Users\Cfguy\AppData\Local\niemiro\Archive\x86_microsoft-windows-grouppolicy-gptext_31bf3856ad364e35_6.1.7600.16385_none_372622adf05a6587\gptext.dll to C:\Windows\winsxs\x86_microsoft-windows-grouppolicy-gptext_31bf3856ad364e35_6.1.7600.16385_none_372622adf05a6587\gptext.dll.

Successfully copied file C:\Users\Chris\AppData\Local\niemiro\Archive\x86_microsoft-windows-g..policy-admin-gpedit_31bf3856ad364e35_6.1.7601.23932_none_d0ab6b01dc595145\gpedit.dll to C:\Windows\winsxs\x86_microsoft-windows-g..policy-admin-gpedit_31bf3856ad364e35_6.1.7601.23932_none_d0ab6b01dc595145\gpedit.dll.

Successfully copied file C:\Users\Chris\AppData\Local\niemiro\Archive\x86_microsoft-windows-fde_31bf3856ad364e35_6.1.7601.17514_none_aa136561b9ed4ae4\fde.dll to C:\Windows\winsxs\x86_microsoft-windows-fde_31bf3856ad364e35_6.1.7601.17514_none_aa136561b9ed4ae4\fde.dll.

Successfully copied file C:\Users\Chris\AppData\Local\niemiro\Archive\x86_microsoft-windows-fdeploy_31bf3856ad364e35_6.1.7601.17514_none_e1bcfc28af006dea\fdeploy.dll to C:\Windows\winsxs\x86_microsoft-windows-fdeploy_31bf3856ad364e35_6.1.7601.17514_none_e1bcfc28af006dea\fdeploy.dll.



Successfully restored ownership for C:\Windows\winsxs\x86_microsoft-windows-grouppolicy-gptext_31bf3856ad364e35_6.1.7600.16385_none_372622adf05a6587\gptext.dll

Successfully restored permissions on C:\Windows\winsxs\x86_microsoft-windows-grouppolicy-gptext_31bf3856ad364e35_6.1.7600.16385_none_372622adf05a6587\gptext.dll

Successfully restored ownership for C:\Windows\winsxs\x86_microsoft-windows-g..policy-admin-gpedit_31bf3856ad364e35_6.1.7601.23932_none_d0ab6b01dc595145\gpedit.dll

Successfully restored permissions on C:\Windows\winsxs\x86_microsoft-windows-g..policy-admin-gpedit_31bf3856ad364e35_6.1.7601.23932_none_d0ab6b01dc595145\gpedit.dll

Successfully restored ownership for C:\Windows\winsxs\x86_microsoft-windows-fde_31bf3856ad364e35_6.1.7601.17514_none_aa136561b9ed4ae4\fde.dll

Successfully restored permissions on C:\Windows\winsxs\x86_microsoft-windows-fde_31bf3856ad364e35_6.1.7601.17514_none_aa136561b9ed4ae4\fde.dll

Successfully restored ownership for C:\Windows\winsxs\x86_microsoft-windows-fdeploy_31bf3856ad364e35_6.1.7601.17514_none_e1bcfc28af006dea\fdeploy.dll

Successfully restored permissions on C:\Windows\winsxs\x86_microsoft-windows-fdeploy_31bf3856ad364e35_6.1.7601.17514_none_e1bcfc28af006dea\fdeploy.dll

PowerCopy:: directive completed successfully.









Successfully processed all directives.







Failed to generate a complete zip file. Upload aborted.





SFCFix version 3.0.2.1 by niemiro has completed.

Currently storing 4 datablocks.

Finish time: 2022-08-09 18:40:42.730

Script hash: qBriVhfie1Al/7QJp8IcbyY9si1r3NgeArWigB3QYMg=

----------------------EOF-----------------------



Once that process was completed, I rebooted my system, as you had requested, and preformed another "sfc /scannow" with elevated, administrative permissions.



The scan took long, so I began to work on other things around the house, and the last time I came back and checked I knew that it had completed because there was no longer a "scan in progress … x% complete" message in a window on my desktop. In fact, it didn't leave any type of message regarding "corrupted files" that were unfixable, etc.; however I am unsure if it ever gave a message like that and then disappeared from the screen after a specified period of time, or if it never showed any such type of message.



As you predicted, the resulting cbs.log file was fairly large, so I used "7zip" program to zip it, and I am going to upload the resulting zipped file ("cbs.zip") as an attachment to this post.



Hope I gave you all that you needed. Please let me know what my next step should be.



Thank you again for all of your help.



-Cfguy
 

Attachments

The log looks good.

Reboot the machine.
Check Windows Update and report the result. Do NOT install any updates yet but provide a screenshot of the available important updates first.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top