Rider cannot load its own assemblies when installed to a symlink path on Windows

October 26, 2026 11:17 Updated

If you install Rider to a path that's represented by a symlink, it won't be able to load some of its .NET components.

It will not support any advanced features in the editor, and will show a message "Code analysis has been suspended". The following error will be written to the IDE log file:

Could not load file or assembly 'file:///.dll' or one of its dependencies. Operation is not supported. (Exception from HRESULT: 0x80131515)
An attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed in previous versions of the .NET Framework.
This release of the .NET Framework does not enable CAS policy by default, so this load may be dangerous.
If this load is not intended to sandbox the assembly, please enable the loadFromRemoteSources switch. See http://go.microsoft.com/fwlink/?LinkId=155569 for more information.

The solution is to reinstall Rider to a path not containing any symlinks.