Since v1803 - Problem Ejecting USB Attached SCSI (UAS) MSD

Please pardon any first post missteps - I have been a follower of these forums since Win7, and I find myself needing the great information contained herein even more now that I made the leap of faith to Win10 last December.

Since I got my current Dell XPS8920 system using Windows 10 last December, I have been using Seagate Expansion+ USB External drives to back up data files and system images. Routinely I would connect the USB cable to the drive, backup the files by copying, or by using SyncBack, then when finished, selecting the Safe Removal icon from the taskbar, and selecting the "Eject Expansion+" option, and the "Safe to Remove..." popup would display with no problem.

Some time since the upgrade to v1803, all of my Expansion+ drives return a "Problem Ejecting USB Attached SCSI (UAS) Mass Storage Device" error popup, stating that the drive is in use, whenever Safe Remove is attempted. USB thumb drives work OK with Safe Remove, however.

I have verified that no programs are accessing the drives, that 'Optimize for Quick Removal' has disabled Write Caching, that 'Allow Indexing Service...' is disabled for each volume on the drive, and that all updates to Windows 10, device drivers, Intel Drivers, and Dell-provided updates have been made right up to the present. Has anyone else had this problem come up only after the v1803 upgrade? Was the USB Attached SCSI (UAS) Protocol driver added to Windows 10 in or after v1803?

I have also used USBTreeView to look at the drive information when connected, and got the following (in part):
-----
+++++++++++++++++ Device Information ++++++++++++++++++
Device Description : USB Attached SCSI (UAS) Mass Storage Device
Device Path : \\?\usb#vid_0bc2&pid_2323#msft30na8a2pw4#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
Device ID : USB\VID_0BC2&PID_2323\MSFT30NA8A2PW4
Hardware IDs : USB\VID_0BC2&PID_2323&REV_0100 USB\VID_0BC2&PID_2323
Driver KeyName : {4d36e97b-e325-11ce-bfc1-08002be10318}\0004 (GUID_DEVCLASS_SCSIADAPTER)
Driver : \SystemRoot\System32\drivers\uaspstor.sys (Version: 10.0.17134.1 Date: 2018-04-11)
Driver Inf : C:\Windows\inf\uaspstor.inf
Legacy BusType : PNPBus
Class : SCSIAdapter
Class GUID : {4d36e97b-e325-11ce-bfc1-08002be10318} (GUID_DEVCLASS_SCSIADAPTER)
Interface GUID : {a5dcbf10-6530-11d2-901f-00c04fb951ed} (GUID_DEVINTERFACE_USB_DEVICE)
Service : UASPStor
Enumerator : USB
Location Info : Port_#0001.Hub_#0002
Location IDs : PCIROOT(0)#PCI(1C00)#PCI(0000)#USBROOT(0)#USB(1), ACPI(_SB_)#ACPI(PCI0)#ACPI(RP02)#ACPI(PXSX)#ACPI(ASM1)#ACPI(HS01)
Container ID : {b7645173-d91b-50a8-8e4a-1469f70cae1d}
Manufacturer Info : USB Attached SCSI (UAS) Compatible Device
Capabilities : 0x14 (Removable, UniqueID)
Status : 0x0180600A (DN_DRIVER_LOADED, DN_STARTED, DN_DISABLEABLE, DN_REMOVABLE, DN_NT_ENUMERATOR, DN_NT_DRIVER)
Problem Code : 0
Power State : D0 (supported: D0, D3, wake from D0)
Child Device 1 : Disk drive (Disk3)
DevicePath : \\?\scsi#disk&ven_seagate&prod_expansion+#000000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
Device ID : SCSI\DISK&VEN_SEAGATE&PROD_EXPANSION+\000000
Class : DiskDrive
-----

When I try to use USBTreeView's 'Safely Remove' option on the drive, I get a Removal Failed popup stating:

Result: CR_REMOVE_VETOED
VetoType: DEVICE
VetoName: STORAGE\Volume\{07049b2f-99cc-11e8-a817-14b31f081fa5}#0000000000100000

Any ideas on what might be the problem? I have even mastered the art of unplugging the drive at the moment of spin-down during a restart, but I would really like to get back to the way these Expansion+ drives worked before v1803... Many thanks for all the help I have already gained from the forums!!!

Mike

I see you have tried a lot of options there, couldn't see you if you had disabled the use of the Recycle Bin for thet drive.

Also, have you seen this page re similar issues.

Windows will not allow me to safely remove my drive. It keeps reporting the drive is busy or in use | Seagate Support

das10,

Thank you for your response - I did try disabling Recycle Bin for the drives, no luck. I reported the problem to Seagate support, and they replied with that same link, also no luck.

The thing that really throws me is that the drives worked fine with Windows 10 v1709; unfortunately I cannot remember what build number was closest to the first time I couldn't remove the drive...

Mike

Have you tried USBDeview by nirsoft ?

View any installed/connected USB device on your system

It allows you to remove entries of the USB devices which you have attached to your PC in the past with their dates. Maybe if you removed your problem entry from there and let Windows Re_enumerate it when you next insert that USB it might work. Or it may give you some kind of clue as to why your USB is behaving as it is. Anyway have a read of the page.

What does the Windows event log say when you try to safely remove?

Warning

8/12/2018 17:38:03

Microsoft-Windows-Kernel-PnP

225

(223)

The application \Device\HarddiskVolume4\Windows\System32\Taskmgr.exe with process id 12080 stopped the removal or ejection for the device USB\VID_1058&PID_0820\575839314141343736503844.

Same problem on my 1803 Win10 .
But its not always , sometimes have to reboot , sometimes HDDs can be ejected in the normal way...........
Still searching for a working solution !

Thanks to all for the responses - While searching on the CR_REMOVE_VETOED error message received in USBTreeView, I found Uwe Sieber's DriveRemove and USBDriveInfo. After a little reading and fiddling, DriveRemove was successful at powering off the drive and removing the Safe Removal icon from the systray.

Now, here is the strange thing - immediately after removing the drive with DriveRemove, I attached the drive again to be sure all was well with the contents, and now the Safe Remove icon works as it used to!! DriveRemove is command-line and would have been a little tiring to use, so I am glad the problem seems resolved at this point. USBDriveInfo is a Windows program, part of his USB Drive Letter Manager service, but as he says is a 'handy standalone', also with the ability to Safely Remove USB drives.

I will continue to experiment, and see if the 'restoration' of my ability to Safely Remove my Expansion+ drives persists. Of course, tomorrow is a Patch Tuesday, so who knows what will happen ….

Tried the "recycling bin-option " , did not work after next reboot same old situation .
However, Im not getting any errors in my logs ( ?)
Im afraid to destroy my external HDDs by rebooting , each time I cant eject the HDD............

@das10 - thanks for the steer to USBDeview - I think my goto utility will be USBDriveInfo, from previous post.



@pietcorus2 - I recommend you look up Uwe Sieber's USBDriveInfo.exe, and try the Safe Remove right-click options for the drive in question, and try the same thing on each of the three tab views. If they do not work, try the command line DriveRemove. It seems one use of that utility cured my XPS8920's problem … but only time will tell.