Deadlock FATAL ERROR: "Unable to find child" (fix)
Deadlock shows "FATAL ERROR: Unable to find child 'ShopFilters' in layout file 'panorama\layout\citadel_hud_hero_shop.xml'" (or another child name and layout file) and closes, either at launch or when a screen opens.
Also appears as: unable to find child, deadlock fatal error unable to find child, deadlock fatal error: unable to find child, unable to find child 'shopfilters' in layout file, unable to find child 'healthbar fill' in layout file, unable to find child in layout file panorama layout, citadel_hud_hero_shop.xml, citadel_hud_top_bar_player.xml, deadlock layout file fatal error mods
The game's HUD layout files no longer match what the game expects. The two players who posted it after the September 29, 2026 update (child 'ShopFilters', then 'HealthBar Fill' in citadel_hud_top_bar_player.xml) both said they play with mods. It also appeared in June 2026 (child 'idolcashinmeter', and 'KothCashlnMeter' after the June 30 minor update) and in May as 'SteamProfileOverlay' when clicking a profile, where a reply blamed mods. Replies on the newest threads said to disable mods (one also suggested -dx11, which the poster didn't confirm). Nobody reported a fix that worked, and we saw no reply from Valve.
Fix it, step by step
Disable all mods and remove any FPS config
Every report of this dialog came from a player running mods. A reply to the September 29 'ShopFilters' report said to disable mods after the major update, and in the Deadlock Community Discord more than a dozen modded players hit the same layout-file dialogs after that update (see [Deadlock FATAL ERROR after the update](/deadlock/errors/fatal-error-mods/)). Turn mods off in your mod manager and remove any community "FPS config" before relaunching.
Verify Deadlock's files in Steam
In Steam, right-click Deadlock > Properties > Installed Files > Verify integrity of game files, which restores the game's own layout files if a mod replaced them. Players in the Discord reports say this restored the originals after removing mods; none of the Steam posters for this exact dialog came back to confirm it.
- NoteUnconfirmed
Valve hasn't commented on this error, so nothing here is confirmed. If you rely on a mod, check whether its author has updated it for the latest patch before turning it back on. If it's error 126 instead, see the [Deadlock error 126 page](/deadlock/errors/error-126/).
Sorted. Glad that worked.
Nothing worked. Here's what to do next.
You've ruled out every step on this page, which is useful. Send this to support or drop it in the community Discord so nobody makes you repeat yourself.
Hit this error? Leave a comment
Say where you are, what you see on screen, and whether any fix worked for you.
No links. Anonymous, no account. Keep it about the game.
What people are saying
Notes from players who've hit this one — no time limit, an answer from months ago is still an answer.
- Nothing reported here yet.
From isthisgamedownMatched on ""
From isthisgamedownMatched on ""
From isthisgamedownMatched on ""