Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Is my usb hub failing and causing issues with my hard drives?

external hard drive usb hub windows 10 windows 10 pro hard drive hdd Error 0X800701B1 failure copy error

  • Please log in to reply

#1
leader 2

leader 2

    Member

  • Member
  • PipPip
  • 48 posts

Hi. I appreciate any help anyone here can give in advance. I am not technical so please use laymens terms when replying. Thanks for your understanding. :)

 

I have 2 WD Elements 8tb external hdds. They were both plugged into a 3 year old Inland brand usb hub I bought from Microcenter which has an ac adapter and doesn't just plug into the computer.

 

Yesterday I tried to copy all of my files (over 6tb) from my main WD Elements drive to my backup one. I've done this before with no issues. It was copying normally until I got this error today: 

 

ERROR 0X800701B1 A DEVICE WHICH DOES NOT EXIST WAS SPECIFIED 

 

The main drive then gave a F: is not accessible error after I cancelled the copying. It wasn't detected by free file sync either to complete the copy process and gave the same error in that program.

 

I googled that error and at this link (https://bit.ly/3hcdVQe) the next to last reply from  glslive there mentioned hdd's giving those errors if not being plugged into an ac powered usb hub. I plugged both hdds directly into my computer and the F drive was detected and is now copying normally via Free File sync. 

 

Can anyone tell me if maybe the usb hub is failing and that caused the error with the F drive copying? How would I test for that? I haven't had issues with flash drives being detected/giving errors in all 3 yrs I've owned that hub either. My hub is ac powered like glslive mentioned at that microsoft forum above so I didn't think that was an issue.

 

Or is it a problem with the drive itself? The last time I had drives give that inaccessible error both failed completely soon after that. The drive gave that error before in this thread (https://bit.ly/2XQq4my) and the issue appeared to have been resolved, but now I'm starting to wonder if that drive is really giving out completely if it's not the usb hub causing the error. 


  • 0

Advertisements


#2
RKinner

RKinner

    Malware Expert

  • Expert
  • 23,013 posts
  • MVP

It sounds like the hub but let's look at your drives:

 

Get the free version of Speccy:

http://www.filehippo...ownload_speccy/ 

(Look in the upper right for the Download
Latest Version button  - Do NOT press the large Start Download button on the upper left!)  
Download, Save and Install it.  Tell it you do not need CCLEANER.    Run Speccy.  When it finishes (the little icon in the bottom left will stop moving),
File, Save as Text File,  (to your desktop) note the name it gives. OK.  Open the file in notepad and delete the line that gives the serial number of your Operating System.  
(It will be near the top,  10-20  lines down.) Save the file.  Attach the file to your next post.  Attaching the log is the best option as it is too big for the forum.  Attaching is a multi step process.

First click on More Reply Options
Then scroll down to where you see
Choose File and click on it.  Point it at the file and hit Open.
Now click on Attach this file.

 


  • 0

#3
leader 2

leader 2

    Member

  • Topic Starter
  • Member
  • PipPip
  • 48 posts

Thanks for your help. Here is my log file.

Attached Files


Edited by leader 2, 12 June 2020 - 11:09 AM.

  • 0

#4
RKinner

RKinner

    Malware Expert

  • Expert
  • 23,013 posts
  • MVP

If you look at the S.M.A.R.T. values for each drive in Speccy you will see something very odd.  Each drive has

the same values:

Attribute name    Spin-Up Time
                                          Real value    12452035 ms

...

Attribute name    Head Stability
                                            Real value    65,535
   ...                                      
                                   
 Attribute name    Reported Uncorrectable Errors
                                            Real value    65,536
 ...                                                          

Attribute name    Command Timeout
                                            Real value    70,911,667
                                            

I can't believe that all drives have exactly the same values so I feel pretty certain your USB  Hub is not working correctly.  You could verify this by connecting a drive directly to the PC and rerunning Speccy and see if it still give identical readings.


  • 0

#5
leader 2

leader 2

    Member

  • Topic Starter
  • Member
  • PipPip
  • 48 posts

But the drives are all currently connected to the computer right now and when I first ran speccy. After the issue with the drive occurred in my topic starter post, I connected the drives to the computer USB ports thinking that maybe that might help the problem. They aren't currently connected to the USB hub. Is there something else I need to try?


  • 0

#6
RKinner

RKinner

    Malware Expert

  • Expert
  • 23,013 posts
  • MVP

Perhaps Speccy has a bug.  Let's get a second opinion.

 

See if you can get Speedfan to work:

http://www.filehippo...nload_speedfan/

Download, save and Install it (Win 7 or Vista right click and Run As Admin.) then run it (Win 7 or Vista right click and Run As Admin.).

It will tell you your temps.  If they seem hot (over 50) then check Automatic Fan Speed.
Leave it running and see if the temps drop. What it does on a laptop if it works is turn the fan on full which seems to help.

click on the S.M.A.R.T. tab.  Click on the down arrow to the right of the Hard Disk box.  Select your hard drive.  Click on Perform an In-depth Online Analysis of this hard disk.  Your browser will open.

At the bottom of the new page will be a line:  

The link to get back and see a new report about this hard disk in the future is this.

Right click on the underlined "this" and select Copy Link Address.  Move to a Reply and Paste (Ctrl + v).

 

Repeat for several different drives so we can compare to what Speccy claims it sees.

 


 


  • 0

#7
leader 2

leader 2

    Member

  • Topic Starter
  • Member
  • PipPip
  • 48 posts

I tried the speedfan. Here are my links.

 

http://www.hddstatus...cation=1EBB4FE9

 

http://www.hddstatus...cation=E75CCF8C

 

http://www.hddstatus...cation=7030FE44

 

http://www.hddstatus...cation=101FE0E6

 

I have an 8tb Seagate external hard drive and tried to Perform an In-depth Online Analysis of this hard disk. It showed no data. Does that mean there is a problem with that drive or does Speedfan only work with Hitachi and Western Digital?


  • 0

#8
RKinner

RKinner

    Malware Expert

  • Expert
  • 23,013 posts
  • MVP

Speedfan usually works with Seagate.  Also the WD30NMZW drive only showed 3 attributes so something is wrong there.  I checked against my PC and Western Digital drives do not have the attribute: Command Timeout so something is getting confused. 

 

Open an elevated command prompt:

http://www.howtogeek...-in-windows-10/

(If you open an elevated Command Prompt properly it will say Administrator: Command Prompt in the margin at the top of the window)


Once you have an elevated command prompt:

Type:

 DISM  /Online  /Cleanup-Image  /RestoreHealth

 


 (I use two spaces so you can be sure to see where one space goes.)
Hit Enter.  This will take a while (10-20 minutes) to complete.  Once the prompt returns:

Reboot.  Open an elevated Command Prompt again and type (with an Enter after the line):
 

sfc  /scannow

 




This will also take a few minutes.  

When it finishes it will say one of the following:

Windows did not find any integrity violations (a good thing)
Windows Resource Protection found corrupt files and repaired them (a good thing)
Windows Resource Protection found corrupt files but was unable to fix some (or all) of them (not a good thing)

If you get the last result then type:

findstr  /c:"[SR]"  \windows\logs\cbs\cbs.log  >  %UserProfile%\desktop\junk.txt

 



Hit Enter.  Then type::

 

notepad %UserProfile%\desktop\junk.txt

 


Hit Enter.

 Copy the text from notepad and paste it into a reply.


After you finish SFC, regardless of the result:



1. Please download the Event Viewer Tool by Vino Rosso
http://images.malwar...om/vino/VEW.exe
and save it to your Desktop:
2. Right-click VEW.exe and Run AS Administrator
3. Under 'Select log to query', select:

* System
4. Under 'Select type to list', select:
* Error
* Warning


Then use the 'Number of events' as follows:


1. Click the radio button for 'Number of events'
Type 20 in the 1 to 20 box
Then click the Run button.
Notepad will open with the output log.


Please post the Output log in your next reply then repeat but select Application.  (Each time you run VEW it overwrites the log so copy the first one to a Reply or rename it before running it a second time.)


 


  • 0

#9
leader 2

leader 2

    Member

  • Topic Starter
  • Member
  • PipPip
  • 48 posts

Here's my output log from VEW. Just for my future reference Speedfan still won't show data for my Seagate Drive. Are you sure that's normal? When I click Perform an In-depth Online Analysis of this hard disk for the Seagate 8tb all it shows is a blank box like in this image. https://ibb.co/hR6FP7C

 

Why would it show data for the Western Digital and Hitachi drives, but not the seagate drive? Do you know why this is and if that is a bad sign?

 

Vino's Event Viewer v01c run on Windows 7 in English
Report run at 13/06/2020 11:35:55 AM
 
Note: All dates below are in the format dd/mm/yyyy
 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 13/06/2020 3:33:16 PM
Type: Error Category: 0
Event: 10000 Source: Microsoft-Windows-DistributedCOM
Unable to start a DCOM Server: {94269C4E-071A-4116-90E6-52E557067E4E}. The error: "2147942593" Happened while starting this command: C:\Users\HP CMT\AppData\Local\Microsoft\OneDrive\19.232.1124.0005\FileCoAuth.exe -Embedding
 
Log: 'System' Date/Time: 13/06/2020 3:01:49 PM
Type: Error Category: 0
Event: 7022 Source: Service Control Manager
The System Guard Runtime Monitor Broker service hung on starting.
 
Log: 'System' Date/Time: 13/06/2020 2:59:38 PM
Type: Error Category: 0
Event: 7022 Source: Service Control Manager
The Downloaded Maps Manager service hung on starting.
 
Log: 'System' Date/Time: 13/06/2020 2:56:29 PM
Type: Error Category: 0
Event: 12 Source: VBoxNetLwf
The driver detected an internal driver error on \Device\VBoxNetLwf.
 
Log: 'System' Date/Time: 13/06/2020 2:54:43 PM
Type: Error Category: 0
Event: 12 Source: VBoxNetLwf
The driver detected an internal driver error on \Device\VBoxNetLwf.
 
Log: 'System' Date/Time: 13/06/2020 2:54:26 PM
Type: Error Category: 0
Event: 12 Source: VBoxNetLwf
The driver detected an internal driver error on \Device\VBoxNetLwf.
 
Log: 'System' Date/Time: 13/06/2020 7:42:28 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 13/06/2020 7:42:28 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 13/06/2020 7:42:28 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 13/06/2020 7:42:28 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 13/06/2020 7:42:28 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 13/06/2020 7:42:28 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 13/06/2020 7:42:28 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 13/06/2020 7:42:28 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 13/06/2020 7:42:28 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 13/06/2020 7:42:28 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 13/06/2020 7:42:28 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 13/06/2020 7:42:28 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 13/06/2020 7:42:28 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 13/06/2020 7:42:28 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 13/06/2020 3:25:02 PM
Type: Warning Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}  and APPID  {15C20B67-12E7-4BB6-92BB-7AFF07997402}  to the user DESKTOP-N7QQU6I\123 SID (S-1-5-21-1727030935-3764560176-2632440269-1005) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
 
Log: 'System' Date/Time: 13/06/2020 3:11:24 PM
Type: Warning Category: 0
Event: 8021 Source: BROWSER
The browser service was unable to retrieve a list of servers from the browser master \\HP on the network \Device\NetBT_Tcpip_{9681A6A0-6529-4F09-BAA1-896AB4A31F4E}.    Browser master: \\HP  Network: \Device\NetBT_Tcpip_{9681A6A0-6529-4F09-BAA1-896AB4A31F4E}    This event may be caused by a temporary loss of network connectivity. If this message appears again, verify that the server is still connected to the network. The return code is in the Data text box.
 
Log: 'System' Date/Time: 13/06/2020 3:00:59 PM
Type: Warning Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID  Windows.SecurityCenter.SecurityAppBroker  and APPID  Unavailable  to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
 
Log: 'System' Date/Time: 13/06/2020 3:00:59 PM
Type: Warning Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID  Windows.SecurityCenter.WscBrokerManager  and APPID  Unavailable  to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
 
Log: 'System' Date/Time: 13/06/2020 3:00:05 PM
Type: Warning Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}  and APPID  {15C20B67-12E7-4BB6-92BB-7AFF07997402}  to the user DESKTOP-N7QQU6I\HP CMT SID (S-1-5-21-1727030935-3764560176-2632440269-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
 
Log: 'System' Date/Time: 13/06/2020 2:59:50 PM
Type: Warning Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}  and APPID  {15C20B67-12E7-4BB6-92BB-7AFF07997402}  to the user DESKTOP-N7QQU6I\HP CMT SID (S-1-5-21-1727030935-3764560176-2632440269-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
 
Log: 'System' Date/Time: 13/06/2020 2:59:48 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name upeer.me timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 13/06/2020 2:54:14 PM
Type: Warning Category: 0
Event: 11 Source: Microsoft-Windows-Wininit
Custom dynamic link libraries are being loaded for every application. The system administrator should review the list of libraries to ensure they are related to trusted applications. Please visit http://support.microsoft.com/kb/197571for more information.
 
Log: 'System' Date/Time: 13/06/2020 2:53:08 PM
Type: Warning Category: 0
Event: 27 Source: e1cexpress
Intel® 82579LM Gigabit Network Connection  Network link is disconnected. 
 
Log: 'System' Date/Time: 13/06/2020 2:09:08 PM
Type: Warning Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}  and APPID  {15C20B67-12E7-4BB6-92BB-7AFF07997402}  to the user DESKTOP-N7QQU6I\HP CMT SID (S-1-5-21-1727030935-3764560176-2632440269-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
 
Log: 'System' Date/Time: 13/06/2020 2:09:08 PM
Type: Warning Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}  and APPID  {15C20B67-12E7-4BB6-92BB-7AFF07997402}  to the user DESKTOP-N7QQU6I\HP CMT SID (S-1-5-21-1727030935-3764560176-2632440269-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
 
Log: 'System' Date/Time: 13/06/2020 2:06:03 PM
Type: Warning Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID  {C2F03A33-21F5-47FA-B4BB-156362A2F239}  and APPID  {316CDED5-E4AE-4B15-9113-7055D84DCC97}  to the user DESKTOP-N7QQU6I\HP CMT SID (S-1-5-21-1727030935-3764560176-2632440269-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ShellExperienceHost_10.0.18362.449_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-155514346-2573954481-755741238-1654018636-1233331829-3075935687-2861478708). This security permission can be modified using the Component Services administrative tool.
 
Log: 'System' Date/Time: 13/06/2020 1:26:33 PM
Type: Warning Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}  and APPID  {15C20B67-12E7-4BB6-92BB-7AFF07997402}  to the user DESKTOP-N7QQU6I\HP 8200 SID (S-1-5-21-1727030935-3764560176-2632440269-1006) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
 
