Quick answer: Unreal found the plugin, but not the compiled module (the .dll) it needs for your engine version. Work out where the plugin lives, then:
- Built into the engine (GameFeatures, Mutable…): verify the engine in the Epic Games Launcher, and open the project with the engine version it was made for.
- Installed into the engine from Fab or a developer (for example NVIDIA’s NIS): install the build made for your exact engine version.
- Your own or a downloaded C++ plugin in the project: build it from Visual Studio or Rider.
- Only fails in a packaged or Shipping build: check the module name in
IMPLEMENT_MODULE.
Don’t need the plugin? Disable it in your .uproject (shown below).
The exact errors people see
| Error | What it usually means |
|---|---|
| Plugin ‘GameFeatures’ failed to load because module ‘GameFeatures’ could not be found | A built-in engine plugin is missing its files. Your engine install is incomplete, or the project points at another engine version. |
| Plugin ‘NIS’ failed to load because module ‘NISShaders’ could not be found | NVIDIA Image Scaling isn’t installed for this engine version. |
| Plugin ‘PlatformAssetOverrides’ failed to load because module ‘PlatformAssetOverrides’ could not be found | The project enables a plugin that your engine build doesn’t include. It isn’t in the Launcher builds of UE 5.5 to 5.8 we checked. |
| Plugin ‘MyPlugin’ failed to load because module ‘MyPlugin’ could not be found | A C++ plugin that was never compiled for this engine version. |
The message ends with “Please ensure the plugin is properly installed, otherwise consider disabling the plugin for this project.” Both options are covered below.
Step 1: Find where the plugin lives
Search your engine and project folders for the plugin’s .uplugin file (for example GameFeatures.uplugin):
| Location | Type | Go to |
|---|---|---|
Engine/Plugins/… | Built into the engine | Step 2 |
Engine/Plugins/Marketplace/… | Installed into the engine from Fab or the Launcher | Step 3 |
YourProject/Plugins/… | Project plugin (yours or downloaded) | Step 4 |
| Not found anywhere | The project enables a plugin you don’t have | Disable it (Step 5) |
Step 2: Built-in engine plugins
- In the Epic Games Launcher, go to Unreal Engine > Library, click the arrow next to your engine version and choose Verify. This restores missing engine files.
- Make sure the project opens with the right engine: right-click the
.uprojectand choose Switch Unreal Engine version. - Using a source-built engine? Build the full editor target in your IDE, not only your game target, so every engine plugin gets compiled.
Step 3: Plugins installed into the engine
Plugins from Fab, the Launcher or a developer’s site (such as NVIDIA’s NIS plugin) are built per engine version. After an engine update, install the build for the new version. Delete the old copy first if it’s still in Engine/Plugins/Marketplace.
Step 4: Project plugins with C++ code
If YourProject/Plugins/MyPlugin/Binaries is missing or empty, the plugin was never compiled for this engine:
- Right-click the
.uprojectand choose Generate Visual Studio project files. - Open the
.slnand build Development Editor.
A Blueprint-only project can’t compile plugins. Download the build for your engine version, or see how to build Unreal Engine plugins from source.
Step 5: Disable the plugin if you don’t need it
When the editor won’t open, edit the .uproject in a text editor and turn the plugin off:
"Plugins": [
{
"Name": "NIS",
"Enabled": false
}
]
Error only in a packaged or Shipping build
If the editor works but the packaged game shows the error, the most likely cause is a typo in the module’s IMPLEMENT_MODULE line. The second argument must match the module name in the error exactly:
//Correct: the second argument is the module name from the error.
IMPLEMENT_MODULE(FCarWheels, CarWheels);
//Also correct: the class name doesn't matter, the module name does.
IMPLEMENT_MODULE(FSomeDifferentClassName, CarWheels);
//Wrong: the class name was used as the module name.
IMPLEMENT_MODULE(FCarWheels, FCarWheels);
Also check the module’s Type in the .uplugin. Modules of type Editor are not packaged, so runtime code must not depend on them.
Seeing “could not be loaded” instead?
“Could not be loaded” is a different problem: the DLL is there but Windows can’t load it. Examples are Plugin ‘Fab’ failed to load because module ‘Fab’ could not be loaded and Plugin ‘Mutable’ failed to load because module ‘MutableValidation’ could not be loaded. See Plugin failed to load: module could not be loaded.
FAQ
Will deleting Binaries and Intermediate fix it?
Only for C++ code you compile yourself, because it gets rebuilt. It won’t restore files for engine or downloaded plugins.
Why did this start after updating the engine?
Plugins installed into the engine are built for one engine version. Install the build for your new version.