"Failed to open descriptor file" error when opening uproject file on local network - solution

for people who have the habit of opening unreal files that are on another computer on a network, and are having this problem here with UE 5.1:
“Failed to open descriptor file”
image

I’ll leave here the solution I found, very simple. You just have to go to the folder where your project is, right-click and select the option “Map network drive”

You will choose the letter of the drive you want to create, leave the option “Reconnect at sign-in” checked and click on finish.
image

Windows will create a location as if it were a drive on the computer itself, opening the file through that drive I no longer had the “Failed to open descriptor file” problem, everything worked correctly.
image

4 Likes

I fixed this by simply specifying the full path to the .uproject, starting from the drive.

1 Like

how do you specify the full path to the .uproject, from where?

I use this command:

"C:\Program Files\Epic Games\UE_5.2\Engine\Binaries\Win64\UnrealEditor.exe" "C:\MyProjectFolder\MyProject.uproject" -run=DerivedDataCache -fill

you can add -ddc=noshared to the end if you are working on the project alone and using one pc

1 Like

how do you specify a path for us dummies

1 Like

Yes, for dummies :smiley:
I had the same error but in different situation, I was working locally on my PC, not in network. Opening the uproject file directly worked, but when I launched Local Windows Debugger in Visual Studio then the error occured.

I managed to fix my problem the “hard way” :smiley:
I removed the .sln and .vsconfig files and removed the directories: .vs, Binaries, DerivedDataCache, Intermediate and Saved.
Then I generated Visual Studio files again and it works now :smiley:
Yes I know, this was brute force but I got the job done :wink:

6 Likes

This error also occurs when you launch to your connected device and forget to launch in development mode. You cannot launch in shipping mode or you get this error.

1 Like

Had this issue myself which directed me to this thread.

In my case it was pretty simple to solve. For me, the issue was that the project was looking at the D-drive whereas my project currently exists on my E-drive. I could simply open the Properties of the project from Visual Studio by right-clicking, navigate to Debugging, and in the Command Arguments, I saw it was looking for the uproject on the D-drive. I simply had to change this to the E-drive.

Problem solved for me :slight_smile: