Problem appeared since I reinstalled the Editor a month back.
I have 2 drives , C:(SSD-1) and P:(SSD-2)
ISSUE- After I start Unreal, I can’t read/write from the drive P:. Until I restart the computer.
Even Unreal can’t access the drive as it was installed in that drive previously and couldn’t r/w its own files and kept crashing.
Now I tried installing on the C: drive and it’s not crashing but issue with drive P: still exists.
-I checked disabling the antivirus but it’s not causing it.
-All engine versions behaving the same way.
NOTE-
I made a symbolic link the last time I was installing Unreal using mklink command cause the C drive was getting full.
Like this - Symbolic link from C to D Drive
I have a strong suspicion that this could be causing it but I can’t figure it out.
Please help! Thanks in advance!
Try using an explicit Junction instead of a mklink Symbolic Link. The easiest way to make this happen is using PowerShell instead of Command Prompt. The built-in version of powershell will suffice for this.
Below, target means where the files actually are (-Value), and source is the shortcut (-Name).
This makes a folder D:\NewUnrealEngine which the OS will resolve to C:\Users\NAME\AppData\Local\UnrealEngine, BUT it will still appear to be on the D drive. I use this whenever I have projects stored on another filesystem and I want them to access a specific build of the Engine by looking for UnrealEngine in the project’s parent directory.
Note that if your files are on a network share, you’ll need to map them to a drive letter first to use this method.
You should see the little shortcut icon on the folder once done. You need to delete the existing SymbolicLink first before you do this, or you’ll get an error.
If you keep having problems, then I suspect a bigger problem in the underlying hardware.
