# Built .exe file won't run - no log generated (Windows, UE5.1) **URL:** \ **Category:** Platform & Builds\ **Tags:** unreal-engine, crash, question\ **Created:** [January 25, 2023, 8:12am UTC](https://forums.unrealengine.com/t/built-exe-file-wont-run-no-log-generated-windows-ue5-1/756482 "2023-01-25T08:12:39Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![alecdutch](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@alecdutch](https://forums.unrealengine.com/u/alecdutch)\ **Post date:** [January 25, 2023, 8:12am UTC](https://forums.unrealengine.com/t/built-exe-file-wont-run-no-log-generated-windows-ue5-1/756482/1 "2023-01-25T08:12:39Z")
Hi, I’ve packaged my game for Windows, but when I click the .exe it doesn’t run. It also doesn’t generate a log in the Saved folder as it normally would, so I don’t see a way to troubleshoot the issue. This issue seems similar to the one [here](https://forums.unrealengine.com/t/built-exe-file-wont-run-windows/652973), but it’s not quite the same problem (in the other case, a log file _was_ generated when they tried to open the .exe) It might be relevant that we recently upgraded our project to UE5.1. We previous were on UE5.02 and were able to build the game and run the .exe, but a lot of code and content has gone in since then- so the version upgrade may not be the issue. Things we’ve tried: - Disabling the Quixel Bridget plugin from editor \> Plugins (this fixed the issue in the other post, but not ours) - Building in shipping and development mode to see if we can generate a log in either mode (nope) - Attempting to run the .exe on a different PC (in case of a hardware issue on my side) - Deleting and regenerating the binary and intermediate files for all of our plugins (in case of corruption when upgrading) - Running the .exe from the command prompt - Checking the log during the build for errors (the only error in the log is the “not initialized properly” error discussed [here](https://forums.unrealengine.com/t/fs-test-id-is-not-initialized-properly/560690/5), which seems to be benign) Here’s the build log, in case there’s anything else in there that’s relevant: [1-24-23 build output log.txt](https://forums.unrealengine.com/uploads/short-url/7XtScF1x3spqvgXYjboXiUJHiLt.txt) (32.8 KB) Any help or ideas on how to troubleshoot would be much appreciated! ---
**Author:** ![Ari\_Epic](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/ari_epic/32/956630_2.png) [@Ari\_Epic](https://forums.unrealengine.com/u/Ari_Epic)\ **Post date:** [January 25, 2023, 4:09pm UTC](https://forums.unrealengine.com/t/built-exe-file-wont-run-no-log-generated-windows-ue5-1/756482/2 "2023-01-25T16:09:13Z")
This should help you with troubleshooting. Since you have the game fully packaged you can actually run the game from Visual Studio as if it was running in that packaged directory. In visual studio, switch your project configuration from `Development Editor` to a non-editor one, like `Development` (try that first) or `Shipping`. Then, add the `-basedir` launch command-line parameter, like this: `-basedir=C:\PathToYourGameFolder\Binaries\Win64`. ![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/8/d/2/8d233a993edd7d61e385fd3d5e734c8043b316a0.png) Now you can compile the game and run it but using the pak file, configs and everything as if it was running in that game folder, and you can debug exactly what is happening. ---
**Author:** ![alecdutch](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@alecdutch](https://forums.unrealengine.com/u/alecdutch)\ **Post date:** [January 25, 2023, 7:10pm UTC](https://forums.unrealengine.com/t/built-exe-file-wont-run-no-log-generated-windows-ue5-1/756482/3 "2023-01-25T19:10:59Z")
Thanks Ari! That’s a nifty trick- I was able to run the game from Visual Studio as you recommended. A breakpoint was hit immediately upon running the game, which I guess is why it didn’t generate a log outside Visual Studio. This is the error I saw in VS: **Assertion failed: Module [File:D:\build++UE5\Sync\Engine\Source\Runtime\Core\Private\Modules\ModuleManager.cpp] [Line: 393]** **ImageWrapper** The cause of the error was this line that attempted to load the ImageWrapper module at the top of a file. Removing this line allowed us to build the game and run it: ```auto //Module loading is not allowed outside of the main thread, so we tried to load the ImageWrapper module ahead of time //Source: https://nerivec.github.io/old-ue4-wiki/pages/asynchronous-image-loading-from-disk.html static IImageWrapperModule& ImageWrapperModule = FModuleManager::LoadModuleChecked(TEXT("ImageWrapper")); ``` ---
**Author:** ![Emrehan](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/emrehan/32/1194629_2.png) [@Emrehan](https://forums.unrealengine.com/u/Emrehan)\ **Post date:** [February 20, 2023, 12:47am UTC](https://forums.unrealengine.com/t/built-exe-file-wont-run-no-log-generated-windows-ue5-1/756482/4 "2023-02-20T00:47:27Z")
Thank you so much for sharing this, Ari! It helped a lot! ---
**Author:** ![Anonymous\_efcab960b6a805483e40a135aeef6c08](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/anonymous_efcab960b6a805483e40a135aeef6c08/32/607901_2.png) [@Anonymous\_efcab960b6a805483e40a135aeef6c08](https://forums.unrealengine.com/u/Anonymous_efcab960b6a805483e40a135aeef6c08)\ **Post date:** [March 17, 2024, 6:37am UTC](https://forums.unrealengine.com/t/built-exe-file-wont-run-no-log-generated-windows-ue5-1/756482/5 "2024-03-17T06:37:18Z")
I don’t understand，How is this different from an additional process。 ---
**Author:** ![AncientArtifact](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/ancientartifact/32/464847_2.png) [@AncientArtifact](https://forums.unrealengine.com/u/AncientArtifact)\ **Post date:** [November 26, 2025, 10:42pm UTC](https://forums.unrealengine.com/t/built-exe-file-wont-run-no-log-generated-windows-ue5-1/756482/6 "2025-11-26T22:42:58Z")
i was using UE 5.4, my issue was the Fab plugin, i removed it and it worked.