diff --git a/services/wolf.sh b/services/wolf.sh
index 49cbb8e..d09f5d6 100644
--- a/services/wolf.sh
+++ b/services/wolf.sh
@@ -5065,6 +5065,33 @@ time Cemu launches from ES-DE too.
    repo, not just reconnecting) reliably cleared it in testing, giving a
    fresh PulseAudio session to work with. Reconnect to a fresh Desktop
    session afterward and try again.
+
+   **If the TV device stays stuck on "Disabled" and won't take a real
+   device at all** (not just a one-time hang), this narrows down whether
+   it's PulseAudio itself with nothing to offer inside the container, or
+   Cemu choking on a device it can actually see:
+   \`\`\`bash
+   # Has this been a full Wolf restart, not just a reconnect, since it broke?
+   sudo ./setup.sh wolf
+
+   # Does PulseAudio inside the Desktop container see any output devices at all?
+   CONTAINER=\$(docker ps --format '{{.Names}}' | grep -i WolfDesktop | head -1)
+   docker exec "\$CONTAINER" pactl list short sinks
+   docker exec "\$CONTAINER" pactl info | grep -i "default sink"
+
+   # Cemu's own log — it logs audio device init/errors directly
+   GAME_DIR=\$(grep '^GAME_STORAGE_DIR=' $WOLF_DIR/.env | cut -d= -f2-)
+   find "\$GAME_DIR/retro-home/Cemu" -iname "log.txt" -exec cat {} \\;
+
+   # What settings.xml currently has for Audio (even while stuck "disabled")
+   cat "\$GAME_DIR/retro-home/Cemu/settings.xml" 2>/dev/null | grep -A5 -i "<Audio"
+   \`\`\`
+   An empty \`pactl list short sinks\` means there's no real fix on Cemu's
+   side to chase — the container itself has no audio sink for anything to
+   attach to. A populated sink list with Cemu still stuck points at Cemu's
+   own device-switch path instead, and \`log.txt\` / the \`<Audio>\` block
+   above are what to paste back for that to get root-caused rather than
+   guessed at.
 6. **Adding a second controller and the first one ends up driving both
    characters?** That's not a Cemu-specific bug — see
    "Multiple controllers" above (\`./manage.sh controllers\`).