Log: 'System' Date/Time: 13/06/2020 1:26:33 PM
Type: Warning Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}  and APPID  {15C20B67-12E7-4BB6-92BB-7AFF07997402}  to the user DESKTOP-N7QQU6I\HP 8200 SID (S-1-5-21-1727030935-3764560176-2632440269-1006) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
 
Log: 'System' Date/Time: 13/06/2020 1:03:50 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name tracker.ilibr.org timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 13/06/2020 12:52:50 PM
Type: Warning Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}  and APPID  {15C20B67-12E7-4BB6-92BB-7AFF07997402}  to the user DESKTOP-N7QQU6I\HP 8200 SID (S-1-5-21-1727030935-3764560176-2632440269-1006) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
 
Log: 'System' Date/Time: 13/06/2020 12:52:50 PM
Type: Warning Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}  and APPID  {15C20B67-12E7-4BB6-92BB-7AFF07997402}  to the user DESKTOP-N7QQU6I\HP 8200 SID (S-1-5-21-1727030935-3764560176-2632440269-1006) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
 
Log: 'System' Date/Time: 13/06/2020 11:31:52 AM
Type: Warning Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID  {C2F03A33-21F5-47FA-B4BB-156362A2F239}  and APPID  {316CDED5-E4AE-4B15-9113-7055D84DCC97}  to the user DESKTOP-N7QQU6I\HP CMT SID (S-1-5-21-1727030935-3764560176-2632440269-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ShellExperienceHost_10.0.18362.449_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-155514346-2573954481-755741238-1654018636-1233331829-3075935687-2861478708). This security permission can be modified using the Component Services administrative tool.
 
