Search in
Sort by:

Question Status:

Search help

  • Simple searches use one or more words. Separate the words with spaces (cat dog) to search cat,dog or both. Separate the words with plus signs (cat +dog) to search for items that may contain cat but must contain dog.
  • You can further refine your search on the search results page, where you can search by keywords, author, topic. These can be combined with each other. Examples
    • cat dog --matches anything with cat,dog or both
    • cat +dog --searches for cat +dog where dog is a mandatory term
    • cat -dog -- searches for cat excluding any result containing dog
    • [cats] —will restrict your search to results with topic named "cats"
    • [cats] [dogs] —will restrict your search to results with both topics, "cats", and "dogs"

[Closed] Failed to open descriptor file - previous solution N/A

I'm using 4.10.4, the standard binary version of the engine from the launcher. The project is blueprint only. We have Visual Studio Community 2015 with Common Tools and Visual C++ tools included. We are using Perforce. The project is completely up to date with all files checked in, and was originally created on the same machine we are using to package it.

After running a shipping build we continuously get this error "Failed to open descriptor file '.../../../PROJECTNAME-Shipping/PROJECTNAME-Shipping.uproject'

There is a solution to this problem already listed in the forum, but it is not working for us. It mentions navigating to WindowsNoEditor/Engine/Binaries/Win64 (or32)/ and renaming the '.uproject' found there. We are not finding that '.uproject' file. As far as I can tell there is no '.uproject' file being included anywhere in the WindowsNoEditor directory after packaging.

The only file in the above directory is CrashReportClient.exe. If we disable 'Include Crash Reporter' in our package settings, that directory doesn't get created at all.

I cannot include an image, but here is a list of our package settings:

Build Configuration: Shipping Staging Directory: A folder on Desktop Full Rebuild: True For Distribution: True Include Debug Files: False

Use Pak File: True Generate Chunks: False Build Http Chunk install Data: False

Include Prerequisites: True

Cook everything in the project content directory: True

Just like with the other people experiencing this problem, a development build works fine. It's only the shipping builds where we are seeing this issue. It's been a problem for us since 4.9 and have opted to do very many projects in Unity as a result. I am advocating heavily for UE4, but this problem has been disruptive.

Any help would be greatly appreciated.

Product Version: UE 4.10
more ▼

asked Mar 02 '16 at 08:20 PM in Packaging & Deployment

avatar image

6 1 2 3

avatar image Kalan Mar 02 '16 at 08:51 PM

We've also attempted to do a shipping build of the sidescroller template using the same settings and are running in to the same problem.

There must be something very basic we are missing here, but we aren't seeing it.

Even trying to package a very simple project without source control, no assets or package targets are crossing drives, no permissions issues, we still hit this.

avatar image MrMagarac Mar 03 '16 at 02:15 PM

I have the same issue, when i build fresh First Person template following this guide https://docs.unrealengine.com/latest/INT/Engine/Deployment/Releasing/index.html i get this error on step 7. I have no idea what to do because i am complete newbie, i was trying to build project then create patch for it but i can't get this to work. alt text

untitled.jpg (18.9 kB)
avatar image VictorBurgos Mar 07 '16 at 01:13 PM

Having the same problem shipping with Win64... Must be a new issue with 4.10.4

(comments are locked)
10|2000 characters needed characters left
Viewable by all users

The question has been closed Aug 12 '16 at 07:44 PM by Steve Hardister for the following reason:

The question is answered, right answer was accepted

1 answer: sort voted first

Ok here is the answer, at least for my issue, you need to remove "-Win64-Shipping" from exe file:


More info here:


Im using UE 4.10.4

more ▼

answered Mar 03 '16 at 03:39 PM

avatar image

51 3 4 6

avatar image Kalan Mar 03 '16 at 10:04 PM

This kind of works.

When I rename that file, and launch using that exe file, the program runs. That's great.

But with the development build, we are able to launch using the PROJECTNAME.exe file that shows up in the 'WindowsNoEditor' folder after packaging. With the shipping build, we can never launch using that exe. Even after renaming the exe file found in 'WindowsNoEditor\PROJECT\Binaries\Win64\' we still get this error:

Couldn't Start: pathToFileIJustLaunched + "-Win64-Shipping.exe" CreateProcess() returned 2.

What is happening here that is causing the difference?

avatar image Tom H Apr 19 '16 at 02:46 PM

I've written a bat script that should save you a little time here. Needs a small edit for project name and rename file extension to .bat is all. Attached to my answer here.

(comments are locked)
10|2000 characters needed characters left
Viewable by all users

Follow this question

Once you sign in you will be able to subscribe for any updates here

Answers to this question