You click a snapshot in the Recall timeline — or launch Recall from the taskbar — and nothing happens. Maybe the window flashes and vanishes, maybe it hangs on a blank screen, maybe the app crashes outright. Meanwhile, behind the scenes, Recall may still be capturing away happily. The viewer — the part you actually look at — is the broken piece.

This separation matters for diagnosis. The viewer is a presentation layer: it reads the snapshot store and draws the timeline UI. When it fails while capture continues, the fault sits in the viewer app, its data, or the graphics stack — not the capture pipeline.

This guide gives you six fixes in technician order: confirm the scope, repair the app package, fix its data, update the graphics stack, and reset as a last resort. Work through them in sequence.

Why this happens

  • Corrupted viewer app package: A half-applied Windows update can leave the viewer’s files mismatched — new enough to launch, broken enough to crash on load.
  • Damaged snapshot database: If the viewer chokes parsing a corrupt database entry on startup, it dies before drawing anything. The capture service tolerates the same corruption because it only writes.
  • Broken graphics driver: The viewer renders image-heavy timeline cards through the GPU. A faulty display driver turns that rendering into a crash or a permanently blank window.
  • Crashed dependency service: The viewer depends on background Recall services being in a sane state. If one is wedged, the viewer waits forever or times out on launch.
  • Corrupted viewer cache or settings: The viewer’s own local cache and preferences can corrupt independently of the snapshot store, producing a crash loop that survives reboots.
  • Conflicting overlay or capture software: Screen-recording tools, overlays, and some “game booster” utilities hook the same presentation APIs the viewer uses and can prevent its window from initializing.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Confirm the scope of the failure

Two minutes of scoping tells you whether you are fixing a viewer, a service, or a whole-Recall problem — and each has a different repair path.

  1. Check whether new snapshots are still being captured: look at the Recall indicator or check the timeline’s latest timestamp from Settings if you can reach it.
  2. Try launching Recall from the taskbar, from Start search, and from Settings — note whether all three fail identically or only one entry point breaks.
  3. Open Task Manager while attempting a launch and watch whether the Recall process appears briefly and dies, never appears, or appears and hangs.
  4. If capture is healthy but every launch path fails, you have a pure viewer fault — continue here. If capture is also dead, a corrupted Recall database may be the deeper cause.
  5. Write down the exact behavior (crash, hang, blank window) — you will need it if you reach the Feedback Hub step.

Fix 2: Repair the Recall app package

Windows can repair the viewer’s app package in place — re-registering its files without touching your snapshots, settings, or history. This fixes the half-updated-package failures from Windows updates.

  1. Open Settings > Apps > Installed apps and find the Recall/Windows Recall entry.
  2. Open its advanced options and use Repair (not Reset yet) — this re-registers the package files.
  3. Try launching the viewer again; a successful repair shows here immediately.
  4. If Repair is unavailable or changes nothing, run sfc /scannow in an elevated Command Prompt to fix corrupted system files the viewer depends on.
  5. Microsoft documents app repair flows in the Windows support hub if your Settings layout differs slightly by build.

Fix 3: Clear the viewer’s cache and local data

The viewer’s own cache — separate from the snapshot store — can corrupt and crash the app on every launch. Clearing it forces a clean rebuild while your actual snapshot history stays untouched.

  1. In the Recall app’s advanced options (Settings > Apps > Installed apps > Recall), look for storage/cache options and clear cached data.
  2. If no cache option is exposed, sign out and back in — this releases locked per-user app data the viewer holds.
  3. Restart the PC with a full shutdown (hold Shift while clicking Shut down) to clear in-memory app state.
  4. Launch the viewer and give it a full minute — first launch after a cache clear rebuilds data structures and is slower than normal.
  5. Do not confuse this with clearing snapshots: you are clearing the viewer’s scratch data, not your timeline.

Fix 4: Update or reinstall the graphics driver

A viewer that crashes or shows a blank window while everything else in Recall works is a classic graphics-stack symptom — the app dies the moment it tries to render its image-heavy timeline through a broken driver.

  1. Open Device Manager, expand Display adapters, and note your GPU and driver date.
  2. Download the latest driver for your exact laptop model from Dell , HP , or Lenovo support and perform a clean install.
  3. Restart and launch the Recall viewer before opening any other graphics-heavy app, so you get a clean test.
  4. If the viewer now opens, the driver was the fault — keep an eye on it after future driver updates.
  5. Heavy memory pressure can mimic driver faults in image-heavy apps, so if the whole system feels starved, the live captions high memory usage guide covers diagnosing that class of problem.

Fix 5: Reset the viewer app as a last resort

When repair, cache clears, drivers, and service restarts all fail, resetting the viewer app returns it to factory state. This is still an app-level reset — your snapshot store survives — but you will lose viewer preferences.

  1. In Settings > Apps > Installed apps > Recall, use Reset (the stronger option below Repair).
  2. Restart the PC, then launch the viewer and let it fully initialize — expect it to take longer as it rebuilds its local structures from the snapshot store.
  3. If the viewer opens, spot-check several timeline entries to confirm your history rendered correctly.
  4. If even a reset viewer will not open on current drivers with healthy services, document the exact failure and file it in Feedback Hub under Privacy > Recall — you have eliminated every local cause, and the fault class resembles stubborn system-service failures like the print spooler crashing on ARM laptops .
  5. Do not reinstall Windows for this. A viewer that survives an app reset is either a build-level bug (fixed by the next cumulative update) or a hardware-adjacent fault, and neither is solved by wiping the OS.

Closing

A viewer that will not open is an app-layer problem wearing a scary disguise — your history is almost certainly fine underneath. Repair the package, clear its cache, fix the graphics stack, and restart its services.

Frequently asked questions

Why won't the Recall snapshot viewer open?
The viewer is separate from the capture service and fails for its own reasons: corrupted app data, a damaged snapshot database, broken graphics drivers, or a crashed background service it depends on.
Is my snapshot history safe if the viewer won't open?
Usually yes. The capture service and snapshot store are independent of the viewer — history keeps being recorded while the viewer refuses to launch. Do not delete snapshots to fix a viewer problem.
Can a Windows update break the Recall viewer?
Yes. Feature updates occasionally leave the viewer’s app package half-updated while the rest of Recall works fine. Repairing or re-registering the app package fixes this without touching your data.
Should I reinstall Windows to fix the viewer?
No — that is drastic overkill. Every viewer failure here resolves at the app, driver, or database level. An OS reinstall is never the right first answer for one misbehaving component.