Log: 'System' Date/Time: 13/06/2020 11:31:51 AM
Type: Warning Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID  {C2F03A33-21F5-47FA-B4BB-156362A2F239}  and APPID  {316CDED5-E4AE-4B15-9113-7055D84DCC97}  to the user DESKTOP-N7QQU6I\HP CMT SID (S-1-5-21-1727030935-3764560176-2632440269-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ShellExperienceHost_10.0.18362.449_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-155514346-2573954481-755741238-1654018636-1233331829-3075935687-2861478708). This security permission can be modified using the Component Services administrative tool.
 
Log: 'System' Date/Time: 13/06/2020 10:58:35 AM
Type: Warning Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID  {C2F03A33-21F5-47FA-B4BB-156362A2F239}  and APPID  {316CDED5-E4AE-4B15-9113-7055D84DCC97}  to the user DESKTOP-N7QQU6I\HP CMT SID (S-1-5-21-1727030935-3764560176-2632440269-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ShellExperienceHost_10.0.18362.449_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-155514346-2573954481-755741238-1654018636-1233331829-3075935687-2861478708). This security permission can be modified using the Component Services administrative tool.

  • 0

#10
leader 2

leader 2

    Member

  • Topic Starter
  • Member
  • PipPip
  • 48 posts

Here is my application log from VEW

 

