Reset a Frozen Infotainment Screen

Last updated: June 10, 2026

If the touchscreen in your Volkswagen Tiguan (Mk2, 2016–Present) has frozen, gone black, or stopped responding to taps, you can force the radio to reboot yourself in under a minute — no garage, no tools, and without losing any settings.

Which system is in your Mk2 Tiguan

The second-generation Tiguan (AD) launched on VW’s MIB2 platform: Composition Media, Discover Media (built-in navigation), or the top Discover Pro with the larger glass screen and gesture control, usually paired with the digital Active Info Display. The 2021 facelift moved higher trims to MIB3 with the touch slider beneath the screen. A freeze, boot-loop or black screen on any of these is almost always a software lock-up in the head unit — not a dead screen — and the cure is the same: hold the volume/power knob until it reboots.

Soft reset (reboot) the screen

Do this parked, with the ignition on so the unit stays powered.

1. Find the round volume/power knob beside the screen (lower-left on MIB2 cars; the slim control below the display on MIB3 facelift cars). It is also the on/off control.
2. Press and hold it — keep pressing through the point where the audio mutes.
3. After about 10–15 seconds the screen goes black; a stubborn unit may need up to 20 seconds.
4. When the VW logo appears, release the knob — the system is rebooting.
5. Allow up to a minute for the home screen and Active Info Display to reload.

Will this erase anything? No

The knob-hold reboot is completely safe. It does not wipe your radio presets, navigation favourites, paired phones, or settings — it just restarts the software, like rebooting a phone. Use it as often as the screen plays up.

If the screen stays frozen

• Hold longer. If 15 seconds did nothing, try again and hold a full 20 seconds before releasing at the logo.
• Try the SD/media card. On Discover Media/Pro cars, a corrupt navigation SD card can trigger a boot-loop — eject it, then reboot; if the unit comes back, reseat the card.
• Let the car sleep. Switch off, lock with the key, and walk away for about five minutes so the electronics power down; then unlock and restart — Tiguan owners often find the screen wakes up after this.
• Check for a software update. VW issued MIB2/MIB3 firmware for the Tiguan to fix freezes and reboot loops; a dealer can flash the latest build.
• Pull the fuse (last resort). With the car off, remove the infotainment fuse in the lower-left dash fusebox for 10 seconds and refit it to force a cold restart.

Factory reset (erases data — rarely needed)

A factory reset is separate from the reboot and only worth doing if you are selling the car or chasing a deep glitch. Go to Menu → Setup → System → Factory settings (“Reset to factory settings”). It erases presets, paired phones and navigation history, so only do it deliberately.

Frequently Asked Questions

Will I lose my sat-nav favourites or presets?

No. The volume-knob reboot keeps every preset, navigation favourite, setting and paired phone. Only the menu-driven factory reset clears them.

My Tiguan is stuck looping on the VW logo — what do I do?

A boot-loop usually needs a full power-down. Hold the knob for 20 seconds; if it keeps looping, eject the navigation SD card and try again, then lock the car for five minutes before restarting. Persistent loops point to a firmware update being due.

Does my Tiguan have MIB2 or MIB3?

Pre-2021 cars run MIB2 (separate rotary volume knob beside the screen); the 2021-on facelift fitted MIB3 with a slim touch slider below the display. The reboot works the same on both.

Is it safe to drive with the screen frozen?

Yes. The infotainment is separate from the engine and driving systems — you only lose audio and navigation. Reboot once you are safely parked.

The screen keeps freezing every few days — why?

Recurring freezes are usually old software or a corrupt navigation card. Have the dealer update the MIB firmware, check the SD card, and re-pair your phone before suspecting the hardware.

If a warning light or fault message stays on the dash after the reboot, it may have stored a diagnostic trouble code — you can look it up on autodtcs.com.