[SOLVED] Win 8.1: amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634

colesdav · Dec 28, 2016

Hello can someone please help me with the following issue please?
I usually run the following PC Checks before and after I run Windows Update or change BIOS Settings or before I start working on my PC.

chkdsk
chkdsk /scan
sfc /scannow
Dism /Online /Cleanup-Image /CheckHealth
Dism /Online /Cleanup-Image /ScanHealth
Dism /Online /Cleanup-Image /RestoreHealth

Today I see the following issues reported.

Dism /Online /Cleanup-Image /CheckHealth = The component store is repairable.
Dism /Online /Cleanup-Image /ScanHealth = The component store is repairable.
Dism /Online /Cleanup-Image /RestoreHealth =

The restore operation failed. Either the repair source was not found or the component store cannot be repaired.

Error: 0x800f081f

DISM failed. No operation was performed.
For more information, review the log file.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

Looking at the CBS Log file I see the following:

Checking System Update Readiness.

(p) CSI Payload Corrupt amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbport.sys
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbport.inf
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbehci.sys
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbohci.sys
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbuhci.sys
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbhub.sys
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbd.sys
Repair failed: Missing replacement payload.

Summary:
Operation: Detect and Repair
Operation result: 0x0
Last Successful Step: Entire operation completes.
Total Detected Corruption: 7
CBS Manifest Corruption: 0
CBS Metadata Corruption: 0
CSI Manifest Corruption: 0
CSI Metadata Corruption: 0
CSI Payload Corruption: 7
Total Repaired Corruption: 0
CBS Manifest Repaired: 0
CSI Manifest Repaired: 0
CSI Payload Repaired: 0
CSI Store Metadata refreshed: True

Total Operation Time: 594 seconds.

More information to follow.

colesdav · Dec 28, 2016

My System is Windows 8.1 Pro 64 Bit on Z87 Motherboard with i7-4770K.

I have tried the following methods in an attempt to repair the DISM issue.

(1). DISM /Source pointing to Windows 7 Ultimate / Windows 8.0 Upgrade /Windows 8.1 ISO to look for the files specified in the missing amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634 directory.
Looking at the contents of all of these disks, the amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634 are not on the original Windows 7 64bit Ultimate/Windows 8.0 Pro / Windows 8.1 ISO download disks.

(2). Looking on the web I thought the missing/corrupted amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634 directory had something to do with Microsoft Update Patch KB2962409. I tried to uninstall and reinstall the patch. It would not uninstall.

(3). I have another Windows 8.1 Pro PC with Z97 Motherboard and i7-4790K. It passes all of the PC Checks fine. It has a amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634 directory. I tired a method where i run takedown command on the files in the corrupted amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634 on my Z87 machine, then change my permissions to admin, then copy the amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634 files from my Z97 pc directory to my corrupted amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634 Z87 pc directory.
I then rebooted the Z87 machine and reran the PC checks. Ther DISM checks all fail in the same way as before.

colesdav · Dec 28, 2016

So in summary, I am now out of ideas.
My PC has passed all of these checks in the past. I run these checks regularly.
I do not know why DISM is now complaining about the amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634 directory files as corrupted.
I did have an AMD Relive Driver dysfunction during game testing (PC Freeze) but the driver reset itself once I reset my PC. In any case I completely uninstalled the AMD Relive driver and
I went back to AMD Radeon Software Version 16.11.5. which previously checked out fine. Perhaps something got corrupted during the video Driver crash but I am not sure.

I have also checked all of my USB Drivers on my Z87 machine and tried to update them in Device Manager. They all report to be running o.k. and on the latest and correct driver version. Everything seems to be working o.k.
I also checked my Asus Z87 Motherboard Drivers Disk for the amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634 files. They are not there.

Can someone please tell me the following?

(1). What exactly is the amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634 directory and what does it relate to?

(2). The amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634 directory must have got onto my PC's from somewhere, since they are not on any of the original installation or motherboard disks they must they be from a Microsoft Update?

In the spirit of Christmas, please help me out. I use these PC's for work, and this is stopping me from proceeding with programming.
I have tried to work out this issue myself over the past few days but I am completely stuck now.
Thanks

colesdav · Dec 28, 2016

I forgot to mention I have also tried running the following sequence:

DISM/Online /Cleanup-Image /AnalyzeComponentStore
Dism /online /Cleanup-Image /StartComponentCleanup
Dism /Online /Cleanup-Image /RestoreHealth

