Version Mismatch
Who should use this guide
Use this page when the client says your version is not supported, still shows the old build after update, or reports a mismatch between local and required version numbers.
Before you begin
- Confirm the target version in the changelog or support instruction - Make sure you know which folder you are launching from - Stop all copies of the client before changing files
Steps
1
Check the version requirement
Confirm the exact required version in Changelog or the support note before doing anything else.
2
Verify the actual folder you launched
Many version mismatches happen because a shortcut points to an older folder while the newer version is stored elsewhere.
3
Remove mixed-version folders
If you have several copies of the client, keep only the intended folder or rename the old ones so they cannot be launched accidentally.
4
Reinstall or update cleanly
If the version still does not match, redownload the correct package and repeat the install in a fresh folder.
Screenshot reference
Version mismatch example
Replace with a screenshot showing the local version, required version, and the install folder path.
Screenshot placeholder
Replace this block with a clear screenshot of the exact step described in this guide.
Common questions
Why does the client still show the old version after I updated?
You are probably launching the wrong folder, or the update wrote into a different path than expected.
Can I manually copy files from one version folder to another?
That often creates a worse mismatch. Use a clean package instead.
Support asked me to use a previous stable build. Is that still a mismatch?
No, if support explicitly told you to use that version for testing or rollback.