File-association fix failing + Data\Manifests missing

Summary

If you have PowerToys installed with the “Source code files (Monaco)” add-on enabled, UnrealVersionSelector.exe may fail to fix project file associations.

If your project icon badges show “Other”, instead of the UE version, the issue might be that Launcher never created the Manifests folder inside %ProgramData%, which in turn prevents population of LauncherInstalled.dat.

What Type of Bug are you experiencing?

Other

Steps to Reproduce

Environment

  • Windows 11 26H2 (build 10.0.26300.9974), local administrator account, i7-13850HX, 32 GB RAM
  • Epic Games Launcher 20.3.8 (clean install)
  • UE 5.8.4 installed from Launcher to the default paths (clean install; no source build has ever been on the machine)
  • Microsoft PowerToys v0.102.3101.0 (see cause A)

Issues

A) Launcher prompts the “Project files not associated” error on every start-up; “Fix now” fails to update them.
B) Project icon badges in Launcher show “Other” instead of the engine version: e.g. “5.8”.
C) .uproject file icons in File Explorer are black instead of blue, and the Unreal-specific menu items on right click are missing.

Possible Causes & Workarounds

A: Unable to associate project files

  • PowerToys > File Management > File Explorer Add-ons > Source code files (Monaco) populates HKCU\Software\Classes\.uproject with shellex\{8895b1c6-b41f-4c1c-a562-0d564250836f}, whose default is {D8034CFA-F34B-41FE-AD45-62FCBB52A6DA}, to be able to preview UE project files in File Explorer
  • UnrealVersionSelector.exe starts by deleting HKCU\Software\Classes\.uproject
  • If it finds it populated, it will terminate with exit code 1 (unable to fix)

Workaround

  1. Disable Source code files (Monaco) in PowerToys.
  2. Open elevated PowerShell (right click > Run as administrator).
  3. Run reg delete "HKCU\Software\Classes\.uproject\shellex" /f to remove the leftover shellex stub if present: it will print an error if PowerToys has already removed it.
  4. Run reg query "HKCU\Software\Classes\.uproject" /s to check all keys are cleared. Expect: ERROR: The system was unable to find the specified registry key or value..
  5. Run $p = Start-Process "C:\Program Files\Epic Games\Launcher\Engine\Binaries\Win64\UnrealVersionSelector.exe" -ArgumentList "/fileassociations" -Wait -PassThru; $p.ExitCode to fix file associations.
  6. If the exit code is 0 and the “Couldn’t update file associations.” window didn’t come up, UnrealVersionSelector.exe was successful.

B: Project Icon Badge shows “Other”

  • Upon Launcher installation (unclear when/why), the C:\ProgramData\Epic\EpicGamesLauncher\Data\Manifests folder is NOT created.
  • At start-up, Launcher tries to write .item files inside that folder and fails due to PATH NOT FOUND.
  • According to my Procmon capture, no process ever tries to create that folder.
  • C:\ProgramData\Epic\UnrealEngineLauncher\LauncherInstalled.dat remains unpopulated.
  • A GUID is created under HKCU\Software\Epic Games\Unreal Engine\Builds.
  • When a project is created/opened, the same GUID is stamped into the EngineAssociation field inside the .uproject files.
  • The project icon badges will show “Other” instead of the engine version: e.g. “5.8”.

Workaround

  1. Create the missing folder C:\ProgramData\Epic\EpicGamesLauncher\Data\Manifests.
  2. Start Launcher. The .item files will populate the folder.
  3. Start UE from Launcher and create a template project: in my case LauncherInstalled.dat stayed empty until I had done this; afterwards it correctly listed UE_5.8.
  4. Close UE and Launcher and wait for the processes to clear from Task Manager.
  5. Reopen Launcher. The project icons should now show the correct version badge.

C: Black .uproject Icons in File Explorer

  • In File Explorer .uproject icons are black instead of blue, and the following menu items are missing on right click: “Launch game”, “Generate Visual Studio project files”, “Switch Unreal Engine version”.

Workaround

  • Unsure, but either workaround A or B solved this issue for me.

Possible long term fixes (for Epic Games team)

  • Launcher should create the C:\ProgramData\Epic\EpicGamesLauncher\Data\Manifests folder during installation.
  • If creating it fails, log an error code and tell the user, instead of carrying on with an empty LauncherInstalled.dat.
  • At Launcher start-up, if unable to locate the Manifests folder, Launcher should create it.
  • UnrealVersionSelector.exe should only remove or overwrite the keys it owns under HKCU\Software\Classes\.uproject, and leave other subkeys (e.g. PowerToys’ shellex preview handler) alone. Failing to delete the key shouldn’t abort the whole operation.
  • The “Couldn’t update file associations” dialog and Launcher log should include the failing call and its error code.

Expected Result

Details above.

Observed Result

Details above.

Affects Versions

5.8

Platform(s)

Windows

Additional Notes

Possibly related to:

Update: cause D, the warning returns after opening a project from Explorer

The “Project files not associated” warning came back after I opened a .uproject from Explorer, which is the same symptom @Graviton reported here: Epic Games Launcher - False “Project Files Not Associated” Warning After Opening .uproject via Windows Explorer [Repro + Procmon Evidence]

My findings (via Procmon + reg query)

  • Explorer creates HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.uproject\OpenWithList (a = UnrealVersionSelector.exe) on a double-click or right-click > “Launch game”, before UnrealVersionSelector.exe even starts. Opening from Launcher > Library or the editor’s recent projects doesn’t create it.
  • Launcher checks the legacy ...\FileExts\.uproject\UserChoice\Progid first (never UserChoiceLatest, which Explorer uses on Windows 11 26H2). If it’s missing, Launcher opens OpenWithList and shows the warning.
  • If UserChoice\Progid is Unreal.ProjectFile, Launcher never looks at OpenWithList, so there’s no warning even with OpenWithList present.
  • Deleting OpenWithList also clears the warning (“Fix now” in Launcher does the same), so the association itself was always valid.

Workaround (run once; survived a reboot)

:warning: Warning: these steps edit the Windows registry. Copy the commands exactly, run them in a normal (non-administrator) Command Prompt or PowerShell, and only touch the key shown. Use at your own risk.

Back it up first (this saves a file in the current folder):

reg export "HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.uproject" uproject-fileexts-backup.reg

To restore it, double-click the saved file.

Add the missing key:

reg add "HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.uproject\UserChoice" /v ProgId /t REG_SZ /d Unreal.ProjectFile /f

To undo:

reg delete "HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.uproject\UserChoice" /f

The key has no valid hash, so Windows may discard it later.

Additional long term fix (for Epic Games team)

  • Launcher should read UserChoiceLatest and not treat Windows’ own OpenWithList as a mismatch.