Just finished installing and wanted to be sure the USB Drive drive ejected like it's supposed to, but it doesn't! We're right back where we started:
This Device is Currently in Use. Close Programs! Sheesh!
Sometimes a program that is open, even one you don't think was associated with recent USB drive activity, can prevent the release of the hardware. Common culprits are Outlook and any browsers. Best to close every program one by one to see what was holding it up.
I had already closed everything, but I just went back and closed everything again . . . I still get the same message. BTW, this was also happening in Build 10547 until an update a couple of days ago straightened things out.Sometimes a program that is open, even one you don't think was associated with recent USB drive activity, can prevent the release of the hardware. Common culprits are Outlook and any browsers. Best to close every program one by one to see what was holding it up.
The thing is that this has been an intermittent problem since Windows 7. Sometimes you go to eject your USB drive and no problem. Other times you get the 'drive is busy' thing. I've noticed the same thing right through the 8's and into the 10 builds. The problem is that it's intermittent, and it's really hard to troubleshoot what's going on.Just finished installing and wanted to be sure the USB Drive drive ejected like it's supposed to, but it doesn't! We're right back where we started:
This Device is Currently in Use. Close Programs! Sheesh!
But it's not new to Windows 10, any build, in my experience. As Kanata said, there are programs that don't release their call on the drive - even after you close them. Sometimes, just waiting for a while (maybe a long while) and trying again gets it done. It's a strange problem, and I hope they fix it soon.
I use: Sync
From Admin command prompt, type: sync -e
then just remove the device without using Safely Remove.
NOTE: You can create a shortcut, set it to run as Admin and run whenever you need.
Yet, I've never encountered this problem more than once or twice; not in Windows 7, 8.0/8.1 or Windows 10. That is until it popped up in Build 10547.The thing is that this has been an intermittent problem since Windows 7. Sometimes you go to eject your USB drive and no problem. Other times you get the 'drive is busy' thing. I've noticed the same thing right through the 8's and into the 10 builds. The problem is that it's intermittent, and it's really hard to troubleshoot what's going on.
But it's not new to Windows 10, any build, in my experience. As Kanata said, there are programs that don't release their call on the drive - even after you close them. Sometimes, just waiting for a while (maybe a long while) and trying again gets it done. It's a strange problem, and I hope they fix it soon.
Nor can I figure what "had a hold" on this particular Jump Drive, since the only reason I plugged it in was to see if it could be ejected. I've plugged in four more drives and each and every one of them are in use and cannot be ejected.
You don't have indexing on for the drive in question, do you? Just a random thought.
Not that I know of.You don't have indexing on for the drive in question, do you? Just a random thought.
In order to see what's holding it. Download: Process ExplorerFrom the menu: Find->Find Handle or DLL
Lappy 15 refuses to turn loose of Jump Drive too.
