Install the current Anniversary package
Open the install location for the exact Anniversary client selected in Battle.net. Copy ElvUI, ElvUI_Libraries and ElvUI_Options into that client's Interface/AddOns directory, not a neighboring Retail or Era folder.
- Exit the game first.
- Remove old ElvUI addon folders but preserve WTF.
- Extract the new package and copy all three directories.
- Verify the addon list before entering the world.
Current package versus old TBC tags
The public repository contains historical tags with names such as v2.48-tbc. Those tags document an earlier TBC Classic cycle and should not replace the current 15.18 package on a live interface 2.5.6 client unless you have a specific, tested reason.
Compatibility troubleshooting
An “out of date” warning usually means the installed TOC does not match the client. Confirm both the interface number and install directory before attempting a downgrade. The current API-supported package is the first troubleshooting baseline.
Verify the ElvUI download for TBC Anniversary
The ElvUI download for TBC Anniversary is tied to the live Anniversary client represented by interface 2.5.6 in Tukui's July 2026 metadata. Tukui reported ElvUI 15.18 as the current release and the public repository included a matching v15.18 tag. This verification separates the present multi-client package from historical repository tags such as v2.48-tbc that belonged to an earlier TBC Classic release cycle.
An old tag can contain recognizable Burning Crusade modules and still be wrong for the current Anniversary client. Blizzard may update the executable, security restrictions, frame APIs or interface number without changing the expansion theme. Start with the current supported package and use the interface value to confirm the client. Historical TBC tags are useful for archived environments, comparisons or controlled troubleshooting, not as the default download for a live Anniversary installation.
Version data can change. This page states the check date instead of presenting 15.18 as permanently current. Compare it with Tukui before installing after a game patch. A newer supported release should take priority over this preserved direct tag link.
Find the client folder for the TBC Anniversary archive
Battle.net can install TBC Anniversary beside Retail, Classic Era and progression Classic. Select the Anniversary client in the launcher and open its install location from the game-version menu. Then open that client's Interface/AddOns directory. Do not guess based on a neighboring folder name, because copying the archive into an inactive client produces a clean-looking directory that the running game never reads.
Extract the ElvUI download for TBC Anniversary and open the outer repository wrapper. Copy ElvUI, ElvUI_Libraries and ElvUI_Options directly into AddOns. The three directories must be siblings and must come from the same release. WoW should be able to find the client TOC under the ElvUI directory without passing through an extra ElvUI-15.18 folder.
Before replacing an existing setup, close WoW and back up WTF. Remove the three installed ElvUI folders and copy the three fresh folders. Do not merge new files over an old TBC tag, because modules removed or renamed across major release families can remain and load with the replacement code.
Set up ElvUI for TBC Anniversary gameplay
Run the built-in ElvUI setup on a new or copied profile before importing a community configuration. TBC group sizes, class resources, raid frames, threat information and action-bar requirements can differ from Retail or later Classic expansions. Choose a role baseline, set scale for the actual display and verify that unit frames, action bars, bags, chat, maps and nameplates work before adding external layout components.
Use /ec to open settings. A profile import changes ElvUI configuration but cannot supply missing fonts, texture packs, WeakAuras or optional plugins. If a screenshot includes custom raid indicators or media, read the creator's dependency list. Import into a separate profile name so the tested Anniversary baseline remains available for comparison and recovery.
Enable companion addons one at a time. When an error appears, disable the most recent addition and reload. A plugin written for a previous TBC Classic cycle may not support the current ElvUI download for TBC Anniversary even if its name still mentions TBC. Core ElvUI should be tested independently from every extension.
Troubleshoot current and historical TBC ElvUI builds
If ElvUI is missing from the AddOns list, inspect the active client path and directory depth. If it is out of date, compare the Anniversary client build with interface 2.5.6 and check Tukui for an update. If ElvUI loads but /ec fails, verify the Libraries and Options folders. If action or frame errors persist, test with optional extensions disabled and a clean profile.
Historical v2.x-tbc tags should be evaluated against the exact archived client for which they were created. Record the WoW build, tag, folder structure and required plugins. Keep a separate WTF backup because saved variables from ElvUI 15.x may not be understood by a much older TBC-specific release. Never overwrite the only working profile while testing a downgrade.
Return to the current ElvUI download for TBC Anniversary when the diagnostic purpose is complete. Remove the old three directories, copy the current three directories and allow the supported release to load on a copied profile first. This approach keeps the distinction clear between an archive that is historically authentic and a package that is appropriate for the current live client.
Before deleting the rollback archive, test the parts of the interface used in actual Anniversary content. Join a party, enter combat, switch targets, open the bank and bags, inspect raid frames, use class stances or forms and reload the interface. A city login only proves that the addon parsed; it does not exercise protected actions, group events or combat-state updates. Keep notes about the ElvUI release, client interface, profile name and optional plugins that passed this test.
If several characters use different roles, repeat a short check on each role profile. Tank threat colors, healer indicators and damage layouts can depend on separate filters and private settings. This final verification makes the ElvUI download for TBC Anniversary a maintained installation rather than a one-time ZIP copy with no recovery record. Preserve the dated backup until every active role profile has passed the same check.
When Battle.net updates or relocates the Anniversary client, use its game-version menu to reopen the live folder before copying another archive. Compare the executable location, addon timestamps and displayed ElvUI version. Multiple WoW installations can contain identical-looking TBC folders, so this path check distinguishes a failed package from a successful install placed where the running client cannot read it.
TBC Anniversary FAQ
Which ElvUI works with TBC Anniversary?
ElvUI 15.18 currently lists interface 2.5.6 support in the Tukui API.
Should I download a v2.x-tbc Git tag?
Not for the current live client by default. Those are historical TBC Classic tags; begin with the current package.