Your folders were previewing beautifully on Monday; Windows updated on Tuesday; by Wednesday every PSD is a generic icon again. The timing feels damning, and sometimes an update really does change shell behaviour. More often, an update cycle disturbs the neighbourhood SageThumbs lives in: Explorer restarts with a rebuilt cache, settings drift, registrations are refreshed unevenly, or on Windows 11 a redesigned menu hides an entry that still exists. SageThumbs itself has not changed since version 2.0.0.23 of 9 May 2017 (GPL v2 or later), and its official system list runs to Windows 10, with Windows 11 use being community experience rather than an official promise. Run this checklist in order before concluding anything dramatic; most post-update cases resolve in the first four steps.
Checklist steps 1 to 3: Restart, views, and the missing menu
Step 1: restart the computer once more, cleanly, even if the update already restarted it. Post-update first boots carry one-off setup work, and a second ordinary boot is a surprisingly effective baseline. Step 2: recheck the two Explorer settings that decide whether thumbnails can appear at all: an icon view (Medium or larger) in the affected folders, and Always show icons, never thumbnails unchecked in File Explorer Options. Updates and feature upgrades have been known to reset view preferences, and a folder flipped to Details view looks exactly like a broken handler until you notice the view changed. Step 3, for Windows 11: if it is the right-click preview you miss, remember it lives under Show more options on the classic menu. Updates sometimes coincide with users noticing the two-layer menu for the first time; the entry has usually not vanished, it has been filed one click deeper since the Windows 11 design arrived.
Checklist steps 4 and 5: Cache and configuration drift
Step 4: clear and rebuild the Windows thumbnail cache using Disk Cleanup with Thumbnails ticked, then reopen your main image folders in an icon view and let previews regenerate patiently. Update cycles corrupt or partially invalidate caches with some regularity, and the cache is the cheapest component in the whole system to rebuild from scratch. Step 5: open the SageThumbs page in Control Panel. Its mere presence proves the installation survived; while there, confirm the maximum file size option still matches your work, because a reset configuration that suddenly skips your large files presents as an update breakage that is really a settings change. If the Control Panel page is missing entirely, the update is not your primary suspect: something removed or damaged the installation, and you should move directly to the repair step.
Checklist step 6: Repair the installation cleanly
Reinstall SageThumbs over the top, or uninstall and reinstall if registrations look damaged, using the verified official installer sagethumbs_2.0.0.23_setup.exe (2,242,393 bytes, SHA-256 705d743e28b487e34a4a7245a0dbc303a10e45ba0fd9e4da4101c8cdf506839a). Verify the hash before running it so the repair starts from a known-good file. Restart Explorer or the PC afterwards and rebuild the cache once more so the repaired handler is judged against fresh requests, not pre-update remnants. Watch for security software interference during this step: if your protection product quarantined SageThumbs components around update time, its history will show it, and the remedy lies in that product’s allowlist rather than in repeated reinstalls that keep meeting the same removal.
When it really is an incompatibility
Occasionally a Windows change genuinely alters shell extension behaviour for a 2017 extension, and honest diagnosis should allow that conclusion once settings, cache and registration causes are excluded. Signs pointing that way: a clean install on a healthy profile behaves identically, other classic shell extensions broke in the same update, and community reports cluster on the same build. Your practical options then are patience (servicing updates frequently follow and quietly restore compatibility), workarounds (preview pane and editor-based browsing for critical formats), and keeping the installation ready rather than repeatedly reinstalling. Also keep the format boundary out of this diagnosis: files in formats SageThumbs never covered, such as WebP, SVG, HEIC, AVIF, INDD and CR3, were not broken by the update, and AI, EPS and PDF previews still depend on AFPL GhostScript 8.54 being installed alongside SageThumbs.
Frequently asked questions
A Windows update broke SageThumbs. Should I uninstall the update?
Almost never as a first response. Work the checklist: settings, cache and a clean repair resolve most post-update cases without touching the update, which also carries security fixes you should keep. Reserve update rollback for cases where many components broke and you have a considered reason.
Why did only my largest files lose previews after the update?
That pattern suggests configuration drift, typically the maximum file size option, or a partially rebuilt cache that has only regenerated small files so far. Confirm the SageThumbs setting, rebuild the cache fully, and give heavy folders time to regenerate.
SageThumbs works in one user account but not another after the update. What now?
The installation is system-healthy and the problem is per-user: settings, cache or profile state in the affected account. Apply the checklist inside that account, including its own cache rebuild, before any reinstall.
Related guides
Keep exploring with these guides from this site:
- SageThumbs Thumbnails Not Showing? 8 Fixes
- How to Clear and Rebuild the Windows Thumbnail Cache
- How to Install SageThumbs on Windows 11
Practical notes before you move on
Keep a short note of what you changed and what you observed while working through this guide. Explorer thumbnail problems often return in a slightly different form months later, after a Windows update, a new drive or a change in the kind of files you handle, and a dated note turns the second diagnosis into a five-minute repeat of a known fix instead of a fresh investigation. Note the Windows version, the SageThumbs version (2.0.0.23), the folder and file types involved, and which step actually restored the previews. If a step did nothing, note that too: ruling causes out is real progress, and it keeps the next troubleshooting session focused on what remains.