No luck.
Cheers.

colesdav · Dec 28, 2016

SFC Fix does not find any corruption.

SFCFix version 3.0.0.0 by niemiro.
Start time: 2016-12-28 18:24:59.147
Microsoft Windows 8.1 Update 3 - amd64
Not using a script file.

AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.

Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2016-12-28 18:26:16.261
----------------------EOF-----------------------

colesdav · Dec 28, 2016

SFC Fix does not find any corruption.

SFCFix version 3.0.0.0 by niemiro.
Start time: 2016-12-28 18:24:59.147
Microsoft Windows 8.1 Update 3 - amd64
Not using a script file.

AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.

Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2016-12-28 18:26:16.261
----------------------EOF-----------------------

colesdav · Dec 28, 2016

The takedown, change permissions and copy method I used is described here:

https://support.microsoft.com/en-us/kb/929833

BrianDrab · Dec 28, 2016

(2). Looking on the web I thought the missing/corrupted amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634 directory had something to do with Microsoft Update Patch KB2962409. I tried to uninstall and reinstall the patch. It would not uninstall.

Correct. That's the update where the directory came from.

In the spirit of Christmas, please help me out. I use these PC's for work, and this is stopping me from proceeding with programming.

This should not prevent you from proceeding with any programming.

The following should get you fixed up.

Step#1 - 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. If you still have this on your desktop from downloading previously, you don't need to re-download.
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

colesdav · Dec 29, 2016

Hello,

First of all I would like to say thank you for replying.

I downloaded and ran the SFCFix file you requested.
Here is the SFC.txt output below:

SFCFix version 3.0.0.0 by niemiro.
Start time: 2016-12-29 11:01:55.971
Microsoft Windows 8.1 Update 3 - amd64
Using .zip script file at C:\Users\Colin\Desktop\SFCFix.zip [0]

PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\Winsxs\amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbd.sys
Successfully took permissions for file or folder C:\WINDOWS\Winsxs\amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbehci.sys
Successfully took permissions for file or folder C:\WINDOWS\Winsxs\amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbhub.sys
Successfully took permissions for file or folder C:\WINDOWS\Winsxs\amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbohci.sys
Successfully took permissions for file or folder C:\WINDOWS\Winsxs\amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbport.inf
Successfully took permissions for file or folder C:\WINDOWS\Winsxs\amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634
Successfully took permissions for file or folder C:\WINDOWS\Winsxs\amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbuhci.sys

Successfully copied file C:\Users\Admin\AppData\Local\niemiro\Archive\Winsxs\amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbd.sys to C:\WINDOWS\Winsxs\amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbd.sys.
Successfully copied file C:\Users\Admin\AppData\Local\niemiro\Archive\Winsxs\amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbehci.sys to C:\WINDOWS\Winsxs\amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbehci.sys.
Successfully copied file C:\Users\Admin\AppData\Local\niemiro\Archive\Winsxs\amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbhub.sys to C:\WINDOWS\Winsxs\amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbhub.sys.
Successfully copied file C:\Users\Admin\AppData\Local\niemiro\Archive\Winsxs\amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbohci.sys to C:\WINDOWS\Winsxs\amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbohci.sys.
Successfully copied file C:\Users\Admin\AppData\Local\niemiro\Archive\Winsxs\amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbport.inf to C:\WINDOWS\Winsxs\amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbport.inf.
Successfully copied file C:\Users\Admin\AppData\Local\niemiro\Archive\Winsxs\amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbport.sys to C:\WINDOWS\Winsxs\amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbport.sys.
Successfully copied file C:\Users\Admin\AppData\Local\niemiro\Archive\Winsxs\amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbuhci.sys to C:\WINDOWS\Winsxs\amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbuhci.sys.

