No. AlphaRes ships exclusively as a single 533 KB executable named AlphaRes.exe. There is no setup wizard, no MSI installer, no Windows Installer entry, and no add/remove programs registration. The utility is fully portable. Placing the executable in any folder on disk is sufficient. Removal is equally simple: deleting the .exe removes the program entirely. The single-file design has practical benefits for competitive players who move between machines (LAN events, friend’s PCs, training rigs), since the utility can be carried on a USB drive and run from there without installation. The only state AlphaRes ever touches outside its own folder is Fortnite’s GameUserSettings.ini, and that change is reversible by deleting that file and relaunching Fortnite.

Windows Defender SmartScreen flags any executable that lacks an Authenticode digital signature from a trusted certificate authority. Code-signing certificates from vendors such as DigiCert or Sectigo cost between 250 and 600 USD per year, which is impractical for a free utility. The same warning appears for thousands of legitimate open-source tools including 7-Zip predecessors, OBS earlier builds, and the majority of community-built game utilities. The warning is a procedural notification about signing status, not a malware verdict. SmartScreen has separate machinery for true threat detection that triggers a different, more severe red banner. The blue “More info, Run anyway” prompt indicates only that Microsoft does not have a signature on file from a paying publisher.

The download and placement steps require no special permissions, but the Apply step does. AlphaRes needs to clear the read-only attribute on GameUserSettings.ini before writing new values, then optionally re-apply that attribute. Standard user accounts can usually modify files inside their own %LocalAppData% tree, but cleared-then-restored read-only flags require slightly elevated permissions on some Windows configurations, particularly those locked down by Group Policy. The safest approach is to right-click the executable and choose Run as administrator. On home PCs this triggers a single UAC prompt and resolves all permission issues. On managed corporate machines, contact the local IT administrator if Run as administrator is unavailable.

Any folder writable by the current user works, but stable long-term locations are preferable. Recommended folders include C:\Tools\AlphaRes\, %UserProfile%\Documents\AlphaRes\, or a dedicated folder on a secondary drive such as D:\GameUtilities\AlphaRes\. Avoid the Downloads folder, where Windows Storage Sense may delete files older than 30 or 60 days. Avoid Program Files, since AlphaRes does not need elevation to be located there and storing it there complicates updates. Avoid OneDrive-synced folders, where file locks during sync can interfere with the Apply operation. A folder under the user profile is the cleanest choice, since it follows the user across Windows reinstalls of the same account.

No. AlphaRes is a one-shot configuration writer, not a resident service or background helper. Once Apply has succeeded with the read-only checkbox enabled, the configuration persists indefinitely. Fortnite reads the file on each launch, sees the locked values, and obeys them. AlphaRes can be closed immediately after Apply and does not need to re-run unless the desired resolution, FPS, or window mode changes. For players who frequently switch between (for example) 1440 by 1080 in ranked and 1920 by 1080 in casual playlists, AlphaRes can be reopened to swap values in roughly 10 seconds. The utility holds no state of its own between runs.

Uninstallation is a single delete operation: remove AlphaRes.exe from its folder. There are no registry keys, no scheduled tasks, no services, no Start menu shortcuts (unless manually created), and no Programs and Features entry to clean up. To also revert Fortnite to default behavior, navigate to %LocalAppData%\FortniteGame\Saved\Config\WindowsClient\, right-click GameUserSettings.ini, choose Properties, and uncheck the read-only attribute. Optionally delete the file entirely; Fortnite will regenerate it with default values on next launch. This two-step revert (delete .exe, clear read-only) returns the system to the exact pre-install state with zero residue.

Yes, with the read-only checkbox enabled. Fortnite patches update the game executable and content packages but do not delete or rewrite GameUserSettings.ini. Even when a patch attempts to overwrite the file (rare, typically only on major engine version changes), the read-only attribute set by AlphaRes blocks the write and the existing values remain intact. After major version transitions, it is good practice to launch Fortnite once and confirm the resolution dropdown still shows the expected values. If a patch ever does succeed in resetting the configuration (extremely rare), simply re-run AlphaRes and click Apply to restore the desired settings in approximately five seconds.

No. AlphaRes operates exclusively while Fortnite is closed, modifies a configuration file Epic provides for user settings, and never injects code, hooks DLLs, reads game memory, or interacts with the Fortnite process in any way. Easy Anti-Cheat scans for runtime tampering with the game executable and protected memory regions; a static text file edit performed by an unrelated process at a different time is outside its detection scope. Editing GameUserSettings.ini by hand in Notepad is functionally identical to what AlphaRes does and is something Epic implicitly permits by shipping the file in plaintext. Years of community usage and dedicated safety analyses have produced zero substantiated reports of an EAC ban tied to AlphaRes.

Yes. Fortnite stores its GameUserSettings.ini per Windows user inside %LocalAppData%, which expands differently for each account. Two siblings sharing one PC can run AlphaRes independently from their own user sessions and configure entirely different resolutions, FPS caps, and window modes without conflict. The AlphaRes executable itself can be stored in a shared folder (such as C:\Tools\) or duplicated into each user’s profile. Both approaches work because AlphaRes always resolves %LocalAppData% at runtime to the currently logged-in user. Each account must independently launch Fortnite once to generate its own configuration file and must run AlphaRes elevated under its own user session.

Three causes account for nearly all such cases. First, Fortnite or the Epic Games Launcher was running during Apply, holding a write lock that caused the operation to fail silently; close both, including the launcher tray icon, and re-apply. Second, AlphaRes was launched without administrator rights, so the read-only attribute could not be cleared; right-click and choose Run as administrator. Third, an old GameUserSettings.ini.backup file may exist next to the configuration file and Fortnite restored from it; delete the backup. If all three checks pass and the issue persists, delete GameUserSettings.ini entirely, launch Fortnite once to regenerate it with defaults, then run AlphaRes elevated.