Moving Files to Explorer

the jimmy said:

I've always moved files from Windows Live Mail by dragging them into Explorer, now I get this message, also happened trying to move files from my phone (android)

That rather unhelpful 'The system cannot find the file specified' error is often seen if Controlled Folder Access has blocked access to a protected destination folder.

Add Protected Folders to Controlled Folder Access in Windows 10

Add or Remove Allowed Apps for Controlled Folder Access in Windows 10

Enable or Disable Controlled Folder Access in Windows 10

the jimmy said:

Bree, following your last link I believe this was introduced in a recent windows build.

Controlled Folder Access was introduced in build 16232, that was an Insider build prior to the public release in version 1709 build 16299. Little has change in 1803 build 17134 except that CFA is on by default now (it was off by default in 1709).

Also when an app is blocked, why didn't MS add the ability to click on an "allow" button so it could be added to the list so I don't need to fish around looking for the exe file.

That would be a useful addition, perhaps they will in subsequent versions? In the mean time, we have to add apps as best we can.

I have found that occasionally CFA starts to block more things than it should, a Restart cures that - try that first.

Yes, you could turn CFA off to let you move files, but as you say that reduces security. You could create a C:\Temp folder, you'd be able to move them there with CFA turned on because that would not be a protected folder. CFA should let File Explorer move them from there to your intended destination (it shouldn't block explorer.exe, if it does you need a Restart). Or you could give access to the app(s) that are being blocked.

The notifications that blocking has occurred are fleeting, and often don't show the full path to the binary file the needs to be added (it's not always the obvious .exe, sometimes it's a .bin).

The event viewer also logs the apps that were blocked. Open Event Viewer, look at the log for:
Applications and Services > Microsoft > Windows > Windows Defender > Operational
Event ID 1123 shows the name and full path of the executable that was blocked. In the Actions pane on the right you can 'Filter current log...' to help you find event ID 1123 quickly.