2019.3.4 Builds But EXE fails to run (side-by-side config is incorrect....)

Unity Engine
,
1

I just updated to 2019.3.4 and did a build (Using Mono, Not I IL2CPP).

Build completed without errors but when I run the resulting .exe I get this:

4986818--486581--Capture.JPG

Not sure where to go from here. Things worked fine with 2019.3.3

2

I am getting this as well on 2019.3.0b4

3

Hey, investigating ASAP.

While I do that, do you have any more information? What’s your exact OS version? Does this happen on an empty Unity project?

4

Hey I cannot reproduce this. Do you by any chance have some odd DLLs next to that executable? Did you try building to an empty folder?

What are your build settings?

5

I did have this problem too but then switched to the 2020 alpha. I didn’t want to lose too much time figuring this out on my project, sorry should’ve at least saved the log… The problem did NOT occur in beta 3 only in 4.
In my case unity actually crashed right after opening the folder with the exe but the exe was half as big as usual and didn’t have the icon assigned yet etc. My build settings were Windows x86 x64 and all of the bools under that to false ( compression LZ4 ).
No DLLs except UnityPlayer.dll next to the exe, didn’t try empty folder.
Win10 pro 10.0.18362

EDIT: Seems somebody already found a simple culprit:

6

Yeah, setting any texture2d in there corrupts the exe. More specifically, corrupts the manifest xml inside.
(Case 1185899) is the submitted error report.

I tried this on two windows 10 computers and a windows 8 one.

7

Thanks, we’ll take a look!