Vino's Event Viewer v01c run on Windows 7 in English
Report run at 13/06/2020 11:35:55 AM
 
Note: All dates below are in the format dd/mm/yyyy
 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 13/06/2020 3:33:16 PM
Type: Error Category: 0
Event: 10000 Source: Microsoft-Windows-DistributedCOM
Unable to start a DCOM Server: {94269C4E-071A-4116-90E6-52E557067E4E}. The error: "2147942593" Happened while starting this command: C:\Users\HP CMT\AppData\Local\Microsoft\OneDrive\19.232.1124.0005\FileCoAuth.exe -Embedding
 
Log: 'System' Date/Time: 13/06/2020 3:01:49 PM
Type: Error Category: 0
Event: 7022 Source: Service Control Manager
The System Guard Runtime Monitor Broker service hung on starting.
 
Log: 'System' Date/Time: 13/06/2020 2:59:38 PM
Type: Error Category: 0
Event: 7022 Source: Service Control Manager
The Downloaded Maps Manager service hung on starting.
 
Log: 'System' Date/Time: 13/06/2020 2:56:29 PM
Type: Error Category: 0
Event: 12 Source: VBoxNetLwf
The driver detected an internal driver error on \Device\VBoxNetLwf.
 
Log: 'System' Date/Time: 13/06/2020 2:54:43 PM
Type: Error Category: 0
Event: 12 Source: VBoxNetLwf
The driver detected an internal driver error on \Device\VBoxNetLwf.
 
