Question This device is currently in use. Close any ...

[BTRY B 529th FA BN]

Been having an issue with the same problem across different motherboards, different installs, Intel & AMD. I can boot up a Hot Plug HDD and or SSD, nothing is using it, I go to eject the device by 'Safely Remove Hardware and Eject Media' and for way too long I get the warning "This device is currently in use. Close any programs or windows that might be using the device, and then try again." I mean over 10 minutes sometimes. ABSOLUTELY NOTHING USING IT. This is insane, why is this happening? What is using it? I have windows search turned off, indexing is off on the drive... wtf

 

[VirtualLarry]

Yes, unfortunately, Windows is a PITA about that. Try using the utilities "HotSwap!" (by a Japanese programmer), or Unlocker. Might also have to hit CTRL+ALT+DEL, select "Log off", and then log back in again. Because the "root" Explorer.exe shell instance, sometimes "holds onto" volume/file locks.

 

[BTRY B 529th FA BN]

Would this also be related to the ability to detect a hot swap SATA HDD/SSD drives? My old X58 build would detect drives immediately when they were turned on via a Lian Li HDD power strip, however I also had a main boot drive that was an SSD. This new X570 board I have I'm using an NVMe drive for my boot drive: the detection of any type of drive being activated while the system is booted up, can vary between a second or two, to taking over 5 minutes to recognize. If I open Device Manager and run a 'Scan for hardware changes' any drive that's taking a long time to recognize will instantly be recognized. Seems more like a windows; or the cpu being in deep sleep state?

 

[VirtualLarry]

If you want to detect an immediately-inserted HDD, consider using the "HotSwap!" tool.

 

[BTRY B 529th FA BN]

How did we go from things working perfect on 10+ year old hardware to this?

EDIT: Hot Swap is enabled in the bios, btw

 

[VirtualLarry]

HotSwap!

mt-naka.com

 

[BTRY B 529th FA BN]

Yup, seen that.

 

[Steltek]

You don't have any VSS errors in your Windows system log do you (especially ones referencing the hot plug drives)?

I've always had suspicions that Windows seems to "hang on" to hot plugged drives due to issues with the VSS service (i.e. the Windows service that does volume shadow copies).

 

[mxnerd]

How To Find Which App Or Process Is Using A USB In Windows

How To Find Which App Or Process Is Using A USB In Windows

www.addictivetips.com

WhatSoftware Blog

WhatSoftware, a daily updated Tech Blog with basic and advanced, unbiased software reviews, computer tips news and more!

www.raymond.cc

 

[BTRY B 529th FA BN]

You don't have any VSS errors in your Windows system log do you (especially ones referencing the hot plug drives)?

I've always had suspicions that Windows seems to "hang on" to hot plugged drives due to issues with the VSS service (i.e. the Windows service that does volume shadow copies).

In Event Viewer? If so I haven't checked. Does the VSS Service have something to do with System Restore? I just turned that off yesterday.

I did run a sfc scannow and it did find some corrupt files.. it's a brand new install, not even a week of use. I installed with everything running at default speeds with the CPU, RAM, nothing that should have effected the stability during install.

 

[Steltek]

In Event Viewer? If so I haven't checked. Does the VSS Service have something to do with System Restore? I just turned that off yesterday.

I did run a sfc scannow and it did find some corrupt files.. it's a brand new install, not even a week of use. I installed with everything running at default speeds with the CPU, RAM, nothing that should have effected the stability during install.

VSS is Volume Shadow Service. System Restore uses it, but other applications can make use of it as well. If you get file corruption in the hidden VSS folder on a drive, it can cause Windows to have issues with releasing a drive. However, you'll normally have VSS warnings/errors show up in the System log if there are issues with that service.

@mxnerd's suggestions above are very good ones to try. It might help you figure out if any processes or applications are accessing the drive that shouldn't be.

 

[Noid]

How did we go from things working perfect on 10+ year old hardware to this?

When MS declared itself a "service" .. rather than an OS.
( operating system - software purchased.)