Last updated: May 2026. Verified on Fortnite Chapter 7 with AlphaRes v1.1.0 on Windows 11 24H2.
Locking Fortnite’s resolution against Epic’s update process requires only one operation: setting the Windows read-only file attribute on GameUserSettings.ini. The lock is enforced at the operating-system layer, which means Fortnite’s reconciliation routine can attempt to overwrite the file all it wants, the kernel returns access-denied, and the player’s chosen resolution survives intact. The lock is durable across game patches, chapter rollovers, engine version bumps, and even Windows feature updates. Once applied correctly, no further intervention is required.
The mechanism that protects a custom Fortnite resolution from being overwritten on patches is not a Fortnite setting, a registry tweak, or an anti-cheat workaround. It is a standard NTFS attribute that has existed in Windows since NT 3.1, repurposed to defend a single configuration file from a single misbehaving update routine. AlphaRes, PowerShell’s attrib command, and File Explorer’s Properties dialog all expose the same underlying attribute. The choice between them is a matter of convenience, not capability.
This guide explains why the lock works, walks through three procedures to apply it (AlphaRes for most users, PowerShell for power users, GUI for visual learners), shows three independent verification checks that confirm the lock is in effect, lists the three failure scenarios where the lock can break, and answers the ten most common questions players ask about read-only resolution locking. The methods are independent: applying any one of them produces the same end state.
TL;DR
- The lock: Windows read-only attribute on
%LocalAppData%\FortniteGame\Saved\Config\WindowsClient\GameUserSettings.ini. - Fastest method: Run AlphaRes v1.1.0 as administrator, type width and height, tick the Read-only checkbox, click Apply. Total time under one minute.
- Verification: Three independent checks (Properties dialog, PowerShell
IsReadOnly, post-patch behaviour). All three must agree before the lock is considered durable. - Most common failure: Running AlphaRes without administrator elevation. The resolution is written, the read-only flag is silently skipped, Fortnite resets the file on the next patch.
Why Fortnite Resets Resolution
Fortnite ships with a configuration reconciliation routine that runs during every patch installation and during certain version-stamped launch sequences. The routine reads GameUserSettings.ini, validates each entry against Epic’s recognized schema, and overwrites any value that does not match a recognized preset. Resolution values are at the top of the validation list. A custom ResolutionSizeX=1600 paired with ResolutionSizeY=1080 does not match any of the presets Epic ships with the game, so reconciliation rewrites both lines to the system desktop default, typically 1920x1080. The same logic targets LastUserConfirmedResolutionSizeX and LastUserConfirmedResolutionSizeY.
This behaviour is intentional. The reconciliation routine is designed to recover Fortnite from broken configurations after schema changes, monitor disconnections, driver migrations, or corrupt-file scenarios. It is also why Fortnite refuses to launch at 0x0 when a player ran the game on an older monitor and unplugged it before the next session. The unintended side effect is that legitimate competitive setups with stretched, downscaled, or otherwise non-preset resolutions are also rewritten on every patch.
The reconciliation runs most aggressively during patch installation, which is why the symptom presents as “resolution resets after every update.” It also runs during chapter rollovers (when the schema gains new fields), after engine version bumps, and occasionally after a clean Fortnite reinstall. Between routine play sessions on the same patch, the file is left alone. The lock described in this guide does not disable the reconciliation routine. It blocks the routine’s write attempt at the file-system layer, which is sufficient to preserve the player’s resolution without modifying Fortnite at all.
The Read-Only Attribute Mechanism
Windows NTFS supports a read-only attribute that prevents any process from writing to a file, regardless of the process’s user privileges. The attribute is stored in the file system’s metadata, not in the file contents. When a process attempts to open a read-only file for write access, the kernel returns ERROR_ACCESS_DENIED (error code 5) before the process’s write buffer ever reaches the disk. Fortnite’s reconciliation routine handles the error silently, the file remains unchanged, and the player’s chosen resolution survives the patch.
The attribute is enforced by the operating system at a level below the application layer. This is what makes the lock durable: Fortnite cannot bypass it without explicitly clearing the attribute first, and Fortnite’s reconciliation logic does not include a clear-attribute step. The routine is designed for the common case where a configuration file is fully writable; it does not anticipate the file being deliberately locked. The read-only attribute exploits this gap without modifying the game.
What AlphaRes does at the file level is the same operation that PowerShell attrib +R performs, and the same operation that ticking the Read-only checkbox in File Explorer Properties performs. All three paths set a single flag in the file’s NTFS metadata. The differences are in convenience and atomicity: AlphaRes writes the resolution values and sets the attribute in one Apply action, eliminating the most common error (forgetting to set the attribute after a manual edit). PowerShell and the GUI require the user to perform two distinct steps and risk interleaving them incorrectly.
The attribute survives normal file operations: copying (the new copy inherits read-only), moving within the same volume, antivirus scans that do not modify the file, and Windows feature updates. It does not survive a deliberate file deletion, a Fortnite reinstall that removes the entire WindowsClient folder, an explicit attrib -R command, or third-party optimizer tools that “clean” file attributes as part of a system tune-up. The recovery procedure for each of those scenarios is documented later in this guide.
Method 1: AlphaRes (Recommended)
AlphaRes v1.1.0 is the canonical tool for applying and locking a custom Fortnite resolution. It writes the resolution values to GameUserSettings.ini and sets the read-only attribute in a single Apply action. This method is the recommended path for almost every player because it removes the two most common error vectors: editing the file with a syntax mistake that prevents Fortnite from parsing it, and forgetting to set the read-only attribute after a successful manual edit.
Download and Place AlphaRes
Get the verified binary from the official AlphaRes download page. The file is 533 KB, x64 only, and ships unsigned (SmartScreen will warn on first run, which is expected). Place alphares_x64.exe in a stable location like C:\Tools\AlphaRes\ or your Desktop. Avoid clones at alphares.dev or alphares.info; they sometimes serve repackaged builds.
Run as Administrator
Right-click alphares_x64.exe and select Run as administrator. Elevation is non-optional. Without it, AlphaRes can write the resolution to the configuration file but the read-only attribute set fails silently because the attribute change is treated as a privileged operation under several Windows configurations. The Apply action will appear to succeed, and the resolution will reset on the next Fortnite patch.
Enter Width and Height
Type the desired resolution width into the Width field and the height into the Height field. Common picks for Fortnite competitive play: 1600x1080 (balanced stretch), 1440x1080 (maximum stretch), 1720x1080 (mild stretch). For non-stretched custom resolutions like 1024x768 retro setups or 2560x1080 ultrawide, the same procedure applies. AlphaRes does not validate that the resolution is supported by your monitor; that responsibility is yours.
Tick the Read-only Checkbox
This is the step that most users miss. The Read-only checkbox controls whether AlphaRes sets the Windows read-only attribute on GameUserSettings.ini after writing the resolution values. With the checkbox unchecked, AlphaRes writes the resolution but leaves the file fully writable, and Fortnite’s reconciliation logic rewrites the values on the next patch. Tick the checkbox before clicking Apply. It remains ticked between AlphaRes sessions but verifying it is good hygiene.
Click Apply
AlphaRes writes the resolution values to all four resolution keys (ResolutionSizeX, ResolutionSizeY, LastUserConfirmedResolutionSizeX, LastUserConfirmedResolutionSizeY), writes the FPS and window mode if specified, sets the read-only attribute, and closes the file handle. There is no confirmation dialog; the action is fire-and-forget. Close AlphaRes and launch Fortnite. The resolution applies on the next loading screen and persists across every future patch until the read-only attribute is manually cleared.
Method 2: PowerShell
Power users and players on locked-down corporate workstations can apply the same lock entirely from PowerShell. The procedure has three steps: edit the configuration file in Notepad to set the resolution values, save and close the file, then run a single attrib command from an elevated PowerShell window to set the read-only attribute. The end state is identical to Method 1, except that the resolution write is manual rather than automated and is therefore more error-prone.
Open the Configuration File
Press Win+R, paste %LocalAppData%\FortniteGame\Saved\Config\WindowsClient\GameUserSettings.ini, and press Enter. The file opens in Notepad. If Windows reports the file does not exist, launch Fortnite once and let it sit on the lobby for ten seconds, then close it. Fortnite creates the file on first launch with default values; the file must exist before AlphaRes or any manual procedure can edit it.
Edit the Resolution Lines
Use Notepad’s Find feature (Ctrl+F) to locate ResolutionSizeX. Set it to your custom width, for example ResolutionSizeX=1600. Find ResolutionSizeY and set it to the height, for example ResolutionSizeY=1080. Repeat for LastUserConfirmedResolutionSizeX and LastUserConfirmedResolutionSizeY if they appear in the file. Do not modify any other lines unless you understand the schema. Save the file with Ctrl+S and close Notepad.
Apply the Read-Only Lock
Open PowerShell as administrator (right-click Start, then Windows Terminal (Admin) on Windows 11 or PowerShell (Admin) on Windows 10). Run the following command, which sets the read-only attribute on the configuration file. Verify with the second command, which returns True when the attribute is set correctly.
attrib +R "$env:LocalAppData\FortniteGame\Saved\Config\WindowsClient\GameUserSettings.ini" (Get-Item "$env:LocalAppData\FortniteGame\Saved\Config\WindowsClient\GameUserSettings.ini").IsReadOnly
The first command sets the read-only attribute and returns silently. The second command queries the same file’s IsReadOnly property and prints True on success. If IsReadOnly returns False, the attrib +R step did not take effect: confirm the PowerShell session is elevated, confirm the file path resolved correctly (use Test-Path on the same path), and retry. The two-line command sequence is also safe to drop into a PowerShell script for repeatable provisioning across multiple machines.
GameUserSettings.ini syntax. A typo in a resolution value (or accidentally editing an adjacent key) can result in Fortnite refusing to read the file at all, in which case Fortnite generates a fresh default configuration and discards the manual edit entirely. AlphaRes writes the resolution programmatically and avoids this class of error, which is why Method 1 is recommended for non-power-users.
Method 3: File Explorer GUI
Players who prefer File Explorer over the command line can apply the lock entirely through the GUI. This is the slowest of the three methods, but it requires no installed software, no command-line knowledge, and no script execution. The procedure is identical in concept to Method 2: edit the file in Notepad, then set the read-only attribute. The difference is that the attribute is set through a checkbox in the file’s Properties dialog rather than from a command.
Edit the File in Notepad
Press Win+R, paste %LocalAppData%\FortniteGame\Saved\Config\WindowsClient\ (the folder, not the file), and press Enter. File Explorer opens at the WindowsClient folder. Right-click GameUserSettings.ini, hover over Open with, and choose Notepad. Edit the resolution lines as described in Method 2 (ResolutionSizeX, ResolutionSizeY, and the two LastUserConfirmed variants). Save with Ctrl+S and close Notepad.
Open File Properties
Right-click GameUserSettings.ini in File Explorer and choose Properties from the context menu. The Properties dialog opens on the General tab. The Attributes section is at the bottom of this tab and contains exactly two checkboxes: Read-only and Hidden. Read-only is the only one you need.
Tick Read-only and Apply
Tick the Read-only checkbox. Click Apply, then OK. Windows may prompt for administrator confirmation if your account is not the owner of the file (rare on a personal machine, common on corporate domains); click Continue if prompted. The dialog closes and the read-only attribute is now set on GameUserSettings.ini. Fortnite cannot rewrite the file until the attribute is manually cleared.
How to Verify the Lock Is in Effect
Verification has three independent checks. Each one tests a different layer of the lock. All three must agree before the lock is considered durable. If any one of them disagrees, the lock is partially or completely broken and the resolution will reset on the next Fortnite patch.
GameUserSettings.ini in Notepad. Find ResolutionSizeX and ResolutionSizeY. Both must show the custom values written by AlphaRes (or by the manual edit). If they show the desktop resolution instead, the write step failed and the lock is meaningless.(Get-Item "$env:LocalAppData\FortniteGame\Saved\Config\WindowsClient\GameUserSettings.ini").IsReadOnly. Output must be True. PowerShell reads the same NTFS attribute the Properties dialog displays, so disagreement between Check 2 and Check 3 indicates a stale Properties dialog cache (close and reopen).The fourth, behavioural verification is the most authoritative but also the slowest: launch Fortnite, play a session, wait for the next patch, launch Fortnite again, open Settings, and confirm the resolution still matches what was set. If the resolution is unchanged, the lock is fully durable. This check requires waiting for an actual Fortnite patch (Epic ships them roughly weekly during a chapter, less frequently between chapters), so it is best treated as a long-term confidence check rather than a same-day verification step.
What to Do If the Lock Breaks
The read-only lock is durable but not unbreakable. There are three documented scenarios in which the attribute is reverted or the file is recreated. Each has a specific recovery procedure. The recovery in all three cases is to reapply the lock, but the diagnostic step that identifies the cause matters because it determines whether additional preventive action is needed.
%LocalAppData%\FortniteGame\Saved\Config\WindowsClient\ to the antivirus exclusion list and disable any “registry cleaner” or “attribute cleaner” feature in optimizer tools. Reapply AlphaRes. Windows Defender does not exhibit this behaviour and is safe at default settings.GameUserSettings.ini. The old file (with read-only set) is replaced by a freshly created writable file; the old attribute does not transfer.Comparison: AlphaRes vs PowerShell vs GUI
All three methods produce the same end state: a custom resolution written to GameUserSettings.ini with the Windows read-only attribute set on the file. The choice between them is a matter of setup time, ease of use, and reversibility. The table below compares the three methods on the four dimensions that matter most for a typical Fortnite player.
| Dimension | Method 1: AlphaRes | Method 2: PowerShell | Method 3: File Explorer GUI |
|---|---|---|---|
| Setup time | Under 60 seconds (single Apply action handles everything). | 2 to 3 minutes (manual edit plus elevated PowerShell command). | 3 to 5 minutes (manual edit plus right-click Properties navigation). |
| Ease of use | One window, four fields, one button. No technical knowledge required. | Requires elevated PowerShell and familiarity with file paths and basic commands. | No commands but multiple right-click menus; navigation is verbose. |
| Persistence | Identical to other methods; lock is enforced by NTFS regardless of how it was set. | Identical to other methods. | Identical to other methods. |
| Reversibility | Apply with Read-only unticked, or use the Revert button in v1.1.0 to restore defaults. | Run attrib -R on the same path, then edit values back manually. |
Open Properties, untick Read-only, click Apply, then edit values manually. |
| Best for | Almost every Fortnite player. Recommended path. | Power users, scripted provisioning, locked-down workstations where AlphaRes cannot be installed. | Visual learners who prefer File Explorer over commands and have time to spare. |
| Failure modes | Forgetting to elevate (silently skips the lock step). | Notepad syntax errors that prevent Fortnite from parsing the file. | Same as Method 2, plus accidentally ticking Hidden alongside Read-only. |
FAQ
What does the read-only attribute actually do?
The Windows read-only attribute is a single bit in the file’s NTFS metadata that tells the operating system to deny any write request on the file. When a process attempts to open GameUserSettings.ini for write access, the kernel checks this bit, returns ERROR_ACCESS_DENIED (error code 5), and the write never reaches the disk. The check happens at the file-system layer, below any application logic, which is why Fortnite cannot bypass it without explicitly clearing the attribute first. Fortnite’s configuration reconciliation routine does not include a clear-attribute step; it assumes the file is writable and silently skips the rewrite when it is not. This is the entire mechanism that the lock relies on.
Why does AlphaRes need administrator rights to set the lock?
The file lives in %LocalAppData%, which is owned by the current user, so the resolution write itself does not require elevation. The read-only attribute change is treated as a privileged operation under several Windows configurations, particularly when User Account Control is set to its default level and the file’s owner does not match the current process token. Without elevation, AlphaRes can write the resolution but the attribute set silently fails. The Apply action returns success, the player believes the lock is in place, and the resolution resets on the next Fortnite patch. Always run AlphaRes via right-click Run as administrator to avoid this class of silent failure.
Does the lock interact with Easy Anti-Cheat?
No. Easy Anti-Cheat protects executable code, memory regions, and a small set of game-data files specific to Fortnite’s gameplay. GameUserSettings.ini is a user configuration file outside that boundary; EAC does not read it, write it, or check its attributes. The read-only lock is invisible to anti-cheat. The same applies to Epic’s BattlEye instances on platforms that use it. The lock is a standard Windows NTFS feature applied to a normal configuration file, with no relationship to anti-cheat scanning, no kernel-mode component, and no signature that any anti-cheat product flags. AlphaRes itself is also outside the EAC boundary; it never runs while Fortnite is active, since the file is locked at file-system level after Apply.
Will the lock survive a Fortnite reinstall?
No. A Fortnite reinstall (or an Epic Games launcher reinstall that removes Fortnite as part of the operation) deletes the entire %LocalAppData%\FortniteGame\Saved folder, including GameUserSettings.ini. The read-only attribute is a property of the file, so when the file is deleted, the attribute is deleted with it. After the reinstall, launch Fortnite once to let it generate a fresh default configuration file, then reapply the lock using any of the three methods documented in this guide. The same applies to manual deletions of the file or the WindowsClient folder, which some forum posts incorrectly recommend as a fix for unrelated issues. Treat the lock as resolution-specific persistent state, not as a Fortnite-wide setting.
Can the in-game Settings menu still change resolution while the lock is set?
No, and this is intentional. The Fortnite in-game Settings menu lets the player click around and click Apply, but the actual write to GameUserSettings.ini fails silently because the file is read-only. The UI shows the new resolution as if it had been applied, but on the next Fortnite launch the value reverts to whatever the locked file contains. To change the resolution after the lock is in place, run AlphaRes again with the new values: AlphaRes detects the read-only attribute, temporarily clears it, writes the new resolution values, and reapplies the attribute, all in a single Apply action. For Methods 2 and 3, run attrib -R first, edit, then attrib +R.
Does the lock survive Windows feature updates like 23H2 or 24H2?
Yes. The read-only attribute is stored in NTFS file-system metadata, not in any Windows-managed configuration store, so feature updates and quality updates leave it untouched. A major feature update like 24H2 may reorganize parts of the user profile or migrate certain settings to the cloud, but the %LocalAppData% path tree is preserved verbatim. The verification procedure earlier in this guide catches the rare exception: open File Properties after a feature update lands and confirm the Read-only checkbox is still ticked. If a feature update somehow disturbed the attribute (which has not been observed across the Windows 11 22H2, 23H2, and 24H2 cycles for the AlphaRes test rig), reapplying the lock takes under a minute.
What happens during a Fortnite chapter rollover?
Fortnite chapter rollovers (roughly twice per year, when the in-game season cycles to a new chapter) occasionally expand the configuration schema with new fields. When that happens, Epic’s update process deletes and regenerates GameUserSettings.ini rather than upgrading the existing file in place. The old file (with the lock set) is replaced by a fresh writable file with default values. The lock does not transfer to the new file. The recovery is to reapply AlphaRes after the chapter rollover lands; the new file accepts the resolution write and the attribute set cleanly. Routine weekly patches do not regenerate the file and do not break the lock; only chapter-level schema changes do, which is why this is uncommon enough to surprise players when it happens.
Is locking the file safe? Could it corrupt anything?
The lock is safe. The Windows read-only attribute is a standard NTFS feature documented since the original Windows NT release; setting it on a configuration file is a routine operation with no risk of file-system corruption, no risk to other Fortnite data, and no risk to the operating system. The worst case is that a future Fortnite update introduces a configuration field with a default value that differs from the locked file, in which case Fortnite either ignores the new field (most common) or refuses to load the file and generates a fresh default (rare, recoverable by reapplying AlphaRes). Neither outcome corrupts anything; both are reversible by clearing the attribute and editing the file. The lock cannot brick Fortnite, the Epic launcher, or Windows.
Can I lock other Fortnite settings the same way?
Yes, with caveats. The read-only attribute on GameUserSettings.ini locks every setting stored in that file, not just the resolution. Graphics quality, FPS cap, window mode, vsync, motion blur, and a long list of other entries are all in the same file and all become unwritable while the attribute is set. AlphaRes writes only resolution, FPS, and window mode by default, so the rest of the file is left at whatever values were present before. To lock graphics quality, view distance, anti-aliasing, or texture settings, edit those keys manually before applying the lock, or use Forknife (a separate tool from the same author) which writes the full graphics block. The lock is file-wide, not field-specific.
Does this work on Fortnite Mac, console, or cloud streaming?
No. The read-only attribute lock is Windows-specific. Mac Fortnite stores configuration under ~/Library/Application Support on HFS+ or APFS file systems, which use a different attribute model from NTFS; the equivalent operation exists but the path and the command are different. Console Fortnite (PlayStation, Xbox, Nintendo Switch) does not expose configuration files to the user at all; resolution is fixed by the platform. Cloud-streamed Fortnite via Xbox Cloud Gaming, GeForce NOW, or Epic’s own streaming runs the game on a remote server with a server-controlled configuration file that the player cannot modify. AlphaRes is Windows-only by design. Mac, console, and cloud players have no equivalent path to lock a custom resolution.
Where to Go Next
Continue setting up your Fortnite stretched-res rig
- How to Apply a Stretched Resolution in Fortnite Using AlphaRes: the full five-step walkthrough with resolution recommendations and GPU scaling configuration for NVIDIA and AMD.
- Fortnite Resets My Resolution After Update: Permanent Fix: troubleshooting guide for the specific symptom, with diagnostics for the failure modes that cause the reset.
- AlphaRes Settings Not Saving: Diagnostic Walkthrough: full debug procedure when AlphaRes appears to apply but the values do not stick.
- 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.