Log: 'System' Date/Time: 13/06/2020 2:54:26 PM
Type: Error Category: 0
Event: 12 Source: VBoxNetLwf
The driver detected an internal driver error on \Device\VBoxNetLwf.
 
Log: 'System' Date/Time: 13/06/2020 7:42:28 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 13/06/2020 7:42:28 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 13/06/2020 7:42:28 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 13/06/2020 7:42:28 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 13/06/2020 7:42:28 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 13/06/2020 7:42:28 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 13/06/2020 7:42:28 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 13/06/2020 7:42:28 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 13/06/2020 7:42:28 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 13/06/2020 7:42:28 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 13/06/2020 7:42:28 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 13/06/2020 7:42:28 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 13/06/2020 7:42:28 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 13/06/2020 7:42:28 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 13/06/2020 3:25:02 PM
Type: Warning Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}  and APPID  {15C20B67-12E7-4BB6-92BB-7AFF07997402}  to the user DESKTOP-N7QQU6I\123 SID (S-1-5-21-1727030935-3764560176-2632440269-1005) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
 
Log: 'System' Date/Time: 13/06/2020 3:11:24 PM
Type: Warning Category: 0
Event: 8021 Source: BROWSER
The browser service was unable to retrieve a list of servers from the browser master \\HP on the network \Device\NetBT_Tcpip_{9681A6A0-6529-4F09-BAA1-896AB4A31F4E}.    Browser master: \\HP  Network: \Device\NetBT_Tcpip_{9681A6A0-6529-4F09-BAA1-896AB4A31F4E}    This event may be caused by a temporary loss of network connectivity. If this message appears again, verify that the server is still connected to the network. The return code is in the Data text box.
 
