H HSLee Contributor Joined Apr 1, 2019 Posts 57 Apr 22, 2019 #21 A link for the hive has been provided via a private message.
H HSLee Contributor Joined Apr 1, 2019 Posts 57 Apr 23, 2019 #22 Hi Peter, have you seen the link in a private message?
H HSLee Contributor Joined Apr 1, 2019 Posts 57 Apr 23, 2019 #23 The link for the SOFTWARE file (instead of that earlier .reg version) has been in the private message box.
The link for the SOFTWARE file (instead of that earlier .reg version) has been in the private message box.
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,643 Apr 24, 2019 #24 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. Download the Farbar Recovery Scan Tool and save it to your Desktop: 64-bit: Downloading Farbar Recovery Scan Tool 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. Step 2: Start the System Update Readiness Tool (SURT) again. On completion, attach the logfile C:\Windows\Logs\CBS\CheckSUR.log in your next reply. Attachments fixlist.txt 194.9 KB · Views: 1 Last edited: Apr 24, 2019
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. Download the Farbar Recovery Scan Tool and save it to your Desktop: 64-bit: Downloading Farbar Recovery Scan Tool 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. Step 2: Start the System Update Readiness Tool (SURT) again. On completion, attach the logfile C:\Windows\Logs\CBS\CheckSUR.log in your next reply.
H HSLee Contributor Joined Apr 1, 2019 Posts 57 Apr 24, 2019 #25 Thanks. Here are new log files Attachments Fixlog(6).txt 98 KB · Views: 1 CheckSUR(7).log 139.5 KB · Views: 1
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,643 Apr 24, 2019 #26 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. 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. Step 2: Start the System Update Readiness Tool (SURT) again. On completion, attach the logfile C:\Windows\Logs\CBS\CheckSUR.log in your next reply. Attachments fixlist.txt 129.7 KB · Views: 1
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. 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. Step 2: Start the System Update Readiness Tool (SURT) again. On completion, attach the logfile C:\Windows\Logs\CBS\CheckSUR.log in your next reply.
H HSLee Contributor Joined Apr 1, 2019 Posts 57 Apr 24, 2019 #27 Here are new log files Attachments Fixlog(7).txt 132.3 KB · Views: 1 CheckSUR(8).log 80.2 KB · Views: 1
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,643 Apr 26, 2019 #28 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. 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. Step 2: Start the System Update Readiness Tool (SURT) again. On completion, attach the logfile C:\Windows\Logs\CBS\CheckSUR.log in your next reply. Attachments fixlist.txt 47.2 KB · Views: 1
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. 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. Step 2: Start the System Update Readiness Tool (SURT) again. On completion, attach the logfile C:\Windows\Logs\CBS\CheckSUR.log in your next reply.
H HSLee Contributor Joined Apr 1, 2019 Posts 57 Apr 26, 2019 #29 Here are the new log files. Attachments Fixlog(8).txt 47.8 KB · Views: 1 CheckSUR(9).log 80.2 KB · Views: 1
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,643 Apr 26, 2019 #30 The fix didn't work as expected. Did you restart Windows after you send me the SOFTWARE hive ?
H HSLee Contributor Joined Apr 1, 2019 Posts 57 Apr 26, 2019 #31 Yes. I restarted Windows several times after sending you the SOFTWARE hive. Shouldn't I do that?
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,643 Apr 26, 2019 #32 Shouldn't I do that? Click to expand... No, leave it running till I send you a fix. Please provide a fresh copy of the SOFTWARE hive, follow the instructions in message #10.
Shouldn't I do that? Click to expand... No, leave it running till I send you a fix. Please provide a fresh copy of the SOFTWARE hive, follow the instructions in message #10.
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,643 Apr 26, 2019 #33 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. 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. Step 2: Start the System Update Readiness Tool (SURT) again. On completion, attach the logfile C:\Windows\Logs\CBS\CheckSUR.log in your next reply. Attachments fixlist.txt 46.6 KB · Views: 1
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. 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. Step 2: Start the System Update Readiness Tool (SURT) again. On completion, attach the logfile C:\Windows\Logs\CBS\CheckSUR.log in your next reply.
H HSLee Contributor Joined Apr 1, 2019 Posts 57 Apr 26, 2019 #34 Great! Now there is only one Watchlist Component missing. Attachments Fixlog(9).txt 48.3 KB · Views: 1 CheckSUR(10).log 56.4 KB · Views: 1
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,643 Apr 26, 2019 #35 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. 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. Step 2: Start the System Update Readiness Tool (SURT) again. On completion, attach the logfile C:\Windows\Logs\CBS\CheckSUR.log in your next reply. Attachments fixlist.txt 552 bytes · Views: 1
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. 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. Step 2: Start the System Update Readiness Tool (SURT) again. On completion, attach the logfile C:\Windows\Logs\CBS\CheckSUR.log in your next reply.
H HSLee Contributor Joined Apr 1, 2019 Posts 57 Apr 26, 2019 #36 Here are new log files Attachments Fixlog10.txt 982 bytes · Views: 1 CheckSUR11.log 56.1 KB · Views: 1
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,643 Apr 27, 2019 #37 Great. All Component Watchlist errors have been fixed. You may shutdown or restart the machine whenever you like. 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 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. 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: Start the System Update Readiness Tool (SURT) again. On completion, attach the logfile C:\Windows\Logs\CBS\CheckSUR.log in your next reply. Attachments SFCFix.zip 2 MB · Views: 1
Great. All Component Watchlist errors have been fixed. You may shutdown or restart the machine whenever you like. 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 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. 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: Start the System Update Readiness Tool (SURT) again. On completion, attach the logfile C:\Windows\Logs\CBS\CheckSUR.log in your next reply.
H HSLee Contributor Joined Apr 1, 2019 Posts 57 Apr 27, 2019 #38 It is indeed a great job. Thanks again. Now there are only 352 missing deployment keys to be fixed. SFCFix version 3.0.1.0 by niemiro. Start time: 2019-04-27 19:24:42.438 Microsoft Windows 7 Service Pack 1 - amd64 Using .zip script file at C:\Users\Xiang Song LI\Desktop\SFCFix.zip [0] PowerCopy:: Successfully took permissions for file or folder C:\Windows\winsxs\wow64_microsoft-windows-gdi32_31bf3856ad364e35_6.1.7601.18539_none_c1e8a48f945da7dd Successfully took permissions for file or folder C:\Windows\winsxs\amd64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.18539_none_1708c9fbb1322437 Successfully took permissions for file or folder C:\Windows\winsxs\amd64_microsoft-windows-gdi32_31bf3856ad364e35_6.1.7601.18539_none_b793fa3d5ffce5e2 Successfully copied file C:\Users\Xiang Song LI\AppData\Local\niemiro\Archive\winsxs\wow64_microsoft-windows-gdi32_31bf3856ad364e35_6.1.7601.18539_none_c1e8a48f945da7dd\gdi32.dll to C:\Windows\winsxs\wow64_microsoft-windows-gdi32_31bf3856ad364e35_6.1.7601.18539_none_c1e8a48f945da7dd\gdi32.dll. Successfully copied file C:\Users\Xiang Song LI\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.18539_none_1708c9fbb1322437\win32k.sys to C:\Windows\winsxs\amd64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.18539_none_1708c9fbb1322437\win32k.sys. Successfully copied file C:\Users\Xiang Song LI\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-gdi32_31bf3856ad364e35_6.1.7601.18539_none_b793fa3d5ffce5e2\gdi32.dll to C:\Windows\winsxs\amd64_microsoft-windows-gdi32_31bf3856ad364e35_6.1.7601.18539_none_b793fa3d5ffce5e2\gdi32.dll. Successfully restored ownership for C:\Windows\winsxs\wow64_microsoft-windows-gdi32_31bf3856ad364e35_6.1.7601.18539_none_c1e8a48f945da7dd Successfully restored permissions on C:\Windows\winsxs\wow64_microsoft-windows-gdi32_31bf3856ad364e35_6.1.7601.18539_none_c1e8a48f945da7dd Successfully restored ownership for C:\Windows\winsxs\amd64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.18539_none_1708c9fbb1322437 Successfully restored permissions on C:\Windows\winsxs\amd64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.18539_none_1708c9fbb1322437 Successfully restored ownership for C:\Windows\winsxs\amd64_microsoft-windows-gdi32_31bf3856ad364e35_6.1.7601.18539_none_b793fa3d5ffce5e2 Successfully restored permissions on C:\Windows\winsxs\amd64_microsoft-windows-gdi32_31bf3856ad364e35_6.1.7601.18539_none_b793fa3d5ffce5e2 PowerCopy:: directive completed successfully. Successfully processed all directives. SFCFix version 3.0.1.0 by niemiro has completed. Currently storing 1444 datablocks. Finish time: 2019-04-27 19:24:45.928 Script hash: /V365XQKUs842HQjXC8KMzORqV5ErS8txMKHO3tcwRQ= ----------------------EOF----------------------- Attachments CheckSUR(12).log 55.6 KB · Views: 1
It is indeed a great job. Thanks again. Now there are only 352 missing deployment keys to be fixed. SFCFix version 3.0.1.0 by niemiro. Start time: 2019-04-27 19:24:42.438 Microsoft Windows 7 Service Pack 1 - amd64 Using .zip script file at C:\Users\Xiang Song LI\Desktop\SFCFix.zip [0] PowerCopy:: Successfully took permissions for file or folder C:\Windows\winsxs\wow64_microsoft-windows-gdi32_31bf3856ad364e35_6.1.7601.18539_none_c1e8a48f945da7dd Successfully took permissions for file or folder C:\Windows\winsxs\amd64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.18539_none_1708c9fbb1322437 Successfully took permissions for file or folder C:\Windows\winsxs\amd64_microsoft-windows-gdi32_31bf3856ad364e35_6.1.7601.18539_none_b793fa3d5ffce5e2 Successfully copied file C:\Users\Xiang Song LI\AppData\Local\niemiro\Archive\winsxs\wow64_microsoft-windows-gdi32_31bf3856ad364e35_6.1.7601.18539_none_c1e8a48f945da7dd\gdi32.dll to C:\Windows\winsxs\wow64_microsoft-windows-gdi32_31bf3856ad364e35_6.1.7601.18539_none_c1e8a48f945da7dd\gdi32.dll. Successfully copied file C:\Users\Xiang Song LI\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.18539_none_1708c9fbb1322437\win32k.sys to C:\Windows\winsxs\amd64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.18539_none_1708c9fbb1322437\win32k.sys. Successfully copied file C:\Users\Xiang Song LI\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-gdi32_31bf3856ad364e35_6.1.7601.18539_none_b793fa3d5ffce5e2\gdi32.dll to C:\Windows\winsxs\amd64_microsoft-windows-gdi32_31bf3856ad364e35_6.1.7601.18539_none_b793fa3d5ffce5e2\gdi32.dll. Successfully restored ownership for C:\Windows\winsxs\wow64_microsoft-windows-gdi32_31bf3856ad364e35_6.1.7601.18539_none_c1e8a48f945da7dd Successfully restored permissions on C:\Windows\winsxs\wow64_microsoft-windows-gdi32_31bf3856ad364e35_6.1.7601.18539_none_c1e8a48f945da7dd Successfully restored ownership for C:\Windows\winsxs\amd64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.18539_none_1708c9fbb1322437 Successfully restored permissions on C:\Windows\winsxs\amd64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.18539_none_1708c9fbb1322437 Successfully restored ownership for C:\Windows\winsxs\amd64_microsoft-windows-gdi32_31bf3856ad364e35_6.1.7601.18539_none_b793fa3d5ffce5e2 Successfully restored permissions on C:\Windows\winsxs\amd64_microsoft-windows-gdi32_31bf3856ad364e35_6.1.7601.18539_none_b793fa3d5ffce5e2 PowerCopy:: directive completed successfully. Successfully processed all directives. SFCFix version 3.0.1.0 by niemiro has completed. Currently storing 1444 datablocks. Finish time: 2019-04-27 19:24:45.928 Script hash: /V365XQKUs842HQjXC8KMzORqV5ErS8txMKHO3tcwRQ= ----------------------EOF-----------------------
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,643 Apr 27, 2019 #39 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. 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. Step 2: Start the System Update Readiness Tool (SURT) again. On completion, attach the logfile C:\Windows\Logs\CBS\CheckSUR.log in your next reply. Attachments fixlist.txt 69.5 KB · Views: 1
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. 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. Step 2: Start the System Update Readiness Tool (SURT) again. On completion, attach the logfile C:\Windows\Logs\CBS\CheckSUR.log in your next reply.
H HSLee Contributor Joined Apr 1, 2019 Posts 57 Apr 27, 2019 #40 Here are new log files. Attachments Fixlog(11).txt 35.3 KB · Views: 1 CheckSUR(13).log 50.6 KB · Views: 1