

- #Seagate 4tb backup plus portable unable to eject windows 10 update
- #Seagate 4tb backup plus portable unable to eject windows 10 windows 10
Only part of the hardware id such as "0984xxxx" Step 1 should be listed under usbstor but probably are no longer listed or have Type Regedit in the Windows command box at theĬommand and run as administrator. I could usually revive the drive by disconnecting the power cable, unplugging the USB cable, and then reconnecting both. I have a WD USB hard drive I attach forīackups and it has a separate hardware id. I also started having this same problem with my 4TB Backup Plus USB 3.0 external drive after updating my operating system to Windows 8.1. Need is the device id numbers USB\VID_0984&PID_0310&REV_0305 =īoth and do the regedit for both. Right click on USB Mass Storage Device and Type Device Manager in windows command box People like me (same procedure more details): USB\VID_0984&PID_0310 Use the device ID "09840310" to add a newĢ) Run Regedit and enter the information you obtained asįollows: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbstor Add KeyĠ9840310 In key add DWORD DeviceHackFlags Set value to 400 ﴾hex﴿ Of your External USB HDD in device manager under USB Mass Storage Mine was
#Seagate 4tb backup plus portable unable to eject windows 10 windows 10
It startedĭoing it again after this mornings Windows 10 feature update.
#Seagate 4tb backup plus portable unable to eject windows 10 update
Update it would get disconnected after a certain amount of time. There is a newer model of this item: Seagate One Touch, Portable External Hard Drive, 4TB, PC Notebook & Mac USB 3.0, Black, 1 yr MylioCreate, 4 Month Adobe Creative Cloud Photography and Two-yr Rescue Services (STKC4000410)104.02(1,091)In Stock. HDD that is constantly running for the Windows Files backup. New & Used (20) from 79.99& FREE Shipping.

I used the following solution and it worked for me. It also happened when I updated to Windows 10 from Windowsħ. Windows kicking my USB drive off the system after Windows Update.ĥ/2/18 Happened again after new Windows Update. Here is the solution I use every time I get a major Windows update and the problem starts again. I had a similar problem that was caused by Microsoft Windows 10 and updates.
