CreateProcess() returned 570

Development Platform & Builds
, ,
1

Hello everyone,

This is not my first time packaging, but this is the first time I get this error. What’s weird is that I only changed a post process volume (to fix a lighting problem) before packaging it again and now it gives this error upon trying to execute the file. Anyone knows how to fix this?

9 Likes
2

It’s been some time since this question was asked, but I ran into a problem and this was my solution:

I had to go to Edit > Project settings > Packaging, then scroll down to the “Project” tab and find “Full Rebuild” Tick that to true and that fixed my issue.

324424-untitled.png

27 Likes
3

thnx for the solution!

4

Thanks, full rebuild worked!

5

I was getting a similar error in 4.27:

createprocess() returned c1

Which the “Full Rebuild” checkmark also fixed. Thank you for posting the solution!

6

Did not work for me :frowning: . Error appears when clicking on the executable of the package (4.27)

I don’t know what to do.

A pop up appears with the following message:

================

Couldn’t start: “F:\path…\Projectname.exe” Projectname CreateProcess() returned 570.

Any ideas? Thank you!!

7

Ok it seems that some files were corrupted, maybe when interrupting a Launch Process that was taking too long. Each package after that gave error. Fortunately I’d backed up the whole project the day before, and restoring from the backup copy did the trick.

8

This solution worked for me after a package kept crashing with CreateProcess() returned 2, thanks a bunch for sharing. :3

9

Thank you!

10

Thank you SO much, I thought this was going to take hours to troubleshoot.

11

Thanks for this solution, worked perfectly on my end

12

Supeb This Working Thanks

13

thx, even worked with 5.2 today

14

Thanks this worked

15

Ran into this issue and Full Rebuild didn’t seem to fix it.

I had an error during the compile process that looked something like this:

LogClass: Error: FloatProperty FLandscapeHeightPatchConvertToNativeParams::ZeroInEncoding is not initialized properly. Module:LandscapePatch File:Public/LandscapeTexturePatchPS.h

which the editor seemed fine with all the way through to the point of launching the .exe.

Finally resolved it by adding a constructor to a USTRUCT and initializing default values for all it’s fields after reading this: Structs, USTRUCTS(), They’re Awesome - UE4: Guidebook (gg-labs.com)

16

Hi I have some insight into this problem, I ran into this myself testing out different builds for marketplace plugins.

Error 570 is a windows specific application error. The reason this happens in the context of unreal engine is most likely due to the following →

A module you built (project or plugin) was built with a different toolchain than what your engine was built with.

Most people use the binary version of the engine you get from the epic games launcher. This means your engine is built with a very specific toolchain (again on windows only). The toolchain is derived from the visual studio version used to build the engine, which is usually the lowest compatible visual studio version advertised for the engine version.

The reason full rebuild may work for some, is that you have the correct toolchain the engine was built with, or you have the source build of the engine, with any of the compatible toolchains.

The reason is doesn’t work for some is that you aren’t using a c++ project and so full rebuild doesn’t really effect you, or you have a c++ project but have the wrong toolchain your engine was built with, and you don’t have a source build of the engine to rebuild with this new toolchain.

This really only occurs when you have versions of the engine that are dually supported by different toolchains. For example: UE5.1 can be built with VS2019 and VS2022, but is shipped only for the 2019 toolchain. For engine versions that only support one toolchain, there can only be one!

Hope this helps clear up issues for everyone, and understand why it was occurring.

1 Like