Safely remove hardware failure.

Let's regroup...

1) Is this a HDD with a USB 3.x interface?
2) If yes, do you know how to delete the appropriate Root Hub for this device via Device Manager? Be careful.
3) If you are unsure, please contact WDC's technical support by telephone.

Thanks.

Compumind said:

Let's regroup...

Compumind said:

1) Is this a HDD with a USB 3.x interface?

Yes, but it is hooked to a 2.0 USB card reader slot supported by Realtek drivers.

Compumind said:

2) If yes, do you know how to delete the appropriate Root Hub for this device via Device Manager? Be careful.

Yes.

3) If you are unsure, please contact WDC's technical support by telephone.

Thanks.

Will get back with results!

EyeInTheSky said:

Will get back with results!

Can you connect it to a native USB port, either 2.x or 3.x (preferred)?
This is important for testing.

I figured it out - and believe me, this does not make any sense to me why.

After going into my Settings>Privacy>Background apps - and turning Background apps on, it started working again.

The setting is called "Let apps run in the background" - that is all I turned on. I didn't have to turn any of the sub-switches on to make it work.








And finally, I got my balloon pop up back:




Now, I know for a fact that the eject hardware balloon pop up worked before turning that setting on for background apps - so don't believe for one minute that Windows update had nothing to do with this

It was the same for my Realtek Audio drivers too - I went through the same trouble after the last Cumulative Update fubared my Hi-Q Recorder and I had to turn access for the microphone privacy on as well.

Bree said:

The paid-for version? Do you have Macrium Image Guardian turned on?

No, I don't have the paid version.

I figured it out though @Bree!

Thanks for your help anyway - it is always appreciated.

Thank you @Compumind as well.

Well...

I don't understand what you have going there, lol.
However, I'm glad that this config is working.

I cannot see how the global background apps setting can affect this, since the eject function is on the system level, AFAIK.

Could you try turning off the background apps on another system and see if it happens after you reboot?

Cheers!

CarlSD said:

Yep, that's something that started happening with 1809.

"Let Apps run in the background" needs to be turned on or the 'flyout' notifications for disconnecting external drives, etc. won't work. Found this out when the same thing happened to me.

In the settings for the Windows Privacy Dashboard program that I use there is a warning that disabling "Let Apps run in the background" will stop the 'flyout' notifications working in Windows 10 1809.

Yes, I just verified that for myself. Many thanks.

However, the original complaint was a Device Error on ejection of an external USB Drive.
I think that things went a bit OT here but that's OK.

Appreciate you "chiming in!"

CarlSD said:

Yep, that's something that started happening with 1809.

"Let Apps run in the background" needs to be turned on or the 'flyout' notifications for disconnecting external drives, etc. won't work. Found this out when the same thing happened to me.

In the settings for the Windows Privacy Dashboard program that I use there is a warning that disabling "Let Apps run in the background" will stop the 'flyout' notifications working in Windows 10 1809.

I was wondering about that because I never messed around with the background apps settings and out of the blue, the ejection balloon pop up went missing.

I am still confused as to why none of the sub settings had to be turned on though in order for it to work; I figured at least the "Windows Security" switch would have had to of been toggled.

As I pointed out in my pictures, none of the sub switches had to be activated in order for the balloon pop to work; it just started working the second I switched on the main switch.

Also, what is the Privacy Dashboard program you are using?

Compumind said:

Yes, I just verified that for myself. Many thanks.

However, the original complaint was a Device Error on ejection of an external USB Drive.
I think that things went a bit OT here but that's OK.

Appreciate you "chiming in!"

I'm not so sure it was an error ejection complaint as more so I posted in my first post that I wasn't getting the pop up notice.

It was listed as a Driver error in the devices section not Device error as per my picture in the first post.

Either way, it is solved and I'm sorry if I led you to believe that it was more technical than it really was.

Odd thing though, I still get the driver error even though the balloon pop is working now. The "Driver Error" only appears when I click the "safely remove hardware" button and select my device (Passport); otherwise, it isn't there all the time. I had the "Devices" interface open when I ejected the WD Passport and it stayed up for a couple of seconds after ejection of the hardware and then went away the same time the balloon pop up did:



Is it still a problem? I don't know and I even went to the WD support page to check for recent drivers but Driver Easy Pro had already installed the latest drivers for the WD product I have.

Odd thing to note as well; I had 129 drivers all up to date before this incident and now that the pop up is working, I have 105 drivers up to date according to Driver Easy Pro.

What the heck happened to my other 24 drivers? This is very strange, to say the least.

And just to verify nothing strange is going on, I just did another scan:



EDIT:

Oh, and as to your question in post #17: Could you try turning off the background apps on another system and see if it happens after you reboot?

Yes, I tried it with the same results since the other computer is running 1809 as well.