Nine times out of ten it is an addon, not the game. The Appearances tab loads your whole collection at once, so a transmog or collection addon scanning every slot spikes memory until WoW closes. Disable all addons and retry; if the crash stops, re-enable in halves to find the culprit. If it still crashes clean, run Scan and Repair.
Fix it in this order
- Disable every addon. Character select, AddOns button, Disable All, reload. Open the transmog window. No crash means an addon is the cause.
- Bisect the list. Re-enable half your addons, test, then half of whatever half still crashes. Four or five reloads usually isolates it. Collection scanners, appearance trackers and anything that indexes every item you own are the usual suspects.
- Update or drop the culprit. An outdated addon written against the previous patch's API is the single most common reason the wardrobe UI dies mid-load.
- Clear the cache. Close the game, delete the Cache folder in your World of Warcraft directory. It rebuilds itself and costs you nothing — no settings, no keybinds.
- Reset the UI properly. Rename Interface, WTF and Cache (add "_old") instead of deleting them, so you can restore your settings if this was not the problem.
- Scan and Repair. Battle.net launcher, cog icon next to Play, Scan and Repair. Fixes corrupted model or texture files, which is exactly what a window full of 3D previews would choke on.
- Update your GPU driver, then try the other graphics API in System → Advanced. The wardrobe renders live character models, so a shaky driver shows up there before it shows up in open world.
- Lower model and shadow quality if you are on older hardware or short on VRAM. Dropping graphics one preset often makes the Appearances tab survivable.
Why only transmog and nothing else?
Because it is one of the heaviest windows in the game. It queries thousands of appearance entries and renders your character live, so it exposes memory leaks and bad addon code that normal questing never touches.
Same reason people report crashes at a transmog vendor but nowhere else — the vendor opens that identical collection UI.
Will deleting Cache lose my collection?
No. Your appearances, mounts, pets and toys live on Blizzard's servers, not in a local folder. Cache is disposable temp data and the client rebuilds it on the next login.
WTF is the one to be careful with — that holds your settings and addon config, so rename it rather than delete it.
It crashes with zero addons. Now what?
Then it is client files, drivers or hardware. Run Scan and Repair first, update the GPU driver second, and check whether you are running out of VRAM at your current settings.
If the crash still repeats on a clean install with no addons, that is a genuine bug worth reporting to Blizzard with your crash log rather than something you can patch out yourself.
Is there a way to test without losing my whole setup?
Yes. Do the addon bisect first and only touch folders after. Most people fix this at step two and never need to reset the UI at all.
Keep the renamed folders around for a week. If the crash was elsewhere, you drop your settings straight back in.
Once the client behaves, the harder part is actually filling the wardrobe — old raid runs, PvP sets and long collection chains take real hours. If you would rather have a vetted human player help you get there, PewPewShop runs coaching and play-together progression help, including a Full Transmog Project from EUR 70 and the Elite PvP Transmog Set at 1800 rating from EUR 44.99. Real players, no bots, no cheats.