Successfully restored ownership for C:\WINDOWS\Winsxs\amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbd.sys
Successfully restored permissions on C:\WINDOWS\Winsxs\amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbd.sys
Successfully restored ownership for C:\WINDOWS\Winsxs\amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbehci.sys
Successfully restored permissions on C:\WINDOWS\Winsxs\amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbehci.sys
Successfully restored ownership for C:\WINDOWS\Winsxs\amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbhub.sys
Successfully restored permissions on C:\WINDOWS\Winsxs\amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbhub.sys
Successfully restored ownership for C:\WINDOWS\Winsxs\amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbohci.sys
Successfully restored permissions on C:\WINDOWS\Winsxs\amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbohci.sys
Successfully restored ownership for C:\WINDOWS\Winsxs\amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbport.inf
Successfully restored permissions on C:\WINDOWS\Winsxs\amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbport.inf
Successfully restored ownership for C:\WINDOWS\Winsxs\amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634
Successfully restored permissions on C:\WINDOWS\Winsxs\amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634
Successfully restored ownership for C:\WINDOWS\Winsxs\amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbuhci.sys
Successfully restored permissions on C:\WINDOWS\Winsxs\amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbuhci.sys
PowerCopy:: directive completed successfully.

Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 9 datablocks.
Finish time: 2016-12-29 11:01:56.690
Script hash: 0wQR35EIXdkzepM/eIdofAG9UHeKWcghtDlqWPDKqw4=
----------------------EOF-----------------------

colesdav · Dec 29, 2016

Here is the brief result of running the PC Checks again.

As you will see DISM operations still report corruption, even after running the SFC script above.
Again any ideas why this is happening I would be grateful for help.

C:\WINDOWS\system32>chkdsk
Windows has scanned the file system and found no problems.
No further action is required.

C:\WINDOWS\system32>chkdsk /scan
Windows has scanned the file system and found no problems.
No further action is required.

C:\WINDOWS\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\WINDOWS\system32>Dism /Online /Cleanup-Image /CheckHealth

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image Version: 6.3.9600.17031

The component store is repairable.
The operation completed successfully.

C:\WINDOWS\system32>Dism /Online /Cleanup-Image /ScanHealth

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image Version: 6.3.9600.17031

[==========================100.0%==========================]
The component store is repairable.
The operation completed successfully.

C:\WINDOWS\system32>
C:\WINDOWS\system32>Dism /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image Version: 6.3.9600.17031

[==========================100.0%==========================]
The restore operation failed. Either the repair source was not found or the component store cannot be repaired.

Error: 0x800f081f

DISM failed. No operation was performed.
For more information, review the log file.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

C:\WINDOWS\system32>

colesdav · Dec 29, 2016

DISM.log summary.
DISM still sees the corruption during detect, and is unable to repair, I will try to use your AMD_... directory as a repair source location.

=================================
Checking System Update Readiness.

(p) CSI Payload Corrupt amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbport.sys
(p) CSI Payload Corrupt amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbport.inf
(p) CSI Payload Corrupt amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbehci.sys
(p) CSI Payload Corrupt amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbohci.sys
(p) CSI Payload Corrupt amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbuhci.sys
(p) CSI Payload Corrupt amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbhub.sys
(p) CSI Payload Corrupt amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbd.sys

Summary:
Operation: Detect only
Operation result: 0x0
Last Successful Step: CSI store detection completes.
Total Detected Corruption: 7
CBS Manifest Corruption: 0
CBS Metadata Corruption: 0
CSI Manifest Corruption: 0
CSI Metadata Corruption: 0
CSI Payload Corruption: 7
Total Repaired Corruption: 0
CBS Manifest Repaired: 0
CSI Manifest Repaired: 0
CSI Payload Repaired: 0
CSI Store Metadata refreshed: True

Total Operation Time: 252 seconds.
Checking System Update Readiness.

(p) CSI Payload Corrupt amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbport.sys
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbport.inf
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbehci.sys
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbohci.sys
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbuhci.sys
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbhub.sys
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbd.sys
Repair failed: Missing replacement payload.

Summary:
Operation: Detect and Repair
Operation result: 0x0
Last Successful Step: Entire operation completes.
Total Detected Corruption: 7
CBS Manifest Corruption: 0
CBS Metadata Corruption: 0
CSI Manifest Corruption: 0
CSI Metadata Corruption: 0
CSI Payload Corruption: 7
Total Repaired Corruption: 0
CBS Manifest Repaired: 0
CSI Manifest Repaired: 0
CSI Payload Repaired: 0
CSI Store Metadata refreshed: True

Total Operation Time: 576 seconds.

BrianDrab · Dec 29, 2016

Can I please take a look at your entire c:\windows\logs\CBS.log file? Zip and attach. Thanks.

colesdav · Dec 29, 2016

I rebooted the machine, logged in as admin and reran the checks.
The file is called FeedbackSysnative.zip.
It was compressed with 7-zip just in case you have issues with decompress, try changing extension from .zip to .7z.
Thanks again for your help.

BrianDrab · Dec 29, 2016

