It is not recommended to disable EOSBootstrapper.exe. This file is generated when you configure the EOS Plugin Configuration, and it is required for logging in through the Epic Games Portal.
If the project does not include EOSBootstrapper.exe , you will not be able to authenticate with the Epic Portal.
In case you do not require any of its functionalities, you could instead use EOS disabling, as described here: Disable plugin per platform
“Games distributed on the Epic Games Store do not integrate with the EOS service redistributable or the EOS bootstrapper, as the functionality provided by these components is built into the Epic Games Launcher.”
Does we still need the EOS bootstrapper if we distribute through Epic Games Store?
If I understand correctly we do not need authentication with the Epic Portal, because we will authenticate through Epic Games Launcher with exchange codes. Please correct me If I’m wrong.
You’re right regarding Epic Games Store builds: EGS titles do not require EOSBootstrapper.exe nor the EOS Service Redistributable, because the Epic Games Launcher provides those components for store-distributed games. Instead, EGS titles should authenticate via the Exchange Code flow passed by the Launcher on startup.
Important caveat: if you simply delete EOSBootstrapper.exe (and its companion files) from a PEW-generated Windows build without reconfiguring the plugin/launch target, your build may fail to start—because PEW’s default layout expects to launch through the bootstrapper. So the goal is not just “delete files”, but “launch your game directly” for the EGS profile.
What to do
Use Exchange Code auth for EGS
Stop relying on the bootstrapper for the EGS build profile
There isn’t a visible “don’t generate bootstrapper” toggle. Two safe approaches:
A. Build-time configuration: ensure your launch target for EGS points directly to your game executable (not EOSBootstrapper.exe ).
B. Post-build step for the EGS profile: keep your normal PEW build, then in a PostProcessBuild script for your EGS configuration:
Keep the EOS SDK DLLs (e.g., EOSSDK-Win64-Shipping.dll ) in the build; those are still needed by the SDK.