This Device is Currently in Use - USB Jump Drive

And I have had this problem since 10240RTM. I can not eject my external HDD by right-clicking the icon in the notification area. Additionally, in This PC, I do not even have the option to eject in the right-click menu.

mlhifi said:

As far as I'm aware, it has always been the case that USB hard drives do not have an eject option from the right-click in ThisPC, only in the notification area. Only USB memory sticks have that option... again, as far as I'm aware!

There is an option to eject my USB 3.0 Toshiba External drive in "Safely Remove Hardware" in the System Tray, so I'd guess there is that option after all.

mlhifi said:

Exactly what I am getting and, I suspect, we all are.
Something just came up that is probably the same problem.
I decided a clean install of 10565 would be a good idea. I have always used Rufus to make my bootable USB sticks without incident.
However, on this occassion, Rufus locks up with "Requesting Disk Access" and eventually fails with a message basically saying it doesn't have exclusive access to the USB drive! Same thing right? The EJECT problem is because the USB stick is "being used by another program" and Rufus refuses because it "doesn't have exclusive access".
We just need to find exactly WHAT program is preventing both these actions and we're home and dry.
Trouble is, I'm not a PC expert and that's what I (we) need!
Anyone have any thoughts?
(No update to my system has sorted it out sadly Wynona!)

Well, we had the Rufus program author here in Tenforums at @Wynona 's request, and he identified the Windows OS problems and why it wasn't working, but some people were unbelievably rude to him, and I suspect we won't see him again any time soon.

mlhifi said:

Exactly what I am getting and, I suspect, we all are.
Something just came up that is probably the same problem.
I decided a clean install of 10565 would be a good idea. I have always used Rufus to make my bootable USB sticks without incident.
However, on this occassion, Rufus locks up with "Requesting Disk Access" and eventually fails with a message basically saying it doesn't have exclusive access to the USB drive! Same thing right? The EJECT problem is because the USB stick is "being used by another program" and Rufus refuses because it "doesn't have exclusive access".
We just need to find exactly WHAT program is preventing both these actions and we're home and dry.
Trouble is, I'm not a PC expert and that's what I (we) need!
Anyone have any thoughts?
(No update to my system has sorted it out sadly Wynona!)

Arrrghhhh! So a clean install of 10565 didn't solve the problem? Sigh . . .

Yes, I'm suffering the same thing with Rufus, but the first time I brought it up, there was such a firestorm that I decided I wouldn't mention Rufus until someone else brought it up. You lucky victim, you! :)

I'm not totally out of luck, though, since all my systems are dual boot with Insider and Windows 10 RTM. So I can visit the RTM partition when I need to create a bootable Jump Drive. :)

I don't think it's a program; I think it Windows 10 itself, since some have had the "Requesting Disk Access" for most of their Insider life, while others of us have only begun to suffer it since Build 10547. Our machines are just too diverse for it to be a program.

simrick said:

Well, we had the Rufus program author here in Tenforums at @Wynona 's request, and he identified the Windows OS problems and why it wasn't working, but some people were unbelievably rude to him, and I suspect we won't see him again any time soon.

Yeah, I'm still stinging from that rudeness and I'm of the same opinion as you, Simrick. The problem is in Windows 10 itself; our systems are just too diverse for it to be anything else.

Wynona said:

Yeah, I'm still stinging from that rudeness and I'm of the same opinion as you, Simrick. The problem is in Windows 10 itself; our systems are just too diverse for it to be anything else.

Yes, well he proved it, by the fact that Rufus takes exclusive control of the USB stick before creating the media, and Windows won't let it go. Based on his explanation of why it is important for this "exclusive control", I totally agree with him. He also took the time to research a couple of other programs which don't take control, and proved that this was the issue beyond a doubt. So, KUDOS to him, for taking his time to do that. If someone wants to use a program which does not take exclusive control before creating the bootable USB stick, then they can do it, but I wouldn't be confident with what they get in the end.

mlhifi said:

My goodness... what on earth happened when you.... eh, well never mind, I won't go there!

Thank you. I'm sure you've seen Simrick's post on the matter. :)

mlhifi said:

However, I don't see a problem with bringing it up! Why not? It's a great program that I've been using for years and, since I discovered it, have got rid of those other programs that purport to provide the same function!
And it's factual... Rufus DID stall, but that just means something prevented it from functioning.... I just want to know WHAT!
And sooner rather than later, 'cos I need a bootable USB and am unable to make one now!
Let's face it, the "Unable to Eject USB" problem has been around for a long time... I'd love to know what's causing it.

From Simrick's Post about Rufus: Rufus takes exclusive control of the USB stick before creating the media, and Windows won't let it go. Based on his explanation of why it is important for this "exclusive control", I totally agree with him. He also took the time to research a couple of other programs which don't take control, and proved that this was the issue beyond a doubt. So, KUDOS to him, for taking his time to do that. If someone wants to use a program which does not take exclusive control before creating the bootable USB stick, then they can do it, but I wouldn't be confident with what they get in the end.

I will try to find his explanation as to why this is happening and copy and paste his posts here.