Patched DLL
The reviewed five-method bypass build. 393,216 bytes.
Download XIVLauncher.Common.dllSHA-256
CF251AA022B91D3753DAEE4124CE52F71B457649BE17C8258F31E420B11C1221
Use Aethertek's DLL Bypasser to enable plugin use post-maintenance.
It bypasses the usual dev and beta key gates, allowing Dalamud and your plugins to be used directly while official post-maintenance enablement is still pending.
This package replaces XIVLauncher.Common.dll with a statically reviewed build that relaxes Dalamud's game-version and branch-applicability checks. It lets XIVLauncher continue through its existing Dalamud branch and update flow when the normal version gate has not yet been opened.
It does not make an incompatible Dalamud build safe, repair plugins after a game update, bypass account authentication, or guarantee that the launcher or game will work. The files were verified statically; use in the live launcher remains at your own risk.
This bypasser is tied to one reviewed XIVLauncher.Common baseline. Check the DLL currently installed on your PC before continuing:
The reviewed five-method bypass build. 393,216 bytes.
Download XIVLauncher.Common.dllSHA-256
CF251AA022B91D3753DAEE4124CE52F71B457649BE17C8258F31E420B11C1221
The matching official/default file, supplied with a .bak suffix. 394,752 bytes.
SHA-256
F141AA83639E93691C7F13C52E5BA4F0A7BB0A4549B4EDD9A134650BB990F948
Your browser may warn that DLL files can be harmful. Only keep these files when the downloaded names, sizes, and SHA-256 hashes match the values above.
Exit XIVLauncher from the Windows notification area as well as closing its window. If Windows says the DLL is in use later, open Task Manager and make sure no XIVLauncher process remains.
Open PowerShell, run the command below, and apply the compatibility gate above. Do not proceed on an unknown hash.
Use the two buttons above. If your browser adds (1) or another suffix, remove that suffix only after confirming which download is which.
Press Windows + R, paste this path, and press Enter:
Before replacing the official DLL, copy the installed file to XIVLauncher.Common.dll.before-bypasser. Only treat that copy as a clean rollback if the installed hash was the expected official hash.
From Downloads, copy both files into the XIVLauncher current folder:
XIVLauncher.Common.dll replaces the file with the same name.XIVLauncher.Common.dll.bak stays beside it for rollback.Choose Replace the file in the destination when Windows asks.
Run the installed-file check again. It must now report the full patched hash shown below.
Launch normally and confirm that Dalamud reaches the expected branch/update flow. Static verification cannot guarantee acceptance by the live launcher or game, so roll back immediately if startup or updating behaves unexpectedly.
%LOCALAPPDATA%\XIVLauncher\current.XIVLauncher.Common.dll.bak over XIVLauncher.Common.dll.Expected rollback hash: F141AA83639E93691C7F13C52E5BA4F0A7BB0A4549B4EDD9A134650BB990F948
Recheck the new official DLL hash. If it is not the reviewed official hash on this page, do not reinstall this old bypasser. A new launcher build needs a new static comparison and compatible patched build.
XIVLauncher is still running. Exit its tray icon or end the remaining XIVLauncher process in Task Manager, then retry the copy.
Do not install the file. Delete that download, download it again from this page, and recheck. A mismatched hash is unresolved even when the filename looks correct.
Roll back first. This bypass only changes version and branch-selection behavior; it cannot make an outdated Dalamud build compatible with a changed FFXIV client.