T Traveler42 Contributor Joined Jul 16, 2017 Posts 57 Aug 30, 2017 #21 Ok, here is the log file as 2017-08-30-cbs.zip ==== Attachments 2017-08-30-cbs.zip 664 KB · Views: 3
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Aug 31, 2017 #22 SFCFix Script Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own. Download SFCFix.exe (by niemiro) and save this to your Desktop. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it. Save any open documents and close all open windows. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip. Drag the file SFCFix.zip onto the file SFCFix.exe and release it. SFCFix will now process the script. Upon completion, a file should be created on your Desktop: SFCFix.txt. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put tags around the log to break up the text. Attachments SFCFix.zip 4.1 MB · Views: 2
SFCFix Script Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own. Download SFCFix.exe (by niemiro) and save this to your Desktop. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it. Save any open documents and close all open windows. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip. Drag the file SFCFix.zip onto the file SFCFix.exe and release it. SFCFix will now process the script. Upon completion, a file should be created on your Desktop: SFCFix.txt. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put tags around the log to break up the text.
T Traveler42 Contributor Joined Jul 16, 2017 Posts 57 Aug 31, 2017 #23 It still is offering the same 3 updates. Here is the output: === SFCFix version 3.0.0.0 by niemiro. Start time: 2017-08-31 06:39:48.514 Microsoft Windows 8.1 - amd64 Using .zip script file at C:\Users\jim\Desktop\SFCFix.zip [0] PowerCopy:: Successfully took permissions for file or folder C:\Windows\winsxs\wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.16384_none_26b2ee6371e75c38 Successfully copied file C:\Users\jim\AppData\Local\niemiro\Archive\winsxs\wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.16384_none_26b2ee6371e75c38\Flash.ocx to C:\Windows\winsxs\wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.16384_none_26b2ee6371e75c38\Flash.ocx. Successfully restored ownership for C:\Windows\winsxs\wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.16384_none_26b2ee6371e75c38 Successfully restored permissions on C:\Windows\winsxs\wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.16384_none_26b2ee6371e75c38 PowerCopy:: directive completed successfully. Successfully processed all directives. SFCFix version 3.0.0.0 by niemiro has completed. Currently storing 19 datablocks. Finish time: 2017-08-31 06:39:49.138 Script hash: OsEsDKbRj4MA0TgtVYfCowBFEfVSW+9iyEae+16pKVU= ----------------------EOF-----------------------
It still is offering the same 3 updates. Here is the output: === SFCFix version 3.0.0.0 by niemiro. Start time: 2017-08-31 06:39:48.514 Microsoft Windows 8.1 - amd64 Using .zip script file at C:\Users\jim\Desktop\SFCFix.zip [0] PowerCopy:: Successfully took permissions for file or folder C:\Windows\winsxs\wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.16384_none_26b2ee6371e75c38 Successfully copied file C:\Users\jim\AppData\Local\niemiro\Archive\winsxs\wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.16384_none_26b2ee6371e75c38\Flash.ocx to C:\Windows\winsxs\wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.16384_none_26b2ee6371e75c38\Flash.ocx. Successfully restored ownership for C:\Windows\winsxs\wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.16384_none_26b2ee6371e75c38 Successfully restored permissions on C:\Windows\winsxs\wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.16384_none_26b2ee6371e75c38 PowerCopy:: directive completed successfully. Successfully processed all directives. SFCFix version 3.0.0.0 by niemiro has completed. Currently storing 19 datablocks. Finish time: 2017-08-31 06:39:49.138 Script hash: OsEsDKbRj4MA0TgtVYfCowBFEfVSW+9iyEae+16pKVU= ----------------------EOF-----------------------
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Aug 31, 2017 #24 Step#1 - DISM /RestoreHealth Scan Warning:this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own. Right-click on the Start button and select Command Prompt (Admin) When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter Dism /Online /Cleanup-Image /RestoreHealth Once it finishes, copy and paste the following into the command-prompt window and press Enter. If prompted to overwrite the existing file go ahead. copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt" Once this has completed please go to your Desktop and you will find CBS.txt => Please zip/upload to this thread. Please Note:: if the file is too big (over 7MB) to upload to your next post, please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
Step#1 - DISM /RestoreHealth Scan Warning:this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own. Right-click on the Start button and select Command Prompt (Admin) When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter Dism /Online /Cleanup-Image /RestoreHealth Once it finishes, copy and paste the following into the command-prompt window and press Enter. If prompted to overwrite the existing file go ahead. copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt" Once this has completed please go to your Desktop and you will find CBS.txt => Please zip/upload to this thread. Please Note:: if the file is too big (over 7MB) to upload to your next post, please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
T Traveler42 Contributor Joined Jul 16, 2017 Posts 57 Aug 31, 2017 #25 Here is the cbs.zip === Attachments 2017-08-31-cbs.zip 797 KB · Views: 1
T Traveler42 Contributor Joined Jul 16, 2017 Posts 57 Aug 31, 2017 #26 FYI, it continues to offer the 3 updates.
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Aug 31, 2017 #27 Remove Update Manually 1. Click on the Start button and in the search box, type Command Prompt 2. When you see Command Prompt on the list, right-click on it and select Run as administrator 3. When command prompt opens, copy and paste the following command into it, press enter wusa /uninstall /KB:2919355 4. Let me know if it says it was successful or if there are any errors.
Remove Update Manually 1. Click on the Start button and in the search box, type Command Prompt 2. When you see Command Prompt on the list, right-click on it and select Run as administrator 3. When command prompt opens, copy and paste the following command into it, press enter wusa /uninstall /KB:2919355 4. Let me know if it says it was successful or if there are any errors.
T Traveler42 Contributor Joined Jul 16, 2017 Posts 57 Sep 1, 2017 #28 It says in a dialog that the KB is not installed on this computer. And even after is says "successful" to the install it still says that.
It says in a dialog that the KB is not installed on this computer. And even after is says "successful" to the install it still says that.
T Traveler42 Contributor Joined Jul 16, 2017 Posts 57 Sep 1, 2017 #29 And just in case, here is the cbs.txt file: === Attachments 2017-09-01-cbs.zip 797 KB · Views: 1
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Sep 1, 2017 #30 FRST Registry Search 1. Click your Start button and type cmd. 2. Right-click on Command-Prompt that comes up and choose Run as administrator. 3. In the command-prompt window please copy and paste the following and then hit enter. reg load HKLM\COMPONENTS c:\windows\system32\config\COMPONENTS 4. If you see "The operation completed successfully." then you did it correctly and can move on. 5. Please download Farbar Recovery Scan Tool and save it to your Desktop. Note: You need to run the 64-bit Version so please ensure you download that one. 6. Run FRST64 by Right-Clicking on the file and choosing Run as administrator. 7. Copy and paste KB2919355 into the Search box and click the Search Registry button. 8. When the scan is complete a notepad window will open with the results. Please copy and paste the contents in your next reply. If for some reason notepad doesn't open the file should be saved on your desktop named Search.txt. 9. You may close any remaining open windows now.
FRST Registry Search 1. Click your Start button and type cmd. 2. Right-click on Command-Prompt that comes up and choose Run as administrator. 3. In the command-prompt window please copy and paste the following and then hit enter. reg load HKLM\COMPONENTS c:\windows\system32\config\COMPONENTS 4. If you see "The operation completed successfully." then you did it correctly and can move on. 5. Please download Farbar Recovery Scan Tool and save it to your Desktop. Note: You need to run the 64-bit Version so please ensure you download that one. 6. Run FRST64 by Right-Clicking on the file and choosing Run as administrator. 7. Copy and paste KB2919355 into the Search box and click the Search Registry button. 8. When the scan is complete a notepad window will open with the results. Please copy and paste the contents in your next reply. If for some reason notepad doesn't open the file should be saved on your desktop named Search.txt. 9. You may close any remaining open windows now.
T Traveler42 Contributor Joined Jul 16, 2017 Posts 57 Sep 1, 2017 #31 Ok, here is the output of the search: === Attachments 2017-09-01-SearchReg.txt.zip 203.9 KB · Views: 3
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Sep 1, 2017 #32 FRST Fix NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system 1. Download the file from the link and save it to the Desktop. Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop). 2. Run FRST64 by Right-Clicking on the file and choosing Run as administrator. 3. Press the Fix button just once and wait. 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. 4. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply. Dropbox - fixlist.txt
FRST Fix NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system 1. Download the file from the link and save it to the Desktop. Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop). 2. Run FRST64 by Right-Clicking on the file and choosing Run as administrator. 3. Press the Fix button just once and wait. 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. 4. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply. Dropbox - fixlist.txt
T Traveler42 Contributor Joined Jul 16, 2017 Posts 57 Sep 1, 2017 #33 I ran it, the dialog came up that registry was corrupt and it restarted, I re-ran it and it said registry was corrupt and rebooted. Attached is the Fixlog.txt ==== Attachments 2017-09-01-Fixlog.zip 179.8 KB · Views: 2
I ran it, the dialog came up that registry was corrupt and it restarted, I re-ran it and it said registry was corrupt and rebooted. Attached is the Fixlog.txt ====
T Traveler42 Contributor Joined Jul 16, 2017 Posts 57 Sep 1, 2017 #34 I re-ran the FRST.exe a third time and finished. The new output is included below. A cycle of windows update still offered the three updates. === Attachments 2017-09-01-2-Fixlog.zip 342 KB · Views: 2
I re-ran the FRST.exe a third time and finished. The new output is included below. A cycle of windows update still offered the three updates. ===
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Sep 2, 2017 #35 FRST Registry Search 1. Click your Start button and type cmd. 2. Right-click on Command-Prompt that comes up and choose Run as administrator. 3. In the command-prompt window please copy and paste the following and then hit enter. reg load HKLM\COMPONENTS c:\windows\system32\config\COMPONENTS 4. If you see "The operation completed successfully." then you did it correctly and can move on. 5. Please download Farbar Recovery Scan Tool and save it to your Desktop. Note: You need to run the 64-bit Version so please ensure you download that one. 6. Run FRST64 by Right-Clicking on the file and choosing Run as administrator. 7. Copy and paste KB2919355 into the Search box and click the Search Registry button. 8. When the scan is complete a notepad window will open with the results. Please copy and paste the contents in your next reply. If for some reason notepad doesn't open the file should be saved on your desktop named Search.txt. 9. You may close any remaining open windows now.
FRST Registry Search 1. Click your Start button and type cmd. 2. Right-click on Command-Prompt that comes up and choose Run as administrator. 3. In the command-prompt window please copy and paste the following and then hit enter. reg load HKLM\COMPONENTS c:\windows\system32\config\COMPONENTS 4. If you see "The operation completed successfully." then you did it correctly and can move on. 5. Please download Farbar Recovery Scan Tool and save it to your Desktop. Note: You need to run the 64-bit Version so please ensure you download that one. 6. Run FRST64 by Right-Clicking on the file and choosing Run as administrator. 7. Copy and paste KB2919355 into the Search box and click the Search Registry button. 8. When the scan is complete a notepad window will open with the results. Please copy and paste the contents in your next reply. If for some reason notepad doesn't open the file should be saved on your desktop named Search.txt. 9. You may close any remaining open windows now.
T Traveler42 Contributor Joined Jul 16, 2017 Posts 57 Sep 3, 2017 #36 Ok, here is the output file of the current SearchReg === Attachments 2017-09-03-SearchReg.zip 121.6 KB · Views: 4
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Sep 3, 2017 #37 FRST Fix NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system 1. Download the attached file and save it to the Desktop. Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop). 2. Run FRST64 by Right-Clicking on the file and choosing Run as administrator. 3. Press the Fix button just once and wait. 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. 4. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply. Attachments fixlist.txt 1.7 KB · Views: 3
FRST Fix NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system 1. Download the attached file and save it to the Desktop. Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop). 2. Run FRST64 by Right-Clicking on the file and choosing Run as administrator. 3. Press the Fix button just once and wait. 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. 4. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
T Traveler42 Contributor Joined Jul 16, 2017 Posts 57 Sep 4, 2017 #38 Here is the output: ==== Fix result of Farbar Recovery Scan Tool (x64) Version: 20-08-2017 Ran by jim (04-09-2017 08:11:23) Run:4 Running from C:\Users\jim\Desktop Loaded Profiles: jim & cyg_server (Available Profiles: jim & cyg_server) Boot Mode: Normal ============================================== fixlist content: ***************** CreateRestorePoint: DeleteValue:HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\wdmaudio.inf_31bf3856ad364e35_6.3.9600.17031_5158ab61edf6f9a7|s!CBS_package_1364_for_kb2919355~31bf3856ad364e35~amd64~~6.3.1.14._cf3e6626872e134c DeleteValue:HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\wdmaudio.inf_31bf3856ad364e35_6.3.9600.17031_5158ab61edf6f9a7|i!CBS_package_1364_for_kb2919355~31bf3856ad364e35~amd64~~6.3.1.14._cf3e6626872e134c DeleteValue:HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\wdma_usb.inf_31bf3856ad364e35_6.3.9600.16490_5dc76c7e8add9f91|p!CBS_package_1364_for_kb2919355~31bf3856ad364e35~amd64~~6.3.1.14._cf3e6626b5b4e40b DeleteValue:HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\wdma_usb.inf_31bf3856ad364e35_6.3.9600.16490_5dc76c7e8add9f91|s!CBS_package_1364_for_kb2919355~31bf3856ad364e35~amd64~~6.3.1.14._cf3e6626b5b4e40b DeleteValue:HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\wdma_usb.inf_31bf3856ad364e35_6.3.9600.16490_5dc76c7e8add9f91|i!CBS_package_1364_for_kb2919355~31bf3856ad364e35~amd64~~6.3.1.14._cf3e6626b5b4e40b DeleteValue:HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\wvms_pp.inf_31bf3856ad364e35_6.3.9600.16475_53afc584c5506266|p!CBS_package_1083_for_kb2919355~31bf3856ad364e35~amd64~~6.3.1.14._ab1f2af4261d69ef DeleteValue:HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\wvms_pp.inf_31bf3856ad364e35_6.3.9600.16475_53afc584c5506266|s!CBS_package_1083_for_kb2919355~31bf3856ad364e35~amd64~~6.3.1.14._ab1f2af4261d69ef DeleteValue:HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\wvms_pp.inf_31bf3856ad364e35_6.3.9600.16475_53afc584c5506266|i!CBS_package_1083_for_kb2919355~31bf3856ad364e35~amd64~~6.3.1.14._ab1f2af4261d69ef ***************** Restore point was successfully created. HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\wdmaudio.inf_31bf3856ad364e35_6.3.9600.17031_5158ab61edf6f9a7\\s!CBS_package_1364_for_kb2919355~31bf3856ad364e35~amd64~~6.3.1.14._cf3e6626872e134c => value not found. HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\wdmaudio.inf_31bf3856ad364e35_6.3.9600.17031_5158ab61edf6f9a7\\i!CBS_package_1364_for_kb2919355~31bf3856ad364e35~amd64~~6.3.1.14._cf3e6626872e134c => value not found. HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\wdma_usb.inf_31bf3856ad364e35_6.3.9600.16490_5dc76c7e8add9f91\\p!CBS_package_1364_for_kb2919355~31bf3856ad364e35~amd64~~6.3.1.14._cf3e6626b5b4e40b => value not found. HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\wdma_usb.inf_31bf3856ad364e35_6.3.9600.16490_5dc76c7e8add9f91\\s!CBS_package_1364_for_kb2919355~31bf3856ad364e35~amd64~~6.3.1.14._cf3e6626b5b4e40b => value not found. HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\wdma_usb.inf_31bf3856ad364e35_6.3.9600.16490_5dc76c7e8add9f91\\i!CBS_package_1364_for_kb2919355~31bf3856ad364e35~amd64~~6.3.1.14._cf3e6626b5b4e40b => value not found. HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\wvms_pp.inf_31bf3856ad364e35_6.3.9600.16475_53afc584c5506266\\p!CBS_package_1083_for_kb2919355~31bf3856ad364e35~amd64~~6.3.1.14._ab1f2af4261d69ef => value not found. HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\wvms_pp.inf_31bf3856ad364e35_6.3.9600.16475_53afc584c5506266\\s!CBS_package_1083_for_kb2919355~31bf3856ad364e35~amd64~~6.3.1.14._ab1f2af4261d69ef => value not found. HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\wvms_pp.inf_31bf3856ad364e35_6.3.9600.16475_53afc584c5506266\\i!CBS_package_1083_for_kb2919355~31bf3856ad364e35~amd64~~6.3.1.14._ab1f2af4261d69ef => value not found. ==== End of Fixlog 08:11:33 ====
Here is the output: ==== Fix result of Farbar Recovery Scan Tool (x64) Version: 20-08-2017 Ran by jim (04-09-2017 08:11:23) Run:4 Running from C:\Users\jim\Desktop Loaded Profiles: jim & cyg_server (Available Profiles: jim & cyg_server) Boot Mode: Normal ============================================== fixlist content: ***************** CreateRestorePoint: DeleteValue:HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\wdmaudio.inf_31bf3856ad364e35_6.3.9600.17031_5158ab61edf6f9a7|s!CBS_package_1364_for_kb2919355~31bf3856ad364e35~amd64~~6.3.1.14._cf3e6626872e134c DeleteValue:HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\wdmaudio.inf_31bf3856ad364e35_6.3.9600.17031_5158ab61edf6f9a7|i!CBS_package_1364_for_kb2919355~31bf3856ad364e35~amd64~~6.3.1.14._cf3e6626872e134c DeleteValue:HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\wdma_usb.inf_31bf3856ad364e35_6.3.9600.16490_5dc76c7e8add9f91|p!CBS_package_1364_for_kb2919355~31bf3856ad364e35~amd64~~6.3.1.14._cf3e6626b5b4e40b DeleteValue:HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\wdma_usb.inf_31bf3856ad364e35_6.3.9600.16490_5dc76c7e8add9f91|s!CBS_package_1364_for_kb2919355~31bf3856ad364e35~amd64~~6.3.1.14._cf3e6626b5b4e40b DeleteValue:HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\wdma_usb.inf_31bf3856ad364e35_6.3.9600.16490_5dc76c7e8add9f91|i!CBS_package_1364_for_kb2919355~31bf3856ad364e35~amd64~~6.3.1.14._cf3e6626b5b4e40b DeleteValue:HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\wvms_pp.inf_31bf3856ad364e35_6.3.9600.16475_53afc584c5506266|p!CBS_package_1083_for_kb2919355~31bf3856ad364e35~amd64~~6.3.1.14._ab1f2af4261d69ef DeleteValue:HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\wvms_pp.inf_31bf3856ad364e35_6.3.9600.16475_53afc584c5506266|s!CBS_package_1083_for_kb2919355~31bf3856ad364e35~amd64~~6.3.1.14._ab1f2af4261d69ef DeleteValue:HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\wvms_pp.inf_31bf3856ad364e35_6.3.9600.16475_53afc584c5506266|i!CBS_package_1083_for_kb2919355~31bf3856ad364e35~amd64~~6.3.1.14._ab1f2af4261d69ef ***************** Restore point was successfully created. HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\wdmaudio.inf_31bf3856ad364e35_6.3.9600.17031_5158ab61edf6f9a7\\s!CBS_package_1364_for_kb2919355~31bf3856ad364e35~amd64~~6.3.1.14._cf3e6626872e134c => value not found. HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\wdmaudio.inf_31bf3856ad364e35_6.3.9600.17031_5158ab61edf6f9a7\\i!CBS_package_1364_for_kb2919355~31bf3856ad364e35~amd64~~6.3.1.14._cf3e6626872e134c => value not found. HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\wdma_usb.inf_31bf3856ad364e35_6.3.9600.16490_5dc76c7e8add9f91\\p!CBS_package_1364_for_kb2919355~31bf3856ad364e35~amd64~~6.3.1.14._cf3e6626b5b4e40b => value not found. HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\wdma_usb.inf_31bf3856ad364e35_6.3.9600.16490_5dc76c7e8add9f91\\s!CBS_package_1364_for_kb2919355~31bf3856ad364e35~amd64~~6.3.1.14._cf3e6626b5b4e40b => value not found. HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\wdma_usb.inf_31bf3856ad364e35_6.3.9600.16490_5dc76c7e8add9f91\\i!CBS_package_1364_for_kb2919355~31bf3856ad364e35~amd64~~6.3.1.14._cf3e6626b5b4e40b => value not found. HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\wvms_pp.inf_31bf3856ad364e35_6.3.9600.16475_53afc584c5506266\\p!CBS_package_1083_for_kb2919355~31bf3856ad364e35~amd64~~6.3.1.14._ab1f2af4261d69ef => value not found. HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\wvms_pp.inf_31bf3856ad364e35_6.3.9600.16475_53afc584c5506266\\s!CBS_package_1083_for_kb2919355~31bf3856ad364e35~amd64~~6.3.1.14._ab1f2af4261d69ef => value not found. HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\wvms_pp.inf_31bf3856ad364e35_6.3.9600.16475_53afc584c5506266\\i!CBS_package_1083_for_kb2919355~31bf3856ad364e35~amd64~~6.3.1.14._ab1f2af4261d69ef => value not found. ==== End of Fixlog 08:11:33 ====
T Traveler42 Contributor Joined Jul 16, 2017 Posts 57 Sep 4, 2017 #39 I re-ran the SearchReg and it gave identical results to the last time.
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Sep 4, 2017 #40 SFCFix Script Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own. Download SFCFix.exe (by niemiro) and save this to your Desktop. Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it. Save any open documents and close all open windows. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it. SFCFix will now process the script. Upon completion, a log should be created on your Desktop: SFCFix.txt. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse please - put tags around the log to break up the text. Attachments SFCFixScript.txt 2 KB · Views: 5
SFCFix Script Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own. Download SFCFix.exe (by niemiro) and save this to your Desktop. Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it. Save any open documents and close all open windows. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it. SFCFix will now process the script. Upon completion, a log should be created on your Desktop: SFCFix.txt. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse please - put tags around the log to break up the text.