M mst321 Member Joined Jun 7, 2019 Posts 12 Jun 7, 2019 #1 All updates fail - like many other posters. Have tried a billion different solutions posted by different users and forums and am now at the end of my rope. This is a last hope and if this fails, I will move to the country and abandon all technology. Please help ... I do not like insects. I cannot upload the compressed CBS.zip file as the sire states "The uploaded file is too large for the server to process. "
All updates fail - like many other posters. Have tried a billion different solutions posted by different users and forums and am now at the end of my rope. This is a last hope and if this fails, I will move to the country and abandon all technology. Please help ... I do not like insects. I cannot upload the compressed CBS.zip file as the sire states "The uploaded file is too large for the server to process. "
M mst321 Member Joined Jun 7, 2019 Posts 12 Jun 7, 2019 #2 Sorry, I should have read the whole instruction set. Tried to load to G Drive but no luck. Attached is the output file from SFCFix and CheckSur from running the readiness tool. SURT total detected corruption count: 722 Attachments SFCFix.txt 1.7 KB · Views: 1 CheckSUR.log 162.8 KB · Views: 1
Sorry, I should have read the whole instruction set. Tried to load to G Drive but no luck. Attached is the output file from SFCFix and CheckSur from running the readiness tool. SURT total detected corruption count: 722
M mst321 Member Joined Jun 7, 2019 Posts 12 Jun 9, 2019 #3 Hello, I have an update. Using some additional guidance I was able to download the 27 MS KB files identified in the CheckSUR.log from the MS catalog and put them in the Packages directory Windows/Temp/CheckSUR and ran the Widows readiness tool again - took about 8 hours. Many of the 722 corruption count issues were solved, but a number of new ones were identified. Went through the same process for the new ones. I am now at point where there are only 5 corruption count issues remaining across three MS KB files - 2 of which are not available at the MS catalog. The one that is available - KB2952664 - I went through the same process but the corruption issue was not resolved. I also reran the FSCfix.exe which also shows 5 issues not fixable - attached. I then tried to install the MS latest monthly rollup for May 2019 but it failed. Now do not know what is next. I was able to load the zipped CBS directory ~132MB to WeTransfer - CBS.zip Any help would be greatly appreciated. MS error code on Rollup install 80073701 Attachments SFCFix.txt 1.7 KB · Views: 2 CheckSUR.log 1.8 KB · Views: 1
Hello, I have an update. Using some additional guidance I was able to download the 27 MS KB files identified in the CheckSUR.log from the MS catalog and put them in the Packages directory Windows/Temp/CheckSUR and ran the Widows readiness tool again - took about 8 hours. Many of the 722 corruption count issues were solved, but a number of new ones were identified. Went through the same process for the new ones. I am now at point where there are only 5 corruption count issues remaining across three MS KB files - 2 of which are not available at the MS catalog. The one that is available - KB2952664 - I went through the same process but the corruption issue was not resolved. I also reran the FSCfix.exe which also shows 5 issues not fixable - attached. I then tried to install the MS latest monthly rollup for May 2019 but it failed. Now do not know what is next. I was able to load the zipped CBS directory ~132MB to WeTransfer - CBS.zip Any help would be greatly appreciated. MS error code on Rollup install 80073701
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,600 Jun 12, 2019 #4 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 37.3 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.
M mst321 Member Joined Jun 7, 2019 Posts 12 Jun 12, 2019 #5 Thank you - please see below. Also, the June MS rollup was released yesterday. Tried to install but failed. Was able to install the security only update - which I did going back to March 2017 when the rollup installs started failing. SFCFix version 3.0.2.0 by niemiro. Start time: 2019-06-12 14:59:38.308 Microsoft Windows 7 Service Pack 1 - amd64 Using .zip script file at C:\Users\MSTICS\Desktop\SFCFix.zip [1] PowerCopy:: Successfully took permissions for file or folder C:\Windows\servicing\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.19.0.cat Successfully took permissions for file or folder C:\Windows\servicing\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.19.0.mum Successfully took permissions for file or folder C:\Windows\servicing\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.21.6.cat Successfully took permissions for file or folder C:\Windows\servicing\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.21.6.mum Successfully took permissions for file or folder C:\Windows\servicing\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.22.2.cat Successfully took permissions for file or folder C:\Windows\servicing\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.22.2.mum Successfully took permissions for file or folder C:\Windows\servicing\packages\package_1_for_kb3210131~31bf3856ad364e35~amd64~~6.1.1.0.cat Successfully took permissions for file or folder C:\Windows\servicing\packages\package_1_for_kb3210131~31bf3856ad364e35~amd64~~6.1.1.0.mum Successfully took permissions for file or folder C:\Windows\servicing\packages\package_1_for_kb4014565~31bf3856ad364e35~amd64~~6.1.1.2.cat Successfully took permissions for file or folder C:\Windows\servicing\packages\package_1_for_kb4014565~31bf3856ad364e35~amd64~~6.1.1.2.mum Successfully copied file C:\Users\MSTICS\AppData\Local\niemiro\Archive\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.19.0.cat to C:\Windows\servicing\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.19.0.cat. Successfully copied file C:\Users\MSTICS\AppData\Local\niemiro\Archive\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.19.0.mum to C:\Windows\servicing\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.19.0.mum. Successfully copied file C:\Users\MSTICS\AppData\Local\niemiro\Archive\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.21.6.cat to C:\Windows\servicing\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.21.6.cat. Successfully copied file C:\Users\MSTICS\AppData\Local\niemiro\Archive\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.21.6.mum to C:\Windows\servicing\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.21.6.mum. Successfully copied file C:\Users\MSTICS\AppData\Local\niemiro\Archive\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.22.2.cat to C:\Windows\servicing\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.22.2.cat. Successfully copied file C:\Users\MSTICS\AppData\Local\niemiro\Archive\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.22.2.mum to C:\Windows\servicing\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.22.2.mum. Successfully copied file C:\Users\MSTICS\AppData\Local\niemiro\Archive\packages\package_1_for_kb3210131~31bf3856ad364e35~amd64~~6.1.1.0.cat to C:\Windows\servicing\packages\package_1_for_kb3210131~31bf3856ad364e35~amd64~~6.1.1.0.cat. Successfully copied file C:\Users\MSTICS\AppData\Local\niemiro\Archive\packages\package_1_for_kb3210131~31bf3856ad364e35~amd64~~6.1.1.0.mum to C:\Windows\servicing\packages\package_1_for_kb3210131~31bf3856ad364e35~amd64~~6.1.1.0.mum. Successfully copied file C:\Users\MSTICS\AppData\Local\niemiro\Archive\packages\package_1_for_kb4014565~31bf3856ad364e35~amd64~~6.1.1.2.cat to C:\Windows\servicing\packages\package_1_for_kb4014565~31bf3856ad364e35~amd64~~6.1.1.2.cat. Successfully copied file C:\Users\MSTICS\AppData\Local\niemiro\Archive\packages\package_1_for_kb4014565~31bf3856ad364e35~amd64~~6.1.1.2.mum to C:\Windows\servicing\packages\package_1_for_kb4014565~31bf3856ad364e35~amd64~~6.1.1.2.mum. Successfully restored ownership for C:\Windows\servicing\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.19.0.cat Successfully restored permissions on C:\Windows\servicing\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.19.0.cat Successfully restored ownership for C:\Windows\servicing\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.19.0.mum Successfully restored permissions on C:\Windows\servicing\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.19.0.mum Successfully restored ownership for C:\Windows\servicing\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.21.6.cat Successfully restored permissions on C:\Windows\servicing\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.21.6.cat Successfully restored ownership for C:\Windows\servicing\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.21.6.mum Successfully restored permissions on C:\Windows\servicing\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.21.6.mum Successfully restored ownership for C:\Windows\servicing\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.22.2.cat Successfully restored permissions on C:\Windows\servicing\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.22.2.cat Successfully restored ownership for C:\Windows\servicing\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.22.2.mum Successfully restored permissions on C:\Windows\servicing\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.22.2.mum Successfully restored ownership for C:\Windows\servicing\packages\package_1_for_kb3210131~31bf3856ad364e35~amd64~~6.1.1.0.cat Successfully restored permissions on C:\Windows\servicing\packages\package_1_for_kb3210131~31bf3856ad364e35~amd64~~6.1.1.0.cat Successfully restored ownership for C:\Windows\servicing\packages\package_1_for_kb3210131~31bf3856ad364e35~amd64~~6.1.1.0.mum Successfully restored permissions on C:\Windows\servicing\packages\package_1_for_kb3210131~31bf3856ad364e35~amd64~~6.1.1.0.mum Successfully restored ownership for C:\Windows\servicing\packages\package_1_for_kb4014565~31bf3856ad364e35~amd64~~6.1.1.2.cat Successfully restored permissions on C:\Windows\servicing\packages\package_1_for_kb4014565~31bf3856ad364e35~amd64~~6.1.1.2.cat Successfully restored ownership for C:\Windows\servicing\packages\package_1_for_kb4014565~31bf3856ad364e35~amd64~~6.1.1.2.mum Successfully restored permissions on C:\Windows\servicing\packages\package_1_for_kb4014565~31bf3856ad364e35~amd64~~6.1.1.2.mum PowerCopy:: directive completed successfully. Successfully processed all directives. SFCFix version 3.0.2.0 by niemiro has completed. Currently storing 11 datablocks. Finish time: 2019-06-12 14:59:39.494 Script hash: 9Cl2FM/bHvnVPfRsWR3DU44/mh752qvX4FYTSjQhNz4= ----------------------EOF-----------------------
Thank you - please see below. Also, the June MS rollup was released yesterday. Tried to install but failed. Was able to install the security only update - which I did going back to March 2017 when the rollup installs started failing. SFCFix version 3.0.2.0 by niemiro. Start time: 2019-06-12 14:59:38.308 Microsoft Windows 7 Service Pack 1 - amd64 Using .zip script file at C:\Users\MSTICS\Desktop\SFCFix.zip [1] PowerCopy:: Successfully took permissions for file or folder C:\Windows\servicing\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.19.0.cat Successfully took permissions for file or folder C:\Windows\servicing\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.19.0.mum Successfully took permissions for file or folder C:\Windows\servicing\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.21.6.cat Successfully took permissions for file or folder C:\Windows\servicing\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.21.6.mum Successfully took permissions for file or folder C:\Windows\servicing\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.22.2.cat Successfully took permissions for file or folder C:\Windows\servicing\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.22.2.mum Successfully took permissions for file or folder C:\Windows\servicing\packages\package_1_for_kb3210131~31bf3856ad364e35~amd64~~6.1.1.0.cat Successfully took permissions for file or folder C:\Windows\servicing\packages\package_1_for_kb3210131~31bf3856ad364e35~amd64~~6.1.1.0.mum Successfully took permissions for file or folder C:\Windows\servicing\packages\package_1_for_kb4014565~31bf3856ad364e35~amd64~~6.1.1.2.cat Successfully took permissions for file or folder C:\Windows\servicing\packages\package_1_for_kb4014565~31bf3856ad364e35~amd64~~6.1.1.2.mum Successfully copied file C:\Users\MSTICS\AppData\Local\niemiro\Archive\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.19.0.cat to C:\Windows\servicing\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.19.0.cat. Successfully copied file C:\Users\MSTICS\AppData\Local\niemiro\Archive\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.19.0.mum to C:\Windows\servicing\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.19.0.mum. Successfully copied file C:\Users\MSTICS\AppData\Local\niemiro\Archive\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.21.6.cat to C:\Windows\servicing\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.21.6.cat. Successfully copied file C:\Users\MSTICS\AppData\Local\niemiro\Archive\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.21.6.mum to C:\Windows\servicing\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.21.6.mum. Successfully copied file C:\Users\MSTICS\AppData\Local\niemiro\Archive\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.22.2.cat to C:\Windows\servicing\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.22.2.cat. Successfully copied file C:\Users\MSTICS\AppData\Local\niemiro\Archive\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.22.2.mum to C:\Windows\servicing\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.22.2.mum. Successfully copied file C:\Users\MSTICS\AppData\Local\niemiro\Archive\packages\package_1_for_kb3210131~31bf3856ad364e35~amd64~~6.1.1.0.cat to C:\Windows\servicing\packages\package_1_for_kb3210131~31bf3856ad364e35~amd64~~6.1.1.0.cat. Successfully copied file C:\Users\MSTICS\AppData\Local\niemiro\Archive\packages\package_1_for_kb3210131~31bf3856ad364e35~amd64~~6.1.1.0.mum to C:\Windows\servicing\packages\package_1_for_kb3210131~31bf3856ad364e35~amd64~~6.1.1.0.mum. Successfully copied file C:\Users\MSTICS\AppData\Local\niemiro\Archive\packages\package_1_for_kb4014565~31bf3856ad364e35~amd64~~6.1.1.2.cat to C:\Windows\servicing\packages\package_1_for_kb4014565~31bf3856ad364e35~amd64~~6.1.1.2.cat. Successfully copied file C:\Users\MSTICS\AppData\Local\niemiro\Archive\packages\package_1_for_kb4014565~31bf3856ad364e35~amd64~~6.1.1.2.mum to C:\Windows\servicing\packages\package_1_for_kb4014565~31bf3856ad364e35~amd64~~6.1.1.2.mum. Successfully restored ownership for C:\Windows\servicing\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.19.0.cat Successfully restored permissions on C:\Windows\servicing\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.19.0.cat Successfully restored ownership for C:\Windows\servicing\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.19.0.mum Successfully restored permissions on C:\Windows\servicing\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.19.0.mum Successfully restored ownership for C:\Windows\servicing\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.21.6.cat Successfully restored permissions on C:\Windows\servicing\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.21.6.cat Successfully restored ownership for C:\Windows\servicing\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.21.6.mum Successfully restored permissions on C:\Windows\servicing\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.21.6.mum Successfully restored ownership for C:\Windows\servicing\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.22.2.cat Successfully restored permissions on C:\Windows\servicing\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.22.2.cat Successfully restored ownership for C:\Windows\servicing\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.22.2.mum Successfully restored permissions on C:\Windows\servicing\packages\package_1_for_kb2952664~31bf3856ad364e35~amd64~~6.1.22.2.mum Successfully restored ownership for C:\Windows\servicing\packages\package_1_for_kb3210131~31bf3856ad364e35~amd64~~6.1.1.0.cat Successfully restored permissions on C:\Windows\servicing\packages\package_1_for_kb3210131~31bf3856ad364e35~amd64~~6.1.1.0.cat Successfully restored ownership for C:\Windows\servicing\packages\package_1_for_kb3210131~31bf3856ad364e35~amd64~~6.1.1.0.mum Successfully restored permissions on C:\Windows\servicing\packages\package_1_for_kb3210131~31bf3856ad364e35~amd64~~6.1.1.0.mum Successfully restored ownership for C:\Windows\servicing\packages\package_1_for_kb4014565~31bf3856ad364e35~amd64~~6.1.1.2.cat Successfully restored permissions on C:\Windows\servicing\packages\package_1_for_kb4014565~31bf3856ad364e35~amd64~~6.1.1.2.cat Successfully restored ownership for C:\Windows\servicing\packages\package_1_for_kb4014565~31bf3856ad364e35~amd64~~6.1.1.2.mum Successfully restored permissions on C:\Windows\servicing\packages\package_1_for_kb4014565~31bf3856ad364e35~amd64~~6.1.1.2.mum PowerCopy:: directive completed successfully. Successfully processed all directives. SFCFix version 3.0.2.0 by niemiro has completed. Currently storing 11 datablocks. Finish time: 2019-06-12 14:59:39.494 Script hash: 9Cl2FM/bHvnVPfRsWR3DU44/mh752qvX4FYTSjQhNz4= ----------------------EOF-----------------------
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,600 Jun 12, 2019 #6 Start the System Update Readiness Tool (SURT) again. On completion, attach the logfile C:\Windows\Logs\CBS\CheckSUR.log in your next reply.
Start the System Update Readiness Tool (SURT) again. On completion, attach the logfile C:\Windows\Logs\CBS\CheckSUR.log in your next reply.
M mst321 Member Joined Jun 7, 2019 Posts 12 Jun 12, 2019 #7 Hello, Please see attached. It indicates no errors. Attachments CheckSUR.log 395 bytes · Views: 1
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,600 Jun 12, 2019 #8 Great. Check Windows Update again and report the result.
M mst321 Member Joined Jun 7, 2019 Posts 12 Jun 12, 2019 #9 Just tried installing the June monthly rollup and same result. See images attached. Attachments Capture 0.PNG 28.7 KB · Views: 5 Capture.PNG 66.8 KB · Views: 4
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,600 Jun 12, 2019 #10 Please zip all files in the folder C:\Windows\Logs\CBS and attach it to your next reply. Note: if the file is too big to upload to your next post please upload via a service such as Filedropper or One Drive or SendSpace and provide the download link.
Please zip all files in the folder C:\Windows\Logs\CBS and attach it to your next reply. Note: if the file is too big to upload to your next post please upload via a service such as Filedropper or One Drive or SendSpace and provide the download link.
M mst321 Member Joined Jun 7, 2019 Posts 12 Jun 12, 2019 #11 Hello, Please see attached. Used we transfer due to size. CBS.zip
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,600 Jun 12, 2019 #12 Remove Update Manually 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 command into it, then press enter. wusa /uninstall /KB:4075211 Let me know if it says it was successful or if there are any errors.
Remove Update Manually 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 command into it, then press enter. wusa /uninstall /KB:4075211 Let me know if it says it was successful or if there are any errors.
M mst321 Member Joined Jun 7, 2019 Posts 12 Jun 12, 2019 #13 Hello,, Message that update no installed on computer. See attached. Attachments Capture.PNG 95.5 KB · Views: 4
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,600 Jun 12, 2019 #14 Please do following: FRST Registry Search Click your Start button and choose Control Panel. In the upper right corner ensure the View by: is set to Category. Select the Programs group. Click the Turn Windows features on or off link. This will bring up the Server Manager dialog. Note: This loads your components hive which is what we want. Please keep this dialog open while you perform the remaining steps. You can minimize it if you wish but keep it open. Download the Farbar Recovery Scan Tool and save it to your Desktop: 64-bit: Downloading Farbar Recovery Scan Tool Right-click on the file FRST64.exe and choose Run as administrator. Copy and paste KB4075211 into the Search box and click the Search Registry button. When the scan is complete, a message will display that 'SearchReg.txt' is saved in the same folder FRST was started from. Notepad will open this file also. Close Notepad and attach the file 'SearchReg.txt' to your next reply. You may close any remaining open windows now.
Please do following: FRST Registry Search Click your Start button and choose Control Panel. In the upper right corner ensure the View by: is set to Category. Select the Programs group. Click the Turn Windows features on or off link. This will bring up the Server Manager dialog. Note: This loads your components hive which is what we want. Please keep this dialog open while you perform the remaining steps. You can minimize it if you wish but keep it open. Download the Farbar Recovery Scan Tool and save it to your Desktop: 64-bit: Downloading Farbar Recovery Scan Tool Right-click on the file FRST64.exe and choose Run as administrator. Copy and paste KB4075211 into the Search box and click the Search Registry button. When the scan is complete, a message will display that 'SearchReg.txt' is saved in the same folder FRST was started from. Notepad will open this file also. Close Notepad and attach the file 'SearchReg.txt' to your next reply. You may close any remaining open windows now.
M mst321 Member Joined Jun 7, 2019 Posts 12 Jun 12, 2019 #15 Have to run will do later. Thanks for your help on this.
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,600 Jun 12, 2019 #16 No problem.
M mst321 Member Joined Jun 7, 2019 Posts 12 Jun 12, 2019 #17 Hello, Please see attached Attachments SearchReg.txt 1.5 MB · Views: 2
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,600 Jun 13, 2019 #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 FRST64.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 1.4 MB · 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 FRST64.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.
M mst321 Member Joined Jun 7, 2019 Posts 12 Jun 13, 2019 #19 Hello, Please see attached. Thanks for your time on this. Attachments Fixlog.txt 2.8 MB · Views: 1
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,600 Jun 13, 2019 #20 Check Windows Update again and report the result.
