Title: Plugin updates fail when MainGame association points to the Unreal Engine installation — verified workaround on UE 5.6.1
Summary
On my machine, Blueprint Assist updates under UE 5.6.1 are affected by the MainGame association fields in the plugin’s installation manifest.
When these fields point to the Unreal Engine installation, the Launcher targets UE_5.6 for the update request and subsequently fails to create an installation task. After changing only the three MainGame identifiers to reference Blueprint Assist itself, the Launcher correctly targeted the plugin, downloaded the update, and completed installation.
This confirms a local trigger condition and a working workaround. Without access to the Launcher’s internal implementation, I cannot determine the underlying code defect or whether this behavior relates to an intended design.
Controlled Test
The test changed only three fields in the following installation manifest:
C:\ProgramData\Epic\EpicGamesLauncher\Data\Manifests\DA0D75FC4C0199B7FA370A91A006D305.item
| Field |
Original value |
Test value |
MainGameCatalogNamespace |
ue |
89efe5924d3d467c839449ab6ab52e7f |
MainGameCatalogItemId |
73923380f4d944d5bcb6d77a0640d26d |
2f4af062b97742948633c711f669951c |
MainGameAppName |
UE_5.6 |
Blueprin0777d1c84a45V15 |
The manifest was backed up before modification. A comparison confirmed that these were the only three fields with semantic changes. HostInstallationGuid, CompatibleApps, and InstallLocation retained their original values.
The Epic Games Launcher was fully closed before editing the manifest.
Before the change
Multiple consecutive update attempts targeted UE_5.6 and failed with:
unable to create Install Task
After the change — 16:43:29
PopulateInstallConfigFromCurrent reported Blueprint Assist itself as MainAppId.
CreateInstallRequest targeted Blueprin0777d1c84a45V15.
- An installation task with
Action: Update was successfully created.
- The target build was
5.6.0-57374845.
Installation completed — 16:44:56
ProcessSuccess: TRUE
ErrorCode: OK
HandleTaskComplete referenced Blueprint Assist with AlertCode=[ok].
- The local
BlueprintAssist.uplugin file’s VersionName changed from 4.9.2 to 4.9.4.
- The installation manifest reported
bIsIncompleteInstall=false.
Expected Behavior
Updating an installed plugin should create an update task for that plugin and complete successfully, while preserving its association with the appropriate Unreal Engine installation.
Actual Behavior
With the original MainGame association pointing to UE_5.6, the update request targeted the engine and failed to create an installation task. Changing the association to reference the plugin itself allowed the update to complete.
Why the Issue May Recur
After installation completed, the logs explicitly showed ResolvePluginMainGameAssociation reassociating Blueprint Assist with UE_5.6. The Launcher automatically changed MainGameAppName back to UE_5.6.
The manifest modification is therefore a verified update workaround, not a permanent fix to the Launcher. Future updates may encounter the same issue.
The entire old manifest should not be restored after a successful update, because doing so would revert version information and other installation metadata.
Other Potentially Affected Installations
The following installed plugins also have MainGame associations pointing to their engine installations and have exhibited similar engine-targeted task failures or duplicate-task skipping during update attempts:
- UE 5.6: SteamCore PRO
- UE 5.8.2: Blueprint Assist, SteamCore PRO, and Electronic Nodes
The workaround has not yet been applied and validated individually for these installations. Successful updates have only been confirmed for Blueprint Assist under UE 5.6.1.
Troubleshooting Already Performed and Evidence Limitations
- Rebuilding the Launcher’s
webcache did not resolve the issue.
- The download queue was empty when checked.
- The installed plugins’
.item manifests were valid and parseable. The relevant manifests were not marked as incomplete installations.
Item is null and Found 0 Mod to UPDATE also appeared during the successful controlled test. These messages alone should therefore not be treated as evidence of the root cause.
- The desktop automation tool could not obtain a controllable Launcher window. I clicked the update button manually, and the outcome was verified using both local logs and the installed plugin version.
Request for Investigation
Please investigate how plugin update requests resolve their target from the MainGame association fields, and why an association with the host engine causes the update request to target the engine and fail in this case.
Please also investigate whether the post-installation ResolvePluginMainGameAssociation step restores the condition that caused the failure, potentially allowing the issue to recur on subsequent updates.