Thanks. Please do the following.

Step#1 - 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. If you still have this on your desktop from downloading previously, you don't need to re-download.
Download the file below, SFCScript.txt, and save this to your Desktop.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCScript.txt.
Drag the file SFCScript.txt 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

colesdav · Dec 29, 2016

SFCFix version 3.0.0.0 by niemiro.
Start time: 2016-12-29 17:20:46.034
Microsoft Windows 8.1 Update 3 - amd64
Using .txt script file at C:\Users\Admin\Desktop\SFCScript.txt [1]

FileScan::
[0: 1] C:\Windows\WinSxS\amd64_usbport.inf_31bf3856ad364e35_6.3.9600.16384_none_ae80bf7dd784a7ca\usbport.sys
File is untraceable.
Found: Xw2u5xqWJig0dZyJfT7m+VKXhBipf0GzXkl9mmouDjY=
Found: 6.3.9600.16384
Trace not available.

[1: 1] C:\Windows\WinSxS\amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17238_none_aebab793d7589deb\usbport.sys
File is untraceable.
Found: M5knUbqcnoY2sdLr9pl6PIRhUfsldxFgU3nMOGA6gAw=
Version number not available.
Trace not available.

[2: 1] C:\Windows\WinSxS\amd64_usbport.inf_31bf3856ad364e35_6.3.9600.18088_none_ae848d63d78148f3\usbport.sys
File is untraceable.
Found: HOuITsKR+B5vI+DuLxaf+2wQv4D9+NDD2zqc6pw536E=
Version number not available.
Trace not available.

[3: 1] C:\Windows\WinSxS\amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17195_none_ae76d547d78bfc65\usbport.sys
File is untraceable.
Found: 9JYFPQ4YTU/BWwYV/L7r8UdK3xVBRPZ2J+AV95VmkQQ=
Found: 6.3.9600.17195
Trace not available.

[4: 3] C:\Windows\System32\drivers\usbport.sys
File is untraceable.
Found: OSImOxc63hbt3HL3MtZBSyl37aLBCb5rtzo98Ac3W38=
Found: 6.3.9600.18088
Trace not available.

[C:\Windows\System32\DriverStore\FileRepository\usbport.inf_amd64_38e8e500c4e5d5f3\usbport.sys]
[C:\Windows\WinSxS\amd64_usbport.inf_31bf3856ad364e35_6.3.9600.18191_none_ae72bd57d78fb0aa\usbport.sys]

[5: 1] C:\Windows\WinSxS\amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbport.sys
File is untraceable.
Found: VhH69EWUnodvQGy0GK4+48Vbpzoq6IhOM2mtB5uMy74=
Version number not available.
Trace not available.

[6: 1] C:\Users\xxxxx\Desktop\SFCFix\Winsxs\amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbport.sys
File is untraceable.
Found: VhH69EWUnodvQGy0GK4+48Vbpzoq6IhOM2mtB5uMy74=
Version number not available.
Trace not available.

[7: 1] C:\SFCFix\Backups\C\WINDOWS\winsxs\amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbport.sys
File is untraceable.
Found: VhH69EWUnodvQGy0GK4+48Vbpzoq6IhOM2mtB5uMy74=
Version number not available.
Trace not available.

[8: 1] C:\Users\Admin\Desktop\New folder (5)\SFCFix\Winsxs\amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634\usbport.sys
File is untraceable.
Found: VhH69EWUnodvQGy0GK4+48Vbpzoq6IhOM2mtB5uMy74=
Version number not available.
Trace not available.
FileScan:: directive completed successfully.

Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 10 datablocks.
Finish time: 2016-12-29 17:20:53.907
Script hash: TLGdlu/1921twg5mOt9VIQ/nduyUMSldMtoE6gk9z0I=
----------------------EOF-----------------------

BrianDrab · Dec 29, 2016

This looks good. As a result I need to take a look at your hives. Please do the following.

Retrieve Components/Software Hives
Note: The Software have has confidential and sensitive information in it so please send me a PM with a link to that particular hive so it's not in the public form.