Log: 'System' Date/Time: 13/06/2020 3:00:59 PM
Type: Warning Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID  Windows.SecurityCenter.SecurityAppBroker  and APPID  Unavailable  to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
 
Log: 'System' Date/Time: 13/06/2020 3:00:59 PM
Type: Warning Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID  Windows.SecurityCenter.WscBrokerManager  and APPID  Unavailable  to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
 
Log: 'System' Date/Time: 13/06/2020 3:00:05 PM
Type: Warning Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}  and APPID  {15C20B67-12E7-4BB6-92BB-7AFF07997402}  to the user DESKTOP-N7QQU6I\HP CMT SID (S-1-5-21-1727030935-3764560176-2632440269-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
 
Log: 'System' Date/Time: 13/06/2020 2:59:50 PM
Type: Warning Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}  and APPID  {15C20B67-12E7-4BB6-92BB-7AFF07997402}  to the user DESKTOP-N7QQU6I\HP CMT SID (S-1-5-21-1727030935-3764560176-2632440269-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
 
Log: 'System' Date/Time: 13/06/2020 2:59:48 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name upeer.me timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 13/06/2020 2:54:14 PM
Type: Warning Category: 0
Event: 11 Source: Microsoft-Windows-Wininit
Custom dynamic link libraries are being loaded for every application. The system administrator should review the list of libraries to ensure they are related to trusted applications. Please visit http://support.microsoft.com/kb/197571for more information.
 
Log: 'System' Date/Time: 13/06/2020 2:53:08 PM
Type: Warning Category: 0
Event: 27 Source: e1cexpress
Intel® 82579LM Gigabit Network Connection  Network link is disconnected. 
 
Log: 'System' Date/Time: 13/06/2020 2:09:08 PM
Type: Warning Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}  and APPID  {15C20B67-12E7-4BB6-92BB-7AFF07997402}  to the user DESKTOP-N7QQU6I\HP CMT SID (S-1-5-21-1727030935-3764560176-2632440269-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
 
Log: 'System' Date/Time: 13/06/2020 2:09:08 PM
Type: Warning Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}  and APPID  {15C20B67-12E7-4BB6-92BB-7AFF07997402}  to the user DESKTOP-N7QQU6I\HP CMT SID (S-1-5-21-1727030935-3764560176-2632440269-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
 
Log: 'System' Date/Time: 13/06/2020 2:06:03 PM
Type: Warning Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID  {C2F03A33-21F5-47FA-B4BB-156362A2F239}  and APPID  {316CDED5-E4AE-4B15-9113-7055D84DCC97}  to the user DESKTOP-N7QQU6I\HP CMT SID (S-1-5-21-1727030935-3764560176-2632440269-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ShellExperienceHost_10.0.18362.449_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-155514346-2573954481-755741238-1654018636-1233331829-3075935687-2861478708). This security permission can be modified using the Component Services administrative tool.
 
Log: 'System' Date/Time: 13/06/2020 1:26:33 PM
Type: Warning Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}  and APPID  {15C20B67-12E7-4BB6-92BB-7AFF07997402}  to the user DESKTOP-N7QQU6I\HP 8200 SID (S-1-5-21-1727030935-3764560176-2632440269-1006) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
 
