Hey there, Unity version: 2018.3.7f1 Recently I noticed that everytime I install a package from the PackageManager I get a bunch of errors saying that there occurs a DirectoryNotFoundException like this with the Addressable-Package: In that very example the file "PooledInstanceProviderBehavior.cs" does exist in my Unity Project. With the Addressable Package I also get a bunch of other DirectoryNotFoundException with other files. And apparently I also can't use the package itself, although it is installed but apparently it's not functional: Also, because of these errors I can't enter playmode in the Editor. Gotta remove the whole package for that. I noticed that this doesn't happen with a clean project which is located at the Desktop of my machine which implies that the directory can be found because the path is short enough. if that's the case and my other project fails to install the packages correctly because the paths of the files are getting to long: what can be done about that besides moving the whole project to another path?