Please download the Freeware RegBak from here: Acelogix Software - Download products
You will find it at the bottom of the page that the link brings you to.
Go ahead and install this program and accept all the defaults. After the last install screen the program should open.
Click the New Backup button. Accept the defaults and simply click Start.
When it says Finished successfully, click the Close button.
This will bring you back to the main screen of the program. You will see one entry in this list with the date that you did it. Right-click on this line-item and select Explore Backup...
This will bring you into the folder where the backup was made. You should see a Users folder and a Windows folder along with a couple other files. Double-click on the Windows folder to open it. Then open the System32 folder and then config folder. You should see around 6 files in here, two of which are named COMPONENTS and SOFTWARE.
Copy these two files to your Desktop. If the COMPONENTS file does not exist, please fetch it instead from C:\Windows\System32\config\COMPONENTS.
Now right click on these files on your desktop and select Send to > Compressed (zipped) folder.
Then please upload the zip file(s) to your favourite file sharing website (it will be too big to upload here). Examples of services to upload to are Dropbox or One Drive or SendSpace and then just provide the link in your reply.
You can close any open windows you have as well as the RegBack program now.

colesdav · Jan 2, 2017

Hello,

Thanks again for all of your help with this.

I downloaded RegBak from Acelogix and generated the data you requested above.

Sorry but I cannot send out any confidential data from this machine to anyone.

I am guessing you think there may be a corrupted / missing / broken/ incorrect Registry Key that may be causing this issue.
If you do have an idea or hint on what to look for then I can look into that myself.
Otherwise please close this thread.

I have decided to simply reinstall Windows 8.1 64bit on another Hard Drive and move on. I have spent too much time trying to fix this issue.
I will also contact MicroSoft to report this issue, as DISM should fix this issue automatically in my opinion.

BrianDrab · Jan 2, 2017

I suspect something is incorrect in the registry but I really don't know what without analyzing the hives. I understand your policy and will close the thread. Sorry I couldn't help you further.

colesdav · Feb 1, 2017

BrianDrab said:
I suspect something is incorrect in the registry but I really don't know what without analyzing the hives. I understand your policy and will close the thread. Sorry I couldn't help you further.

Hello,

Absolutely no need to apologize. I really do appreciate your help. Thank you again.

I have an update to the issue. It looks like it is now fixed.

I ran the same commands as below that I have been running every day for the past month at PC start up:

chkdsk ---> OK.
chkdsk /scan ---> OK.
sfc /scannow ---> OK.
Dism /Online /Cleanup-Image /CheckHealth ---> Repairable.
Dism /Online /Cleanup-Image /ScanHealth ---> Repairable.

Dism /Online /Cleanup-Image /RestoreHealth --->Unable to fix.

Dism /Online /Cleanup-Image /AnalyzeComponentStore ---> Needs Clean up.
Dism /online /Cleanup-Image /StartComponentCleanup ---> Cleaned up.
sfc /scannow ---> OK.
DISM/Online /Cleanup-Image /AnalyzeComponentStore ---> Needs Clean up.
Dism /online /Cleanup-Image /StartComponentCleanup ---> Cleaned up.
Dism /Online /Cleanup-Image /CheckHealth ---> Repairable.
Dism /Online /Cleanup-Image /ScanHealth ---> Repairable.

Dism /Online /Cleanup-Image /RestoreHealth --->Repaired.

chkdsk ---> OK.
chkdsk /scan ---> OK.
sfc /scannow ---> OK.
Dism /Online /Cleanup-Image /CheckHealth ---> OK.
Dism /Online /Cleanup-Image /ScanHealth ---> OK.

I do not know why this issue was fixed for sure.

I can only assume something changed at the Microsoft end with the DISM commands to fix this.

I have also been running Weekly Windows Updates and a number of Disk Cleanup operations over the weeks
that this issue has been a problem. I have also done a number of AMD Radeon Crimson GPU Driver installation and removals.
Each time I run the amdcleanup utility as well.
The above is normal computer use for me.
Nothing unusual has been done otherwise.

I will report if the problem reappears.

Here is my full update on the Microsoft Community Website.
I did have some online chat support from Microsoft so maybe that feedback (and others) got back to Microsoft and maybe they fixed DISM.
Win 8.1: - Microsoft Community

Thanks again.

BrianDrab · Feb 1, 2017

Thanks for the reply and information!

[SOLVED] Win 8.1: amd64_usbport.inf_31bf3856ad364e35_6.3.9600.17116_none_aece54f1d74a3634

Member

Member

Member

Member

Member

Member

Member

Emeritus

Attachments

Member

Member

Member

Emeritus

Member

Attachments

Emeritus

Attachments

Member

Emeritus

Member

Emeritus

Member

Emeritus