AlphaRes Doesn’t Detect My Fortnite Install: 6 Fixes (2026)

Fix #1: Verify the Epic Games Launcher Install Path

Symptom: AlphaRes opens cleanly but reports “Fortnite not detected” or shows a blank install path field. Epic Games launcher itself opens normally and Fortnite is playable. The issue is path-side rather than file-side.

Cause: Fortnite was installed to a non-default drive or a path containing characters that confuse auto-detection. Examples include D:\Games\Fortnite, an external SSD assigned a drive letter that changes between sessions, or a folder name with a trailing space, an emoji, or an accented character.

Steps

1. Open the Epic Games launcher. Click the profile icon in the upper-right corner and choose Settings.
2. Scroll to the Manage Games section. Locate the Fortnite entry and read the Install Location field.
3. If the path resolves under a clean ASCII drive (for example C:\Program Files\Epic Games\Fortnite or D:\Epic Games\Fortnite), the launcher itself is configured correctly and the issue is with AlphaRes detection logic; proceed to Fix #2.
4. If the path contains spaces inside folder names (for example D:\My Games\Fortnite Battle Royale), special characters, an OneDrive-synced parent, or a removed drive letter, that is the structural cause; jump to Fix #4 to reinstall to a clean default path.
5. Confirm Fortnite has been launched at least once after the most recent install. The first launch is what creates GameUserSettings.ini; without it, AlphaRes has nothing to detect.

Fix #2: Manually Configure the AlphaRes Path

Symptom: the diagnostic above confirmed GameUserSettings.ini exists at the standard %LocalAppData% path, yet AlphaRes still reports “Fortnite not detected.” This is the single most common detection scenario when Fortnite is installed on a custom drive: the game files are on D:\, but the config file remains on C:\, and AlphaRes cannot bridge the two automatically.

Cause: Fortnite separates game data (binaries, pak files, shaders) from user config (resolution, keybinds, sensitivity). The game data follows the Epic Games launcher install path, but the user config is always written under %LocalAppData%, which resolves to C:\Users\<name>\AppData\Local\ regardless of where the game itself lives. When AlphaRes auto-detection assumes the config sits next to the game files, it fails on custom-drive installs even though the file is fine.

Steps

1. Right-click alphares_x64.exe in File Explorer. Choose Run as administrator. Accept the UAC prompt that appears.
2. The AlphaRes window opens. Click the path or browse field next to the install path display.
3. In the file picker, paste this path into the address bar and press Enter: %LocalAppData%\FortniteGame\Saved\Config\WindowsClient\.
4. Select GameUserSettings.ini from the listing and click Open. AlphaRes records the path for future launches.
5. Set the desired Width and Height values in the AlphaRes UI, tick the Read-only checkbox, and click Apply. The utility writes the new resolution into the file and then locks the file with the read-only attribute so Fortnite patches cannot rewrite it.
6. Launch Fortnite from the Epic Games launcher and confirm the resolution applied. The first launch after a resolution change can take a few seconds longer while the engine reads the new config.

If the manual path step does not stick across AlphaRes restarts (the path field clears on next launch), the deeper cause is a permission issue on the AlphaRes settings cache; the settings not saving guide covers that scenario. For the standard “Fortnite is on D:\ and AlphaRes cannot find it” case, the manual path step is permanent and only needs to be done once.

Fix #3: Run AlphaRes as Administrator

Symptom: the file picker in Fix #2 cannot reach %LocalAppData%\FortniteGame\Saved\Config\WindowsClient\, or the folder is visible but appears empty even though File Explorer (in a separate window) shows GameUserSettings.ini sitting there. The issue is access-side, not path-side.

Cause: Controlled folder access (a Defender feature that protects user-data folders from unauthorized writes) is enabled, or the Fortnite config folder has had its permissions hardened by a previous security tool. Standard-user processes can be denied read access to a folder that Explorer can still browse with elevated tokens. AlphaRes, running unelevated, sees an empty directory because it does not have the right to enumerate the contents.

Steps

1. Close any open AlphaRes window.
2. Right-click alphares_x64.exe in File Explorer. Choose Run as administrator. Accept the UAC prompt; the dialog will mention an unknown publisher, which is expected behavior for an unsigned utility.
3. The AlphaRes window opens with elevated privileges. Repeat the manual path step from Fix #2.
4. If elevated AlphaRes still cannot enumerate the config folder, open Windows Security > Virus & threat protection > Manage ransomware protection and confirm Controlled folder access is set to Off, or add alphares_x64.exe to the allowed-apps list under Allow an app through Controlled folder access.
5. To make elevation permanent, right-click the EXE, choose Properties > Compatibility, tick Run this program as an administrator, and click Apply. Subsequent double-clicks then automatically request elevation.

Most Fortnite players never need this fix; the default Windows 11 24H2 configuration grants standard-user processes read access to %LocalAppData% without a UAC prompt. Elevation only matters when Controlled folder access has been turned on manually, when a security suite has applied a custom hardening profile, or when the user account itself was created with non-default permissions.

Fix #4: Reinstall Fortnite to the Default Path

Symptom: the Epic Games launcher reports the Fortnite install path under an OneDrive-synced parent folder, a network share, or a path with emoji, accented characters, or trailing whitespace. AlphaRes detection consistently fails even after the manual path step in Fix #2, and the underlying GameUserSettings.ini file does not appear at the standard %LocalAppData% location either.

