"Safe to remove" pop-up does not appear.

I think I found the place to solve this.

- In the search bar next to the Start icon, type in "focus assist"
- Click on "Focus assist"
- Click on the "Off" button

That did it for me.

Omg... my windows 10 current version (winver say 20H2 19042.867) has start to give to me this issue.
On my pc i have download the newest version of "Usb Safely Remove" and the alternative on quick & easy (Downloads | Quick And Easy Software).

I look this other suggestion for try to see how append.... but right now when i click on safe remove for a pendrive i see the drive disappears on "my computer" but the the icon from system tray it's not disappears and no notification appears to say to me i can remove the drive.
It's disappears only when i remove the pendrive from usb port.... strange.

Sorry for my double consecutive question but look right now this little icon ******* :)

It's still remain ever on my system tray:



And it's never disappears............. how i can try to fix this issue ?

The problem has not happened again for me for some time now on my desktop pc. Not sure about my laptop since I rarely use it. Currently running version 20H2 Build 19042.867. Previously the issue was happening after about a week after a reboot or Windows Explorer reset as I mentioned earlier in this thread. Never had the issue before Windows 10.
Mark

Geosammy's fix worked for me.

Hi. Currently running Windows 10 20H2 19042.985. The issue now does not seem to happen with flash drives but does happen sometimes with my external hard drive that I use for Macrium backups. Since it is also set for Quick Removal (like the flash drives), if it happens I just pull out the usb cable. According to Event Viewer the main culprit is usually Windows defender although othe processes or applications have been shown to prevent the Safe Ejection. Also, I just tried Geosammy's fix again. Unfortunately I still have the issue when using my external backup drive.

@f14tomcat:
Interesting. I've used Lockhunter for years, never tried it for this issue (which will probably never be resolved by Microsoft).