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

**URL:** <https://forums.unrealengine.com/t/epic-games-launcher-false-project-files-not-associated-warning-after-opening-uproject-via-windows-explorer-repro-procmon-evidence/2856223>\
**Category:** Issues and Bug Reporting (Unreal Engine)\
**Tags:** unreal-engine\
**Created:** [November 15, 2026, 5:57pm UTC](https://forums.unrealengine.com/t/epic-games-launcher-false-project-files-not-associated-warning-after-opening-uproject-via-windows-explorer-repro-procmon-evidence/2856223 "2026-11-15T17:57:44Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Graviton](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/graviton/32/1200961_2.png) [@Graviton](https://forums.unrealengine.com/u/Graviton)\
**Post date:** [November 15, 2026, 5:57pm UTC](https://forums.unrealengine.com/t/epic-games-launcher-false-project-files-not-associated-warning-after-opening-uproject-via-windows-explorer-repro-procmon-evidence/2856223/1 "2026-11-15T17:57:45Z")

</div>

### 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:

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:

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

 ![ProjectFilesNotAssociated.png](https://d3kjluh73b9h9o.cloudfront.net/original/4X/e/f/0/ef09b24c3a66d2d0f63454cf652e2d063ab807fb.png)

### 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.

---

<div class="post-metadata">

**Author:** ![FiloFederici](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/filofederici/32/1198158_2.png) [@FiloFederici](https://forums.unrealengine.com/u/FiloFederici)\
**Post date:** [November 15, 2026, 9:38pm UTC](https://forums.unrealengine.com/t/epic-games-launcher-false-project-files-not-associated-warning-after-opening-uproject-via-windows-explorer-repro-procmon-evidence/2856223/2 "2026-11-15T21:38:13Z")

</div>

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

> [@File-association fix failing + Data\\Manifests missing](https://forums.unrealengine.com/t/file-association-fix-failing-data-manifests-missing/2856274):
>
> 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…

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

---

<div class="post-metadata">

**Author:** ![FiloFederici](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/filofederici/32/1198158_2.png) [@FiloFederici](https://forums.unrealengine.com/u/FiloFederici)\
**Post date:** [November 16, 2026, 12:19am UTC](https://forums.unrealengine.com/t/epic-games-launcher-false-project-files-not-associated-warning-after-opening-uproject-via-windows-explorer-repro-procmon-evidence/2856223/3 "2026-11-16T00:19:25Z")

</div>

@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):**

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

```

To undo:

```auto
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.

---

<div class="post-metadata">

**Author:** ![Graviton](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/graviton/32/1200961_2.png) [@Graviton](https://forums.unrealengine.com/u/Graviton)\
**Post date:** [November 16, 2026, 5:17pm UTC](https://forums.unrealengine.com/t/epic-games-launcher-false-project-files-not-associated-warning-after-opening-uproject-via-windows-explorer-repro-procmon-evidence/2856223/4 "2026-11-16T17:17:28Z")

</div>

@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:

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!**