Cause: Fortnite was installed to a path that breaks one of the assumptions made by either the Epic launcher or the Fortnite first-launch routine. OneDrive-synced folders are a frequent offender because they treat files as placeholders until accessed, which interferes with the read-only attribute AlphaRes needs to apply. Network shares and removable drives can disconnect between sessions and leave the config writes failing silently.

Steps

1. Open the Epic Games launcher. Click the Library tab. Hover over the Fortnite tile and click the three-dot menu, then choose Uninstall. Wait for the uninstall to complete.
2. Click Install on the Fortnite library tile again. When the destination dialog opens, choose Browse and pick a clean default path on the C: drive: C:\Program Files\Epic Games\Fortnite is the standard default. Avoid any folder under OneDrive, any folder containing non-ASCII characters, and any path on a removable drive.
3. Wait for the download to complete. Fortnite is roughly 30-50 GB depending on the chapter and any optional packs; the reinstall is the slowest step in this guide.
4. Launch Fortnite once after install completes. Click through the Epic Games launcher Play button and let the game reach the lobby. This first launch creates GameUserSettings.ini at the standard %LocalAppData% path.
5. Quit Fortnite. Open AlphaRes; detection should now succeed and the install path field should auto-populate.

Reinstalling is the structural fix for path-related detection issues that the manual path step in Fix #2 cannot resolve. The locker progression, account-bound cosmetics, and Battle Pass progress are all stored on Epic Games servers and survive the reinstall; only the local game files and the local resolution settings are recreated.

Fix #5: Check the Epic Launcher Registry Key

Symptom: Epic Games launcher itself opens correctly and Fortnite is installed, but AlphaRes reports “Fortnite not detected” even after a reinstall. The detection failure persists across reboots and across multiple AlphaRes versions. This points to a registry-side problem rather than a file-side one.

Cause: a stale AppDataPath registry value under the Epic Games launcher key is pointing to a directory that no longer exists. This survives uninstall-reinstall cycles because Epic’s installer rewrites the value only when it changes; if the value already exists with the wrong content, the installer leaves it alone. Windows reinstalls that ported the user profile, launcher upgrades that touched the registry partially, and migration tools that copied registry hives between machines are the typical sources.

Steps

1. Press the Windows key, type regedit, and press Enter. Accept the UAC prompt.
2. In the Registry Editor address bar, paste this path and press Enter: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Epic Games\EpicGamesLauncher.
3. In the right pane, locate the AppDataPath value. Read the data column; it should resolve to a valid directory like C:\ProgramData\Epic\EpicGamesLauncher\Data.
4. If the value is blank, points to a non-existent path, or references a previous Windows install, do not edit it manually. Close the Registry Editor.
5. Open Settings > Apps > Installed apps. Locate Epic Games Launcher in the list. Click the three-dot menu and choose Modify. When the installer dialog opens, choose Repair. The repair pass rewrites the registry values to match the current install. Microsoft documents the registry editor itself at learn.microsoft.com.
6. Reboot. Re-launch AlphaRes. Detection should now succeed.

A registry value should never be hand-edited unless there is a specific verified target value to write; the Repair option is safer because Epic’s own installer knows the correct value and applies it without mistakes.

Fix #6: Edit GameUserSettings.ini Manually

Symptom: none of the previous fixes restored detection, or the AlphaRes UI itself is unstable on the current machine. The goal is to lock the resolution without depending on AlphaRes detection working at all. The manual ini edit achieves the same end result, just without an UI in front of it.

Cause: AlphaRes is a convenience wrapper around four operations: read GameUserSettings.ini, change three lines, save, apply read-only. Each of those four operations can be done by hand in Notepad and File Explorer in under two minutes. When the wrapper itself fails for environmental reasons that none of the previous fixes resolve, the underlying file-edit approach still works because Fortnite reads the same file regardless of how the values got there.

Steps

1. Press the Windows key, type %LocalAppData%\FortniteGame\Saved\Config\WindowsClient, and press Enter. File Explorer opens the config folder.
2. Right-click GameUserSettings.ini. If Read-only is currently ticked under Properties, untick it and click Apply. Then open the file in Notepad.
3. Use Ctrl+F to find ResolutionSizeX. Edit the integer to the desired width (for example 1600 for 1600×1080 stretched). Find ResolutionSizeY and edit the integer to the desired height (1080). Find LastUserConfirmedResolutionSizeX and LastUserConfirmedResolutionSizeY and edit the same values to match. Find FullscreenMode and set the integer to 1 for Windowed Fullscreen or 2 for Windowed.
4. Save the file (Ctrl+S) and close Notepad.
5. Right-click GameUserSettings.ini in File Explorer. Choose Properties. Tick Read-only at the bottom of the General tab. Click Apply. Fortnite can no longer overwrite the file on the next patch.
6. Launch Fortnite and confirm the resolution applied. To revert later, untick Read-only and either edit the values back or let Fortnite rewrite the file at next launch.

The full comparison between using AlphaRes and editing the ini by hand sits in the AlphaRes vs manual GameUserSettings.ini edit guide; that article covers the trade-offs in depth, including why the AlphaRes UI is still preferred for most players despite the manual approach being functionally equivalent.