Last updated: June 2026. Coverage applies to AlphaRes v1.1.0 on Windows 10 22H2 and Windows 11 23H2/24H2 with Fortnite Chapter 7.
AlphaRes v1.1.0 is the current public release of the stretched-resolution lock utility for Fortnite as of mid-2026. It supersedes the original v1.0 line that introduced the tool, and the upgrade path between the two is one of the simplest in the entire competitive PC tooling space. There is no installer to uninstall, no configuration file to migrate, and no registry key to clean. The .exe gets replaced and the next launch runs the new version. Players who carried v1.0 through Fortnite Chapter 5 and Chapter 6 can move to v1.1.0 in roughly two minutes from start to finish.
This guide covers the changes that v1.1.0 introduced relative to v1.0, the safe upgrade procedure, what carries over and what does not, the verification steps that confirm the upgrade succeeded, and the one-click rollback path that exists because AlphaRes is fully portable. The article is the head of the AlphaRes Versions cluster on alphares.org. Readers looking for the full per-version changelog should consult the dedicated AlphaRes version history page; readers comparing AlphaRes v1.1.0 to manual .ini editing should jump to AlphaRes vs manual GameUserSettings.ini editing.
TL;DR: AlphaRes v1.1.0 in five bullets
- v1.1.0 is the current AlphaRes release as of 2026. It replaces the v1.0 line that shipped during the Chapter 5 and Chapter 6 era. As of public information at time of writing.
- The upgrade is drop-in. Replace the old
AlphaRes.exewith the new one, or simply launch the new file from a new folder. The utility is portable; nothing else needs to change. - The headline improvement is Fortnite Chapter 7 compatibility. The v1.1.0 build also exposes a refresh-rate parameter alongside width and height and accepts a wider range of resolution values than v1.0 did.
- The file size grew slightly to roughly 533 KB. No new dependencies were introduced. Windows 10 22H2 and Windows 11 23H2/24H2 are supported. The .exe remains a single portable binary with no installer.
- Rollback to v1.0 is supported by keeping the old EXE. Because AlphaRes has no installer and no stored profile, switching back is as simple as running the v1.0 file again.
Quick Version Reference
The table below summarises the two AlphaRes releases that exist in the public timeline as of mid-2026. This is intentionally lightweight: the full per-version changelog with build hashes lives at the AlphaRes version history page. The table here is enough to answer the single most common question on the support side, which is “which version do I have, and is it the latest one?”
| Version | Release window | File size | Notable changes |
|---|---|---|---|
| v1.0 (initial line) | Original release era, Fortnite Chapter 5/6 | ~520 KB | First public AlphaRes release. Width, height, FPS cap, window mode, read-only flag. |
| v1.1.0 (current) | 2026 release window | ~533 KB | Chapter 7 .ini key compatibility, refresh-rate parameter, expanded resolution range, Windows 11 DPI scaling fixes. |
What Changed in v1.1.0
The four cards below summarise the categories of change that v1.1.0 delivered over v1.0. As of public information at time of writing, the release notes describe four kinds of improvement: Chapter 7 .ini compatibility, an expanded resolution range, an exposed refresh-rate parameter, and a cluster of Windows 11 edge-case bug fixes. Players evaluating whether to upgrade should map their own situation onto these four categories.
Fortnite Chapter 7 GameUserSettings.ini compatibility
The most consequential change. Fortnite occasionally adjusts the key names inside GameUserSettings.ini between major chapter transitions, and the Chapter 7 build introduced shifts that v1.0 did not anticipate. The v1.1.0 update reworks the .ini parser to recognise the Chapter 7 key layout while remaining backward compatible with the Chapter 5 and Chapter 6 layouts.
Practical impact: a player upgrading to Chapter 7 with v1.0 may find that Apply writes to keys Fortnite no longer reads, leaving the resolution unchanged on next launch. Upgrading to v1.1.0 resolves that class of silent failure. As of public information at time of writing.
Expanded resolution range
The width and height fields in v1.1.0 accept a wider range of integer values than v1.0 did. The original release clamped inputs to a conservative band that covered the popular competitive picks (1280×1024, 1440×1080, 1600×1080, 1720×1080) but rejected unusual values that some players experiment with for FPS testing.
v1.1.0 widens the band downward to accommodate ultra-narrow stretched experiments such as 800×600 on internal-rendered tests, and upward to cover ultrawide native panels at non-standard pixel counts. The expansion is a quality-of-life improvement rather than a feature most players will notice in normal use.
Refresh-rate parameter exposed
v1.1.0 introduces a refresh-rate input alongside the existing width and height fields. The parameter writes to the relevant GameUserSettings.ini refresh-rate line so Fortnite launches at the requested Hz value on a multi-mode panel. Players running a 240Hz panel that occasionally drops to 60Hz mode can now lock the refresh rate from inside AlphaRes rather than fighting Windows display settings.
The refresh-rate field is optional. Leaving it blank preserves v1.0 behaviour, where Fortnite picks the panel default. As of public information at time of writing.
Windows 11 DPI scaling fixes
A handful of bug fixes address Windows 11 specific quirks. The most visible was a DPI scaling interaction that caused the AlphaRes window to render at half size on Windows 11 systems where the global display scale was set to 125% or 150%. The fix forces per-monitor v2 DPI awareness and resolves the half-size symptom on every panel tested in the v1.1.0 release window.
Other v1.1.0 fixes are smaller in scope and described in the dedicated changelog. Players on Windows 10 are unlikely to notice any of these fixes because the underlying bugs were Windows 11 specific.
How to Upgrade From v1.0 to v1.1.0
The full upgrade procedure runs end-to-end in roughly two minutes on a modern Windows machine. Five numbered steps cover the entire flow. Because AlphaRes is portable, the steps are deliberately simple: the only meaningful action is replacing one .exe with another.
Close Fortnite
Make sure Fortnite is fully shut down before running the upgrade. The Epic Games Launcher can stay open. Closing the game first prevents any race condition where Fortnite is mid-write to GameUserSettings.ini while AlphaRes is also touching it.
Close any running AlphaRes instance
If v1.0 is currently open in the system tray or as a window, close it from the title bar. Windows will not allow the .exe file on disk to be replaced while a process is using it. This step is the single most common cause of “permission denied” errors during the upgrade.
Download v1.1.0 from /download/
Go to the AlphaRes download page and grab the v1.1.0 .exe. The file is roughly 533 KB and is named AlphaRes.exe. Save the file directly to disk rather than running it from the browser. The download page itself documents the SHA-256 hash and additional verification details for players who want them.
Replace the old EXE (or drop the new one anywhere)
Two valid options. Option A: delete the old AlphaRes.exe and place the new file in the same folder, keeping the existing shortcut working. Option B: drop the new file into a different folder entirely and ignore the v1.0 file. AlphaRes is portable, so it runs from any location on disk. Option B is the safer choice because it leaves the v1.0 file available for rollback.
Launch v1.1.0 and click Apply
Right-click the new AlphaRes.exe and choose Run as administrator. The interface opens to default values; existing width and height settings are preserved if Fortnite’s GameUserSettings.ini is unchanged. Confirm the values match the previous configuration, set the new refresh-rate field if desired, and click Apply. The upgrade is complete.
What Carries Over and What Does Not
This is the section where AlphaRes upgrades differ most clearly from upgrades to traditional installed software. Because AlphaRes has no profile, no preferences file, and no registry footprint, the answer to “what carries over?” is a short list with a single significant entry.
What carries over
The read-only flag on Fortnite’s GameUserSettings.ini stays in place through the upgrade. The flag is a property of the .ini file on disk, not a property of the AlphaRes install. Replacing the .exe does not touch the file and does not alter the flag. Players who locked their resolution under v1.0 will find Fortnite still cannot overwrite the file after launching v1.1.0 for the first time.
What does not carry over
Nothing significant. AlphaRes has no stored profile, no recent-resolutions list, no theme preference, no window-position memory, no log file, and no telemetry. The v1.0 .exe writes nothing to disk outside its own folder and outside Fortnite’s GameUserSettings.ini. There is, in a literal sense, nothing for v1.1.0 to migrate. The interface opens to defaults on first launch, the player enters their preferred values, and the configuration matches whatever the previous AlphaRes session left in GameUserSettings.ini.
Verifying the Upgrade Worked
Two minutes of verification confirm the upgrade succeeded. The process is intentionally minimal because AlphaRes itself is minimal.
First, open the freshly upgraded AlphaRes and check the version number shown in the title bar or about dialog. The string should read v1.1.0 rather than v1.0. If the version still reads v1.0, the launched .exe is the old one; the wrong file is in the wrong folder, or the desktop shortcut still points at the v1.0 path.
Second, confirm the width and height fields populate to the values previously written to GameUserSettings.ini. Click Apply. Launch Fortnite from the Epic Games Launcher and check Settings > Video > Display Resolution. The dropdown should show the same values that AlphaRes wrote. If both checks pass, the upgrade is verified and the player can return to normal play.
If Something Breaks: Rollback Procedure
AlphaRes.exe available. Move it to C:\Tools\AlphaRes-v1.0\ or any other folder before deleting it. Rollback only works if the old binary still exists on disk.
Rollback exists because every release of AlphaRes is portable and self-contained. There is no install registry to corrupt, no shared dependency that might lock to one version, and no service that one version expects to find running. If v1.1.0 misbehaves on a specific player’s setup, the recovery procedure has three steps: close the v1.1.0 window, navigate to the folder where the v1.0 .exe was archived, and run the v1.0 binary instead. Click Apply. The previous behaviour is fully restored.
One caveat applies. Players running Fortnite Chapter 7 may find that v1.0 no longer writes to the .ini keys Fortnite reads, because the Chapter 7 .ini layout shifted. If rollback to v1.0 is necessary on a Chapter 7 build, the resolution lock can be performed by editing GameUserSettings.ini by hand instead. The procedure for that workaround lives at AlphaRes vs manual GameUserSettings.ini editing, which documents the exact lines to change and the read-only flag to set after editing.
Will v1.1.0 Work on Older Fortnite Chapters?
Yes. The .ini key names that drive the resolution lock stayed compatible across Chapters 5, 6, and 7. v1.1.0 was built to recognise the Chapter 7 key layout while preserving the older recognisers, which means players still on a non-current Fortnite build (private servers, beta channels, internal test environments) can use v1.1.0 without any issues. The added refresh-rate parameter is also chapter-agnostic because the underlying .ini line existed in earlier chapters too. The only situation where v1.1.0 should be reverted is the case described in the rollback section, where a specific player’s machine triggers an unusual Windows-side interaction. For ordinary Fortnite players on any chapter from 5 onwards, v1.1.0 is the recommended build.
Should You Upgrade?
Future Versions
AlphaRes development is upstream-controlled and the public release cadence is conservative. The v1.1.0 release closed several long-standing issues that accumulated during the Chapter 5 and Chapter 6 era; future releases would likely target features that the community has been requesting since the v1.0 days. The most-requested missing feature is profile save and load, which would let competitive players store named configurations (a “1600×1080 240Hz scrim” profile and a “1920×1080 144Hz casual” profile, for example) and switch between them with one click. A built-in update checker that surfaces the latest .exe version on launch is the second-most-requested feature. Broader operating system coverage, particularly explicit Windows on Arm support, has come up in support threads as well.
None of these are confirmed for any specific future build. As of public information at time of writing, no v1.2 release is announced. Players who want to be notified when a future version ships should bookmark the version history page, which receives a new entry whenever a new release lands.
Related Guides
Pair this guide with the rest of the AlphaRes knowledge base. These cover the adjacent setups, fixes, and comparisons you’ll run into when locking custom stretched resolutions in Fortnite.
- AlphaRes for Fortnite, Complete Guide (2026), The full reference for AlphaRes itself: features, install, safety, comparisons, and links to every cluster guide.
- AlphaRes Download, Latest v1.1.0 for Windows 10/11, Direct download for the verified AlphaRes v1.1.0 binary, with file specs, SHA-256 verification, and trust signals.
- How to Install AlphaRes on Windows 10/11 (2026 Step-by-Step), Clean install on Windows 10/11 with SmartScreen handling, prerequisites, and first-launch verification.
- Is AlphaRes Safe? A 2026 Security Audit, Independent 2026 security audit with VirusTotal results, source-code review, and behavioral analysis.
- AlphaRes on Windows 11: Setup, DPI Scaling, and Known Issues (2026), Complete AlphaRes guide for Windows 11 covering install paths, DPI scaling interactions, known issues, and the recommended setup workflow.
Frequently Asked Questions
What’s new in AlphaRes v1.1.0?
v1.1.0 introduces four categories of change relative to the v1.0 line. The headline change is Fortnite Chapter 7 GameUserSettings.ini compatibility, which keeps the resolution lock working through the .ini key adjustments that Chapter 7 introduced. The release also exposes a refresh-rate parameter alongside the existing width and height fields, widens the accepted resolution range to support unusual pixel counts at both ends of the spectrum, and ships a cluster of Windows 11 specific bug fixes (most visibly a DPI scaling interaction that caused the AlphaRes window to render at half size on systems with global scale set to 125% or 150%). The file size grew from roughly 520 KB to roughly 533 KB. As of public information at time of writing.
How do I upgrade from v1.0 to v1.1.0?
Five steps. Close Fortnite. Close the running AlphaRes window. Download v1.1.0 from the AlphaRes download page. Replace the old AlphaRes.exe with the new file, or drop the new file into a different folder entirely (AlphaRes is portable, so it runs from any location on disk). Right-click the new .exe, choose Run as administrator, click Apply. The full procedure runs end-to-end in roughly two minutes on a modern Windows machine. Because AlphaRes has no installer, there is no uninstall step for the old version unless the player chooses to delete the v1.0 file manually after the upgrade is verified.
Will my settings carry over after the upgrade?
The relevant settings already live in Fortnite’s GameUserSettings.ini, not inside AlphaRes. AlphaRes has no stored profile, no preferences file, and no recent-resolutions list, so there is technically nothing inside AlphaRes itself to carry over. What does carry over is the read-only flag on the .ini file: that flag is a property of the file on disk, not of the AlphaRes install, and it stays in place through the upgrade. The first time v1.1.0 launches, the interface opens to defaults; clicking through to Fortnite confirms the previous resolution is still active because the .ini was not touched.
Can I roll back to v1.0 if something breaks?
Yes. Rollback is supported and instant. The recommended insurance is to keep the v1.0 .exe archived in a separate folder (such as C:\Tools\AlphaRes-v1.0\) before deleting it from the active folder. If v1.1.0 misbehaves, close the v1.1.0 window, run the archived v1.0 .exe, and click Apply. There is no install registry to clean up because AlphaRes has no installer. One caveat: v1.0 may not handle the Chapter 7 .ini key layout, so on Chapter 7 builds the rollback may require a manual .ini edit instead. The dedicated AlphaRes vs manual .ini editing guide on alphares.org documents that procedure.
Does v1.1.0 work on Fortnite Chapter 6?
Yes. v1.1.0 was built to recognise the Chapter 7 GameUserSettings.ini key layout while preserving compatibility with the Chapter 5 and Chapter 6 layouts. Players on a Chapter 6 build (or earlier, in private-server or beta-channel scenarios) can run v1.1.0 without any issues. The added refresh-rate parameter is also chapter-agnostic because the underlying .ini line existed in earlier Fortnite builds. The only practical reason to stay on v1.0 in a Chapter 6 setup is inertia: if v1.0 already works for the player, the upgrade is optional rather than urgent.
What’s the file size of v1.1.0?
Roughly 533 KB, up from roughly 520 KB for the v1.0 line. The increase reflects the refreshed .ini parser, the additional refresh-rate handling code, and the Windows 11 DPI scaling fix. The .exe remains a single portable binary with no external dependencies, no DLLs to ship alongside, and no installer wrapper. The download page on alphares.org documents the exact file size and SHA-256 hash for the current build, which players can use to verify a fresh download against the published values.
Is v1.1.0 free?
Yes. AlphaRes v1.1.0 is free, as every previous release was. The utility carries no upgrade fee, no subscription tier, no premium features behind a paywall, and no advertising. The v1.0 to v1.1.0 transition does not introduce any monetisation. Players who downloaded v1.0 for free during the Chapter 5 and Chapter 6 era can download v1.1.0 for free during the Chapter 7 era through the same alphares.org download page. The AlphaRes pricing model is documented at length on the safety and pricing pages of alphares.org for players who want the full context.
Where do I download AlphaRes v1.1.0?
The official source is the AlphaRes download page on alphares.org. The download page documents the file size, SHA-256 hash, and SmartScreen handling notes for the current build. Players should treat any other source as suspect until the SHA-256 of the downloaded file matches the value published on the official download page; mismatched hashes indicate the file has been altered or repackaged. The same advice applies to v1.0 archives floating around the web, which often lack any verifiable provenance.
Will Fortnite ban me for using v1.1.0?
No. AlphaRes v1.1.0, like every previous release, runs entirely outside the Fortnite process. It does not inject code, it does not read or write the game’s memory at runtime, and it does not communicate with Fortnite’s servers. All it does is edit GameUserSettings.ini on disk while Fortnite is closed, then optionally set the read-only flag on that file. Both operations are exactly what a player editing the .ini by hand in Notepad would do. Easy Anti-Cheat does not flag .ini edits performed before the game launches. The full safety analysis, including a behavioural audit of the .exe, lives on the AlphaRes safety page.
Why isn’t there a v2.0 yet?
AlphaRes development is upstream-controlled and the public release cadence is conservative. The v1.x line has been sufficient for the use case (lock a chosen stretched resolution in Fortnite without manual .ini editing) since the original release, and the v1.1.0 update closed the most pressing compatibility gap that emerged during Chapter 7. A v2.0 release would imply a rewrite scope large enough to break compatibility with the existing v1.x workflow, which is not a change the project has signalled. As of public information at time of writing, no v1.2 release is announced either, and v2.0 is even further out.
Does v1.1.0 have an auto-updater?
No. AlphaRes v1.1.0 does not include an in-app update checker or auto-updater. The .exe does not phone home to alphares.org or any other server to check for new versions. Players who want to track new releases should bookmark the AlphaRes version history page on alphares.org, which gets a new entry every time a new release lands. The absence of an auto-updater is consistent with the broader AlphaRes design philosophy: no telemetry, no background activity, no network behaviour. Adding an in-app update checker is one of the more frequently requested features for a hypothetical v1.2 release, but nothing is confirmed.
Will I lose my read-only lock during the upgrade?
No. The read-only flag on Fortnite’s GameUserSettings.ini is a property of the file on disk, not a property of the AlphaRes install. The upgrade replaces the AlphaRes .exe; it does not touch GameUserSettings.ini. Whatever the v1.0 session left on the file (resolution values, FPS cap, window mode, read-only flag) remains in place until something explicitly changes it. The first time v1.1.0 launches and Apply is clicked, the same flag-clearing then re-applying behaviour runs, just as v1.0 did. The lock is preserved through the upgrade in every realistic scenario, including the case where the player upgrades while Fortnite is closed and the .ini was last written by v1.0.