Epic Games Launcher - False “Project Files Not Associated” Warning After Opening .uproject via Windows Explorer [Repro + Procmon Evidence]

Summary

Epic Games Launcher repeatedly displays the “Project files not associated” warning even though Windows correctly associates .uproject files with Unreal.ProjectFile and UnrealVersionSelector.exe.

The issue can be reproduced by opening a .uproject file through Windows Explorer. Process Monitor confirms that Explorer creates the per-user OpenWithList registry key. On a subsequent Launcher startup, the association warning reappears.

Clicking “Fix Now” runs UnrealVersionSelector.exe /fileassociations, which rewrites the already-correct associations and deletes OpenWithList. The warning disappears until the project is opened through Windows Explorer again.

What Type of Bug are you experiencing?

Other

Steps to Reproduce

  1. Start Epic Games Launcher on Windows 11 and click “Fix Now” if the file-association warning appears.

  2. Exit the Launcher completely.

  3. Verify that the standard .uproject association is valid and that the following registry key does not exist:

    HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.uproject\OpenWithList

  4. Restart Epic Games Launcher. No association warning is displayed.

  5. Exit the Launcher again.

  6. Double-click an existing .uproject file in Windows Explorer and allow Unreal Editor to open.

  7. Windows Explorer creates OpenWithList and writes:

    a = UnrealVersionSelector.exe

    MRUList = a

  8. Close Unreal Editor and restart Epic Games Launcher.

  9. The “Project files not associated” warning appears again.

  10. Select “No Thanks”, exit, and restart the Launcher. The warning reappears.

  11. Select “Fix Now”. The association utility deletes OpenWithList, and the next Launcher startup completes without the warning.

The sequence was reproduced without manually modifying the Windows registry.

Expected Result

Epic Games Launcher should recognize the existing, valid .uproject file association and should not display the “Project files not associated” warning.

Opening a project normally through Windows Explorer should not cause the Launcher to treat an otherwise valid file association as missing or invalid.

Observed Result

Epic Games Launcher displays the association warning after a
.uproject file is opened through Windows Explorer.

Procmon confirms the following sequence:

Explorer.EXE (PID 15268)
18:06:39.5548726
RegCreateKey: SUCCESS
Disposition: REG_CREATED_NEW_KEY
HKCU\Software\Microsoft\Windows\CurrentVersion
Explorer\FileExts.uproject\OpenWithList

18:06:39.7024944
RegSetValue: SUCCESS
OpenWithList\a = UnrealVersionSelector.exe

18:06:39.7025739
RegSetValue: SUCCESS
OpenWithList\MRUList = a

During Launcher startup, HKCR.uproject correctly resolves to
Unreal.ProjectFile, and the shell open command correctly references
UnrealVersionSelector.exe.

Clicking “Fix Now” launches:

UnrealVersionSelector.exe /fileassociations

Procmon confirms:

14:56:05.3816544
Process: UnrealVersionSelector.exe
RegDeleteKey: SUCCESS
HKCU\Software\Microsoft\Windows\CurrentVersion
Explorer\FileExts.uproject\OpenWithList

The process exits with status 0.

After restarting Epic Games Launcher, the warning no longer appears.

Affects Versions

5.8

Platform(s)

Windows

Upload an image

Additional Notes

Additional diagnostics:

Windows 11 x64
Unreal Engine 5.8.x
Epic Games Launcher

Verified:

  • assoc .uproject = Unreal.ProjectFile
  • ftype Unreal.ProjectFile points to UnrealVersionSelector.exe
  • AssocQueryStringW resolves the expected executable.
  • HKLM file-association exports are identical before and after Fix Now.
  • UserChoice is absent during both successful and problematic startups.
  • OpenWithList is present during the reproduced warning.
  • OpenWithList is absent during the tested warning-free startups.
  • No registry access-denied error was observed in the relevant
    file-association operations.

This suggests that the Launcher may be incorrectly interpreting
per-user OpenWithList information when validating the .uproject
association. This is a hypothesis, not a confirmed root cause.

The issue was first noticed several days after resolving an unrelated
UE 5.8.x Launcher Resume Loop issue, around a subsequent Launcher
startup or update. No causal connection has been established.

@Graviton, likely unrelated, but I’ve had a tangential issue with file associations and have just posted a bug report with workarounds here:

I hope it helps you or someone landing on your report.

@Graviton, after fixing my other issues, I was able to reproduce yours on my machine (Win 11 26H2, Launcher 20.3.8, UE 5.8.4) and I agree with your hypothesis.

In my tests:

  • Right-click > “Launch game” in Explorer creates OpenWithList too. Opening from Launcher > Library or the editor’s recent projects doesn’t.
  • 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. If it’s Unreal.ProjectFile, Launcher never looks at OpenWithList.

A workaround until Epic fixes this (run once, survived a reboot):

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. Launcher should read UserChoiceLatest and not treat OpenWithList as a mismatch. I’ll add these findings in my thread too.

@FiloFederici Thanks for independently reproducing this issue and for the additional investigation!

Your findings are particularly helpful, especially the distinction between opening .uproject files through Windows Explorer and launching projects directly from the Epic Games Launcher or Unreal Editor.

My Procmon captures confirm the following sequence:

  1. Windows Explorer creates OpenWithList when opening a .uproject file and writes:

    • a = UnrealVersionSelector.exe

    • MRUList = a

  2. On the next Epic Games Launcher startup, the “Project files not associated” warning appears, despite valid file associations.

  3. Clicking No Thanks leaves the warning reproducible on subsequent startups.

  4. Clicking Fix Now executes UnrealVersionSelector.exe /fileassociations, which deletes OpenWithList and exits successfully (status 0).

  5. The next Launcher startup completes without the warning.

I reproduced this complete cycle multiple times without manually modifying the registry.

Regarding your UserChoiceLatest observation:

I checked my Windows 11 installation and confirmed:

  • UserChoice: NOT FOUND

  • UserChoiceLatest\ProgId: Unreal.ProjectFile

  • UserChoiceLatest\Hash: Present

  • OpenWithList: Present after opening a .uproject through Explorer

  • OpenWithProgids: Contains Unreal.ProjectFile

I also rechecked two Procmon startup captures: one with the warning and one without it.

In both captures, Epic Games Launcher queries the legacy UserChoice location, which returns NAME NOT FOUND. Neither capture shows a visible access to UserChoiceLatest.

This supports your hypothesis that the Launcher may not fully account for the newer Windows 11 file-association mechanism.

The OpenWithList correlation is reproducible, although we cannot yet confirm the exact validation condition inside the Launcher.

I would also avoid manually creating an unhashed UserChoice entry, since the existing Windows association works correctly.

Thanks again for confirming this on a separate system and identifying another potential part of the problem!