"Could not load file or assembly Operation is not supported." On Mapped Network Drive

I have tried solutions from the following posts/sites:

• Could not load file or assembly Operation is not supported. (Exception from HRESULT: 0x80131515)
• Could not load file or assembly in VS2017 with IIS express
• Visual Studio "Could not load file or assembly. Operation is not supported" error in Release mode
• http://www.clearmindsoftware.com/post/Resolution-Error-Could-not-load-file-or-assembly-file5c5cserver5cpath5cfiledll-or-one-of-its-dependencies-(0x80131515)

Error:

Could not load file or assembly 'file://\[networkdrive]\Programming\Misc Projects\CSVSerializer\UnitTestProject1\bin\Debug\UnitTestProject1.dll' or one of its dependencies. Operation is not supported. (Exception from HRESULT: 0x80131515)

This error occurs when trying to discover tests on my solution on a mapped network drive, on multiple devices, this occurs in vs2015 and vs2017. If I copy the solution and directories to the device itself, it works fine.

What I've tried:

• Unblocking file: The DLLs are not blocked
• Readonly: Not marked as readonly
• loadFromRemoteSources: Enabled on vs2015 & 2017 on all devices
• Using UNC paths instead of a mapped drive

Why a network drive?

To keep my project files in a central, redundant, backed up location that I can access from multiple devices without having to pull from source control and rebuild each time. To save space on VMs for large projects and assemblies.

This seems as a supported, and even anticipated way to use a project considering there is a VS flag just for this https://docs.microsoft.com/en-us/dotnet/framework/configure-apps/file-schema/runtime/loadfromremotesources-element

Why is this happening? Is there more info for this error? what can I do to troubleshoot the problem?