Log: 'System' Date/Time: 13/06/2020 1:26:33 PM
Type: Warning Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}  and APPID  {15C20B67-12E7-4BB6-92BB-7AFF07997402}  to the user DESKTOP-N7QQU6I\HP 8200 SID (S-1-5-21-1727030935-3764560176-2632440269-1006) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
 
Log: 'System' Date/Time: 13/06/2020 1:03:50 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name tracker.ilibr.org timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 13/06/2020 12:52:50 PM
Type: Warning Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}  and APPID  {15C20B67-12E7-4BB6-92BB-7AFF07997402}  to the user DESKTOP-N7QQU6I\HP 8200 SID (S-1-5-21-1727030935-3764560176-2632440269-1006) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
 
Log: 'System' Date/Time: 13/06/2020 12:52:50 PM
Type: Warning Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}  and APPID  {15C20B67-12E7-4BB6-92BB-7AFF07997402}  to the user DESKTOP-N7QQU6I\HP 8200 SID (S-1-5-21-1727030935-3764560176-2632440269-1006) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
 
Log: 'System' Date/Time: 13/06/2020 11:31:52 AM
Type: Warning Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID  {C2F03A33-21F5-47FA-B4BB-156362A2F239}  and APPID  {316CDED5-E4AE-4B15-9113-7055D84DCC97}  to the user DESKTOP-N7QQU6I\HP CMT SID (S-1-5-21-1727030935-3764560176-2632440269-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ShellExperienceHost_10.0.18362.449_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-155514346-2573954481-755741238-1654018636-1233331829-3075935687-2861478708). This security permission can be modified using the Component Services administrative tool.
 
Log: 'System' Date/Time: 13/06/2020 11:31:51 AM
Type: Warning Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID  {C2F03A33-21F5-47FA-B4BB-156362A2F239}  and APPID  {316CDED5-E4AE-4B15-9113-7055D84DCC97}  to the user DESKTOP-N7QQU6I\HP CMT SID (S-1-5-21-1727030935-3764560176-2632440269-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ShellExperienceHost_10.0.18362.449_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-155514346-2573954481-755741238-1654018636-1233331829-3075935687-2861478708). This security permission can be modified using the Component Services administrative tool.
 
Log: 'System' Date/Time: 13/06/2020 10:58:35 AM
Type: Warning Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID  {C2F03A33-21F5-47FA-B4BB-156362A2F239}  and APPID  {316CDED5-E4AE-4B15-9113-7055D84DCC97}  to the user DESKTOP-N7QQU6I\HP CMT SID (S-1-5-21-1727030935-3764560176-2632440269-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ShellExperienceHost_10.0.18362.449_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-155514346-2573954481-755741238-1654018636-1233331829-3075935687-2861478708). This security permission can be modified using the Component Services administrative tool.

  • 0

Advertisements


#11
RKinner

RKinner

    Malware Expert

  • Expert
  • 23,013 posts
  • MVP

