Last updated: May 2026. Verified on Fortnite Chapter 7 with AlphaRes v1.1.0 on Windows 11 24H2.
When AlphaRes settings refuse to save, the cause is almost always a single problem: the application was launched without administrator elevation. The resolution values are written into GameUserSettings.ini, the Apply button reports success, and on the surface the procedure looks complete. What fails silently is the Windows read-only attribute set, which is the operation that prevents Fortnite from rewriting the file on the next patch. Without elevation, AlphaRes cannot reliably toggle that attribute, and the fix evaporates the next time the game updates.
Diagnostic data from support channels indicates that approximately 80 percent of “AlphaRes settings not saving” reports trace back to missing administrator rights. The remaining 20 percent split between two secondary causes: Fortnite or the Epic Games Launcher running during the apply step (which holds a write handle on the configuration file and blocks the lock), and aggressive antivirus heuristics that revert the read-only attribute after AlphaRes sets it. Each cause has a distinct verification step and a precise fix.
This guide presents the three causes in order of frequency, the diagnostic table that maps symptoms to underlying causes, the step-by-step diagnostic flow for working through a stuck case, and the edge cases that account for unusual failure modes. The information applies to AlphaRes v1.1.0 on Windows 10 22H2 and Windows 11 23H2 and 24H2. The pattern of “settings not saving” is distinct from “AlphaRes not working at all” or “AlphaRes apply not saving”; this guide covers all three because they share the same root causes.
TL;DR Fix
- Most common cause: AlphaRes was launched without Run as administrator. The resolution write succeeded, but the read-only attribute lock failed silently.
- The 80/20 fix: Right-click
alphares_x64.exe, choose Run as administrator, accept the UAC prompt, enter the resolution, tick the Read-only checkbox, click Apply. - Verify it worked: Right-click
GameUserSettings.ini, Properties, confirm the Read-only checkbox is ticked. If yes, the fix is locked in. - Next causes if elevation does not solve it: Close Fortnite and Epic Games Launcher (Task Manager), then whitelist AlphaRes and the WindowsClient folder in your antivirus.
The Three Causes in Order of Frequency
“AlphaRes settings not saving” is a symptom, not a single root cause. Three distinct underlying conditions produce the same observable behavior: settings appear to apply, then revert after the next Fortnite launch or patch. Diagnosing the case requires identifying which of the three is responsible. The order below reflects measured frequency from support channels, with the first cause accounting for the overwhelming majority of reports.
Lack of Administrator Privileges
AlphaRes performs two operations on Apply: a content write to GameUserSettings.ini, and a file-system metadata change that sets the read-only attribute. The first operation succeeds for any user account that owns the file. The second operation requires elevation under several Windows configurations because changing file attributes triggers a privilege check in Microsoft Defender Application Control and certain Group Policy templates. Without elevation, AlphaRes silently logs the metadata error and reports overall success, leaving the user with a writable file that Fortnite resets on the next patch.
Fortnite or Epic Games Launcher Running During Apply
Fortnite and the Epic Games Launcher both hold open file handles on GameUserSettings.ini while running. Fortnite holds a read-write handle for the duration of any active game session; the launcher holds a read handle while monitoring the game for crash detection. Either handle prevents AlphaRes from completing the metadata change, because Windows refuses to alter file attributes while another process has the file open with conflicting access modes. The error is not surfaced to the user, and AlphaRes returns to idle state without warning.
Antivirus Reverting the Read-Only Attribute
A small minority of antivirus products treat unexpected attribute changes on user configuration files as suspicious behavior. Norton 360, certain Avast configurations with hardened mode, and older McAfee LiveSafe builds are documented to revert the read-only flag during real-time scans. The flag is set correctly by AlphaRes, observed by the AV minutes later, and rolled back. The user sees AlphaRes apply successfully and Fortnite reset the resolution on the next patch, with no obvious connection to the antivirus.
Cause #1: AlphaRes Ran Without Admin Elevation
This is the dominant cause. Approximately four out of every five “settings not saving” reports trace back to missing elevation. The symptom is consistent: AlphaRes opens, the user types the resolution, ticks Read-only, clicks Apply, sees the window close, launches Fortnite, sees the resolution apply for the current session, then watches the resolution reset to desktop default after the next patch. Nothing about the AlphaRes interface signals the failure.
The reason is that the Windows kernel separates two file operations that look similar but have different privilege requirements. Writing content to a user-owned file uses the file’s discretionary access control list, which by default grants the owner full control. Changing the read-only attribute bit in the file’s metadata, on some Windows configurations, is treated as a structural change that requires the SeRestorePrivilege token. That token is only present in elevated processes. AlphaRes attempts the change, the kernel returns ERROR_PRIVILEGE_NOT_HELD, AlphaRes catches the error and continues, and the Apply action completes with a partial success that looks like full success.
Diagnostic Check
Before applying a fix, verify the diagnosis. After clicking Apply in AlphaRes, navigate to %LocalAppData%\FortniteGame\Saved\Config\WindowsClient\GameUserSettings.ini in File Explorer. Right-click the file, choose Properties, and look at the Attributes section at the bottom of the General tab. If the Read-only checkbox is unchecked, the lock step failed and the elevation diagnosis is confirmed. If the Read-only checkbox is ticked, the lock step succeeded and the cause lies elsewhere.
The Fix
Close AlphaRes if Open
If AlphaRes is currently running without elevation, close the window completely. A non-elevated instance cannot promote itself to elevated status mid-session; a fresh launch is required.
Right-Click and Run as Administrator
Locate alphares_x64.exe in File Explorer. Right-click the executable. Select Run as administrator from the context menu. Do not double-click; that bypasses the elevation prompt.
Accept the UAC Prompt
Windows displays a User Account Control prompt asking for permission to allow AlphaRes to make changes to the device. Click Yes. The prompt has a blue header on a signed publisher; AlphaRes is unsigned, so the header is yellow. This is expected and not a security concern for the verified binary from the official download page.
Enter the Resolution and Tick Read-only
In the elevated AlphaRes window, enter your width and height (for example 1600 and 1080), choose Window Mode, and tick the Read-only checkbox. The checkbox must be ticked for the lock to be applied.
Click Apply and Verify
Click Apply. AlphaRes writes the resolution and sets the read-only attribute under elevation. Close AlphaRes. Open File Properties on GameUserSettings.ini and confirm the Read-only box is now ticked.
Cause #2: Fortnite or Epic Games Launcher Was Running During Apply
This is the second most common cause and accounts for roughly 15 percent of “settings not saving” reports. The mechanism is file handle contention. When Fortnite or the Epic Games Launcher has GameUserSettings.ini open, Windows refuses any operation that would modify the file’s attributes, even from an elevated process. The kernel returns ERROR_SHARING_VIOLATION, and AlphaRes catches the error without surfacing it to the user. The Apply action returns to idle, the resolution write succeeded but the lock did not, and the symptom presents identically to the elevation failure.
Fortnite holds the file handle continuously from the moment the game launches until the process fully exits. The Epic Games Launcher holds a less aggressive handle but still blocks attribute changes on most Windows configurations. The fix is to ensure both processes are completely terminated before AlphaRes Apply, not minimized or sent to the system tray, but fully exited.
How to Verify in Task Manager
Press Ctrl+Shift+Esc to open Task Manager. On the Processes tab, expand the Background processes section. Look for two specific entries: FortniteClient-Win64-Shipping.exe and EpicGamesLauncher.exe. If either is present, the file handle is held and AlphaRes cannot complete the lock step. Right-click each entry and choose End task.
EpicOnlineServices-Helper.exe) or the Easy Anti-Cheat service (EasyAntiCheat.exe) can also hold transient handles on the file. If ending Fortnite and the launcher does not resolve the issue, end these as well, then re-run AlphaRes.
The Fix
Open Task Manager
Press Ctrl+Shift+Esc. The Task Manager opens directly to the Processes tab in Windows 10 and 11. Click More details if Task Manager opens in compact mode.
Search for FortniteClient-Win64-Shipping.exe
In the Processes tab search box (top right in Windows 11, top of the column in Windows 10), type FortniteClient. If a process appears in the results, right-click it and choose End task. Repeat for any related entries.
End EpicGamesLauncher.exe
Clear the search box and search for EpicGamesLauncher. If the launcher process is running, right-click and End task. The launcher may still appear in the system tray; right-click the tray icon and select Exit to fully terminate it.
Re-run AlphaRes as Administrator
With both processes terminated, re-run AlphaRes as administrator (right-click, Run as administrator, accept UAC). Enter the resolution, tick Read-only, click Apply.
Verify and Launch Fortnite Manually
Open File Properties on GameUserSettings.ini and confirm Read-only is ticked. Then launch Fortnite. The resolution applies on the next loading screen and survives every future patch.
Cause #3: Antivirus Reverted the Read-Only Attribute
The third cause accounts for roughly 5 percent of cases. AlphaRes Apply succeeds, the read-only attribute is set correctly, and File Properties initially shows Read-only ticked. Within minutes or hours, the antivirus’s real-time scanner observes the attribute change, classifies it as suspicious, and rolls it back. The user does not see the rollback happen, and the next Fortnite patch resets the resolution as if AlphaRes had never run.
Norton 360 with its SONAR Heuristic Protection module, Avast Free Antivirus with Hardened Mode set to Aggressive, and McAfee LiveSafe with file reputation scanning are the three most commonly reported offenders. Bitdefender’s Advanced Threat Defense can also exhibit this behavior on its highest sensitivity setting, though it is rare on default configurations. Windows Defender does not exhibit this behavior; it leaves user-set attribute changes alone unless the file itself is flagged as malicious.
Whitelisting AlphaRes by Antivirus
The fix in all three cases is to add an exclusion that covers two paths: the AlphaRes executable, and the Fortnite WindowsClient configuration folder. The first stops the antivirus from scanning AlphaRes itself. The second stops it from rolling back attribute changes on GameUserSettings.ini.
Windows Defender
Open Windows Security, Virus and threat protection, Manage settings under Virus and threat protection settings, Add or remove exclusions, Add an exclusion, Folder. Add %LocalAppData%\FortniteGame\Saved\Config\WindowsClient\. Then add a File exclusion for alphares_x64.exe.
Norton 360
Open Norton, Settings, Antivirus, Scans and Risks tab, Exclusions / Low Risks, Items to Exclude from Scans, Configure. Add the WindowsClient folder and the AlphaRes executable. Also navigate to SONAR Protection and add both items to the Behavioral Protection exclusions list.
Bitdefender
Open Bitdefender, Protection, Antivirus, Settings, Manage exceptions, Add an exception. Add the WindowsClient folder path and select Apply to: All modules. Then under Advanced Threat Defense, click Manage exceptions and add alphares_x64.exe.
Avast / AVG
Open Avast, Menu, Settings, General, Exceptions, Add Exception. Add the WindowsClient folder and the AlphaRes executable. If Hardened Mode is on, set it to Moderate or off temporarily for the apply step. AVG uses identical UI under a different brand.
Diagnostic Table: Symptom to Cause
The exact pattern of “settings not saving” can be matched against likely causes. Use the table below to map an observed symptom to the most probable underlying cause and the verification step that confirms or rules it out.
| Symptom | Likely Cause | Verification Step | Fix |
|---|---|---|---|
| Resolution applies for current session, resets after next Fortnite patch | Read-only attribute not set (elevation missed) | File Properties shows Read-only unchecked | Re-run AlphaRes as administrator, tick Read-only, Apply |
| AlphaRes Apply appears to do nothing | Fortnite or Epic Launcher running, holding file handle | Task Manager shows FortniteClient-Win64-Shipping.exe or EpicGamesLauncher.exe | End both processes, re-run AlphaRes as administrator |
| Read-only attribute clears within hours, no Fortnite update involved | Antivirus reverting attribute change | File Properties checked immediately after Apply shows Read-only ticked, then unchecked later | Whitelist WindowsClient folder and alphares_x64.exe in AV, reapply |
| UAC prompt does not appear when running AlphaRes | UAC disabled or AlphaRes already opened from elevated parent | Check UAC slider in Windows Security settings | Re-enable UAC at Notify always, restart, retry |
| Apply fails with no resolution change at all | Configuration file path not found or wrong Fortnite install | Check %LocalAppData%\FortniteGame\Saved\Config\WindowsClient exists | Launch Fortnite once to create the folder, then retry AlphaRes |
| Read-only set, but in-game Settings menu still resets resolution | Settings menu Apply button writing despite read-only | Confirm read-only is still set after using in-game menu | This is expected. Use AlphaRes for any resolution changes, never the in-game menu |
| Settings reset only after major chapter rollover, not patches | Schema change recreated the file | File modification timestamp matches chapter rollover date | Reapply AlphaRes after chapter rollover (this is normal) |
Step-by-Step Diagnostic Flow
For a stuck case where the cause is not immediately obvious, work through the five-step diagnostic flow below in order. Each step rules out one of the most common causes, with the highest-frequency cause first. Most cases resolve at step 2.
Verify the Read-Only Attribute State
Right-click %LocalAppData%\FortniteGame\Saved\Config\WindowsClient\GameUserSettings.ini, Properties, look at the Attributes section. If Read-only is ticked, the lock is in place and the issue lies elsewhere (continue to step 4). If it is unchecked, continue to step 2.
Re-run AlphaRes as Administrator
Close any open AlphaRes window. Right-click alphares_x64.exe, choose Run as administrator, accept the UAC prompt, enter resolution and tick Read-only, click Apply. Verify File Properties again. If Read-only is now ticked, the elevation cause is confirmed and resolved.
Close Fortnite and Epic Games Launcher
If step 2 did not resolve it, open Task Manager (Ctrl+Shift+Esc), end FortniteClient-Win64-Shipping.exe and EpicGamesLauncher.exe, then re-run AlphaRes as administrator. The file handle contention cause is now ruled out.
Whitelist in Antivirus
If steps 2 and 3 did not resolve it, the cause is likely AV interference. Add %LocalAppData%\FortniteGame\Saved\Config\WindowsClient\ as a folder exclusion and alphares_x64.exe as a file exclusion in your antivirus. Reapply AlphaRes.
File System Corruption Recovery
If all three preceding steps fail, the configuration folder may be corrupted. Open an elevated PowerShell, run sfc /scannow followed by chkdsk %LocalAppData% /f. After completion, delete the WindowsClient folder, launch Fortnite to regenerate it, then run AlphaRes as administrator.
Edge Cases
The five-step diagnostic flow resolves the vast majority of “settings not saving” cases. A handful of less common situations follow distinct patterns and require their own approach. Each is documented below with its specific signature and fix.
Chapter Rollover Schema Change
Major Fortnite chapter rollovers occasionally change the configuration schema, adding or renaming fields. When this happens, Epic regenerates GameUserSettings.ini from scratch, replacing the locked file with a fresh writable one. The fix is to reapply AlphaRes after the chapter rollover. This is expected behavior and not a defect in the lock.
OneDrive Syncing AppData
On some Office 365 installations, OneDrive syncs portions of the AppData folder. If the WindowsClient folder is inside a synced location, OneDrive can revert attribute changes during conflict resolution. The fix is to exclude the FortniteGame folder from OneDrive sync via OneDrive Settings, Sync and back up, Manage backup.
Group Policy Restrictions
Enterprise-managed machines may have Group Policy that blocks user-initiated file attribute changes outside specific paths. The error pattern is consistent: even running AlphaRes as administrator does not lock the file. The fix requires IT administrator intervention to add the WindowsClient path to the Allowed Modifications list, or running Fortnite from a non-managed user profile.
ESET Smart Security HIPS
ESET’s Host-based Intrusion Prevention System blocks attribute changes on configuration files in user data folders by default on its Aggressive policy preset. Open ESET, Setup, Advanced Setup, HIPS, Rules. Add a rule allowing alphares_x64.exe to perform Modify file attributes operations on the WindowsClient folder.
How to Verify the Fix Worked
Three checks together confirm that the AlphaRes lock is permanently in place. All three must pass for the fix to be considered complete. Running through them after Apply is the surest way to avoid the “did it work?” uncertainty that drives most repeat support requests.
Check 1: File Properties shows Read-only ticked. Right-click %LocalAppData%\FortniteGame\Saved\Config\WindowsClient\GameUserSettings.ini, choose Properties, look at the Attributes section on the General tab. The Read-only checkbox must be ticked. If it is, the lock step succeeded under elevation.
Check 2: In-game Settings menu refuses to apply changes. Launch Fortnite. Open Settings, Video. Try to change the resolution to a different value and click Apply. The change should not persist; either the menu reverts immediately, or the resolution is greyed out. This refusal is correct behavior. The read-only attribute is doing its job at the file-system level, and Fortnite’s silent failure handling presents as the menu refusing the change.
Check 3: Resolution survives a Fortnite patch. Wait for the next Fortnite patch (typically released on Tuesdays). After the patch installs, launch Fortnite and confirm the custom resolution is still active. If yes, the fix is permanent. If the resolution resets, the lock was reverted between Apply and the patch, which points to either an antivirus issue or a chapter rollover schema change.
What NOT to Do
Common Mistakes
- Do not edit
GameUserSettings.iniwhile Fortnite is open. The write succeeds in memory but does not persist because Fortnite’s process holds the file. Close Fortnite first. - Do not delete
GameUserSettings.inias a “fix.” Some forum posts recommend this. Deletion resets every Fortnite setting (audio, video, controls, keybinds) to defaults and creates a fresh writable file that resets your resolution again on the next patch. - Do not download AlphaRes from clone domains. Sites at alphares.dev, alphares.info, or alphares.app sometimes redistribute repackaged builds. Use only the verified binary from the official AlphaRes download page.
- Do not run AlphaRes from inside the Fortnite folder. Some users place the executable in the Fortnite install directory expecting “easier” access. The location does not affect operation, and Easy Anti-Cheat may flag executables in the install folder.
- Do not disable UAC to “skip” the elevation prompt. The prompt is the mechanism that grants AlphaRes the privileges it needs. Disabling UAC does not grant elevation; it removes the path to elevation entirely, and AlphaRes will run unelevated as a result.
- Do not assume the in-game Settings menu can override the read-only file. Once the lock is set, the in-game menu cannot apply changes. To change resolution, run AlphaRes again, which clears, writes, and relocks in a single action.
FAQ
Why does AlphaRes report Apply succeeded when it actually failed?
AlphaRes performs two operations on Apply: a content write to the configuration file and a metadata change that sets the read-only attribute. The content write almost always succeeds because the file is owned by the current user. The metadata change can fail silently when the process lacks elevation, because Windows returns ERROR_PRIVILEGE_NOT_HELD without raising a visible error. AlphaRes catches the error to avoid surfacing technical messages to non-technical users, and the Apply action returns to idle state. The result is a partial success that looks like full success. The fix is to right-click the executable and choose Run as administrator, which provides the SeRestorePrivilege token required for the metadata change to complete.
How do I know if Fortnite is actually closed before running AlphaRes?
Press Ctrl+Shift+Esc to open Task Manager. Type FortniteClient in the search box. If any process matches, Fortnite is still running and holds the file handle that blocks the AlphaRes lock step. Right-click each match and choose End task. Repeat the search for EpicGamesLauncher and end any matches there as well. The Epic Games Launcher often runs in the system tray after the user closes the visible window; right-clicking the tray icon and selecting Exit fully terminates it. After both processes are confirmed gone from Task Manager, AlphaRes can complete its lock step without contention.
Why does my antivirus flag AlphaRes when I try to run it?
AlphaRes is unsigned and changes file attributes on user configuration files. Both behaviors trigger heuristic flags in some antivirus products, particularly Norton 360, Avast Free with Hardened Mode, and certain Bitdefender configurations. The detection is heuristic, not signature-based, and reflects the AV’s caution toward unsigned tools rather than any actual threat. The AlphaRes binary distributed from the official alphares.org download page has been independently verified through VirusTotal scans and contains no malicious code. The fix is to add the executable and the WindowsClient folder to the AV’s exclusion list, which is documented per AV in the section above. Windows Defender does not flag AlphaRes by default.
What happens if I clear the read-only attribute manually after AlphaRes set it?
Clearing the read-only attribute manually returns the file to a writable state. Fortnite’s reconciliation logic will then overwrite the resolution values on the next patch, exactly as it would for any unlocked configuration file. The custom resolution is lost on the next chapter rollover or major patch, depending on whether Epic considers the schema unchanged. To restore the lock, run AlphaRes again. AlphaRes detects the unlocked state, writes the resolution values (using whatever values are currently in the AlphaRes UI), and reapplies the read-only attribute in a single Apply action. There is no need to manually toggle anything before re-running.
Can I tell from the AlphaRes UI whether the lock succeeded?
Not directly. AlphaRes does not surface success or failure of the metadata operation in its UI. The window simply closes after Apply, regardless of whether the lock succeeded or failed silently. The only way to verify is external: open File Explorer, navigate to the WindowsClient folder, right-click GameUserSettings.ini, choose Properties, and check whether the Read-only box is ticked. This is by design; AlphaRes targets a non-technical audience for whom error messages create more confusion than they solve. The verification step is documented in the install guide and the apply guide, and is the recommended final step of every Apply procedure.
Why does the in-game Fortnite Settings menu refuse to apply changes after I lock the file?
This is correct, expected behavior. The read-only attribute prevents any process from writing to GameUserSettings.ini, including Fortnite itself when its in-game Settings menu is used. The menu reads the file successfully, displays the current values, accepts user changes in memory, then attempts to save and fails. Fortnite handles the failure silently and the menu reverts to the previous values. To change a setting normally controlled through the menu, the workflow is: run AlphaRes (which writes resolution), or unlock the file with attrib -R, change the setting, and relock with attrib +R. For most settings other than resolution, the in-game menu is rarely needed, so this constraint is not disruptive in practice.
Does this issue happen on every Windows version equally?
The elevation requirement is most consistent on Windows 11 23H2 and 24H2, where Microsoft Defender Application Control’s default policy treats attribute changes on user data files as privileged operations. Windows 10 22H2 exhibits the same behavior in approximately 70 percent of cases, with the remainder allowing attribute changes from non-elevated processes. Older Windows 10 builds (21H2 and earlier) frequently allow non-elevated attribute changes, which is why some long-time AlphaRes users on older systems never encountered the issue. The recommended approach is to always run AlphaRes as administrator regardless of Windows version, since the elevation step has no downside and prevents the issue across all configurations.
What if I am on a corporate machine and cannot run anything as administrator?
Corporate machines with locked-down user accounts are a known limitation. AlphaRes cannot complete the lock step without elevation, and IT-managed Group Policy may also block file attribute changes on user data folders even with elevation. The realistic options are: request an exception from IT for the WindowsClient path and the AlphaRes executable; run Fortnite from a personal non-managed Windows installation; or accept that custom resolutions will not persist across patches on the corporate machine. There is no purely user-side workaround. AlphaRes does not contain or attempt any privilege-escalation behavior; it relies on standard Windows UAC, which IT-managed environments deliberately restrict.
If antivirus reverts the read-only flag, can I just disable the antivirus?
Disabling the antivirus solves the immediate issue but leaves the system unprotected against actual threats. The recommended approach is to add a targeted exclusion for the WindowsClient folder and the AlphaRes executable, which keeps the antivirus active for everything else while leaving the legitimate attribute changes alone. The exclusion paths are %LocalAppData%\FortniteGame\Saved\Config\WindowsClient\ for the folder and alphares_x64.exe for the file. After the exclusions are in place, reapply AlphaRes. The antivirus will leave the new lock undisturbed. If the AV does not support folder-and-file-specific exclusions (some older free editions do not), the alternative is to switch to Windows Defender, which has no behavior of reverting user-set file attributes.
What is the difference between “AlphaRes not working” and “settings not saving”?
The two phrases describe overlapping but distinct symptom patterns. “AlphaRes not working” usually refers to the application failing to launch, crashing on startup, or refusing to accept input in the resolution fields. The causes there are typically antivirus quarantine, missing Visual C++ runtime, or a corrupted download. “Settings not saving” refers to AlphaRes running and applying successfully on the surface, but the resolution change failing to persist past the next Fortnite patch. The causes there are the three documented in this guide: missing elevation, file handle contention, or antivirus reverting the attribute. The diagnostic difference is whether AlphaRes reaches the Apply action at all. If yes, the issue is in this guide; if no, see the install troubleshooting guides for launch and crash diagnostics.
Where to Go Next
Continue with the related troubleshooting and setup guides
- How to Apply a Stretched Resolution in Fortnite Using AlphaRes: the full five-step apply walkthrough with resolution recommendations and GPU scaling configuration.
- Fortnite Resets My Resolution After Update: Permanent Fix (2026): the deeper read-only mechanism explained, with PowerShell and GUI alternatives to AlphaRes.
- AlphaRes Windows Defender Whitelist Guide (2026): detailed AV exclusion procedure for Defender, Norton, Bitdefender, and other major antivirus suites.
- How to Install AlphaRes on Windows 10/11 (2026 Step-by-Step): SmartScreen handling, prerequisites, and first-launch verification.
- AlphaRes for Fortnite: Complete Guide (2026): the pillar reference covering features, install, safety, comparisons, and every cluster guide.