Windows Defender stopping me from ejecting harddrive

I got an answer to this issue.  You do not have to safely remove USB drives anymore. If you look under disk management.  Right clik on the disc label in the  lower section. Select properties. Then select the policies tab. Under that is removal policy. Quick Removal(default) and Better Performance. As long as Quick Removal(default) is selected you can remove the drive anytime you want safely. I would  make sure the drive is not actually churning before pulling the plug. I've had no issues since someone explained this to me on Windows 10 help forums. https://www.tenforums.com/

Hope this helps.

 

Hi,

Useful info - but how do you make sure its 'not churning'.  Where is the 'stop churning' button?  I think mine is churning because of Windows Defender doing something.  When I do manage to safely eject the HD it spins down.  When it refuses to eject it won't spin down, and its churning.  When I pull it out when its spinning like this it makes a funny dying sound that doesn't sound normal.

I hope the UI expert who thought it sensible to have an 'eject device' button which then presents a 'Problem ejecting USB Mass storage device - device is currently in use, close any programs or windows that might be using the device and then try again' dialog box if the correct thing is just to pull the USB lead is 'needs improvement' on their annual review. 

Andy

@old-fogey, 

The problem with windows defender is not just for USB devices, the same happens with external SATA drives. This problem started with Windows 10 v 2004 and it is not happening with the same hardware with Version 1909, it is also not happening with insider build 20180 or other development builds.

It definitely looks like a bug caused by windows defender only with builds 19041 or 19042...

When the problem occurs, a restart of the PC seems to cure the problem temporarily and a clean eject is allowed before defender starts using the drive again.

The problem is definitely a bug it only happens with 19041 builds and MS should fix it.

[Machine Translation]

@RobertFlintstone

I appreciate your helpful answer on how to get around this problem. Analyzing your answer I found a Microsoft page that provides more details on this subject:

Change in default removal policy for external storage media in Windows 10, version 1809

@old_fogey

I also agree with you and I think this issue needs a Microsoft approach that gives the user more simplicity and security when removing a USB device. The user needs to have full confidence that they are following the correct procedure when removing a USB device, especially hard drives with high storage capacity.

@fg2001

I use Windows 10 Pro - Version 1909 - OS build: 18363.959 and this Windows Defender problem also occurs on my PC.

@fg2001

I use Windows 10 Pro - Version 1909 - OS build: 18363.959 and this Windows Defender problem also occurs on my PC.

Jose, 

The quick removal for external drives is already set as default. That is not the issue, when eject is issued they should first stop the activity of windows defender on the drive and then eject correctly.

If you see the problem also with 1909, that means that they introduced the bug with some recent changes of the defender also in 1909.

I had 1909 for over a year and never had any problems with eject.

It all started for me with v 2004 in 5 different machines.

Also I don't get the problem with any insider development build up to build 20180.

@fg2001

I use Windows 10 Pro - Version 1909 - OS build: 18363.959 and this Windows Defender problem also occurs on my PC.

Jose, 

The quick removal for external drives is already set as default. That is not the issue, when eject is issued they should first stop the activity of windows defender on the drive and then eject correctly.

If you see the problem also with 1909, that means that they introduced the bug with some recent changes of the defender also in 1909.

I had 1909 for over a year and never had any problems with eject.

It all started for me with v 2004 in 5 different machines.

Also I don't get the problem with any insider development build up to build 20180.

[Machine Translation]

@ fg2001,

Thanks for the answer!

1. • Yes, Quick Removal by default is already OK. I posted the link just to show Microsoft's official information about this feature.

2) - "... If you see the problem also with 1909, that means that they introduced the bug with some recent changes of the defender also in 1909 ..."

Yes, the USB device removal problem and Windows Defender in version 1909 started recently. Before it worked correctly.

@fg2001

I use Windows 10 Pro - Version 1909 - OS build: 18363.959 and this Windows Defender problem also occurs on my PC.

Jose, 

The quick removal for external drives is already set as default. That is not the issue, when eject is issued they should first stop the activity of windows defender on the drive and then eject correctly.

If you see the problem also with 1909, that means that they introduced the bug with some recent changes of the defender also in 1909.

I had 1909 for over a year and never had any problems with eject.

It all started for me with v 2004 in 5 different machines.

Also I don't get the problem with any insider development build up to build 20180.

[Machine Translation]

@ fg2001,

Thanks for the answer!

1. • Yes, Quick Removal by default is already OK. I posted the link just to show Microsoft's official information about this feature.

2) - "... If you see the problem also with 1909, that means that they introduced the bug with some recent changes of the defender also in 1909 ..."

Yes, the USB device removal problem and Windows Defender in version 1909 started recently. Before it worked correctly.

Hi Jose, 

Thanks for the confirmation. I just hope that MS comes out with a fix soon.

As I said earlier the problem is not just with USB devices, but also with external SATA devices.

I don't disagree with anything posted here. I am still having some issues with my USB drive having corrupted files and or folders after coping new data to the drive. It could be because Defender is still running and maybe not clearing the new files as safe. I do not know. I've continued to look for ways to get around this issue. Maybe Defender is the problem. And where is msft in all of this??