Can you unplug all of the external hard drives and then plug just the Seagate back in and then run  Speedfan and see if it then sees it?

 

Can you unplug the Seagate and plug in all of the rest and then run Speccy and post the log?


  • 0

#12
leader 2

leader 2

    Member

  • Topic Starter
  • Member
  • PipPip
  • 48 posts

Thanks for your suggestion. I disconnected the other hard drives and left the Seagate plugged in. Speedfan didn't show any data for the Seagate drive once again like in this image from before. https://ibb.co/hR6FP7C How can this be fixed? The drive seems to be working normally so I thought it would show the data like the other drives did. 

 

I attached the speccy log without the seagate drive plugged in. 

 

EDIT: I'm concerned about the main WD Elements 8tb drive from my topic starter post for another reason now and was wondering if you could give any any insight for my peace of mind. This drive originally had the drive letter E and later it changed to F for some reason without me doing so. After I ran  DISM  /Online  /Cleanup-Image  /RestoreHealth that drive changed back to E and my portable WD 3tb became F.

 

Just now after I unplugged the drives and checked Seagate on Speedfan and then created my speccy log without the Seagate drive plugged in the drive letter changed to H. I am concerned because I heard that drives can randomly change drive letters when they are having problems. Should I be worried about the drive letters changing combined with the issue that I discussed in my original post? I don't want to lose the data on the drive if it's more than the hub being a problem. This drive has also not shown folders as being empty when they were full and had folder and/or file not found errors recently too, adding to my concern.

Attached Files


Edited by leader 2, 15 June 2020 - 02:57 AM.

  • 0

#13
RKinner

RKinner

    Malware Expert

  • Expert
  • 23,013 posts
  • MVP

I was hoping the Seagate was dragging down the rest of the drives but that doesn't seem to be the case.  I don't know why your Seagate is not providing the SMART info to speedfan.  You can get SeaTools for Windows from Seagate and run the extended or long test and see if it sees any problem.

 

https://www.seagate....ols-win-master/

 

There is an equivalent for Western Digital called Data Lifeguard Diagnostic for Windows

 

https://support.wdc....ds.aspx?lang=en

 

I would definitely run it on the

WD30NMZW drive

 

If you have problems with both drive types then it might be a problem with the usb driver.  I think that's part of the intel chipset utility so you might try updating it:

https://downloadcent...ty?product=1145

This is a zip file so you need to save it then right click and Extract All, Extract.  Then right click on SetupChipset.exe and run as admin.


  • 0

#14
leader 2

leader 2

    Member

  • Topic Starter
  • Member
  • PipPip
  • 48 posts

When I tried to run the intel chipset utility it gave this error:

 

 

0x00004E24 This platform is not supported. 

 

What can I do to fix that so it will install on the computer?


  • 0

#15
RKinner

RKinner

    Malware Expert

  • Expert
  • 23,013 posts
  • MVP

Did the extended tests pass?

 

You could try one of the USB test tools here:

https://www.raymond....sb-flash-drive/

 

Probably want to use a clean USB drive and move it from port to port to see if it finds any problems.

 


 

 

 

You could look for an older version of the chipset utility but reading the notes it says it won't help USB.  Turns out Win 10 uses generic drivers for intel.  Win 7 had special drivers for USB and they needed to be uninstalled before updating.

https://www.intel.co...t-software.html

Do you have it installed?

 

Try searching for

device manager

hit Enter

scroll down to the bottom where it says Universal Serial Bus controllers and click on the arrow in front to open it up.

 

Right click on each of the drivers you see below Universal Serial Bus controllers and Uninstall Device.  Reboot when done.

 

Windows will reinstall the drivers and often this correct problems.


  • 0






Similar Topics


Also tagged with one or more of these keywords: external hard drive, usb hub, windows 10, windows 10 pro, hard drive, hdd, Error 0X800701B1, failure, copy error

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP