Whether you are troubleshooting a stubborn Explorer problem, moving to a different thumbnail tool, or retiring a machine, a complete uninstall beats a half-finished one. SageThumbs is a shell extension (version 2.0.0.23, GPL v2 or later), so its footprint is registrations inside Explorer, a settings page in Control Panel, handler components on disk, and cache data including sagethumbs.db3. The standard uninstaller removes the program and its registrations; this guide adds the restart that lets Explorer release the extension, the leftover checks that make the removal genuinely complete, and the verification that Explorer has returned to its stock behaviour. Nothing here touches your image files, which remain exactly where they were throughout.
Step 1: Uninstall the standard way
- Close Explorer windows showing image folders, so no thumbnail work is in progress.
- Open Settings, Apps, Installed apps (or Control Panel, Programs and Features on older setups) and find SageThumbs.
- Choose Uninstall and complete the wizard.
- Do not delete program folders by hand as a substitute; manual deletion leaves registrations pointing at missing files, which is how stranger errors are born.
Use the uninstaller even if you plan to reinstall SageThumbs ten minutes later as a repair. A proper uninstall followed by a restart and a fresh install is the clean cycle that fixes registration damage, whereas layering installers over a confused state preserves the confusion. Note any custom settings first, such as a raised maximum file size or changed format selection, if a reinstall is part of your plan, so the new installation can be configured identically without guesswork.
Step 2: Restart so Explorer releases the extension
Restart the computer. Shell extensions live inside the Explorer process, and components can remain loaded until Explorer fully restarts; a PC restart is the simplest guarantee. After the restart, open a folder of PSD files in an icon view: generic icons in place of previews are the expected sign that the SageThumbs handler is gone, while formats Windows previews natively, such as JPG and PNG, continue to show thumbnails as before. Open the right-click menu (Show more options on Windows 11) and confirm the SageThumbs preview entry no longer appears. Check Control Panel as well: the SageThumbs settings page should be absent. Those three absences together confirm the working parts of the extension have been removed, not merely hidden.
Step 3: Remove leftover cache and data (optional but complete)
A standard uninstall can leave cache residue behind. Search your user profile for sagethumbs.db3, the SageThumbs thumbnail cache database, and delete a leftover copy once you have confirmed the program itself is uninstalled. Consider the Windows thumbnail cache too: entries generated while SageThumbs was active can linger in Explorer’s cache until it turns over naturally, so a Disk Cleanup pass with Thumbnails ticked gives you a genuinely clean slate and forces Explorer to regenerate previews solely with its remaining handlers. If another thumbnail tool will take over SageThumbs’ formats, install it after this cleanup and let it build its own cache against clean folders, rather than inheriting a mixed cache from two regimes. None of these leftovers are harmful if left alone; completeness here is about clarity, especially when you are diagnosing whether a new tool or a clean Windows behaves differently from the old setup.
Step 4: Verify stock behaviour and reinstalling later
Spend a few normal days with folders before declaring the diagnosis complete if you uninstalled to solve freezes or crashes. Explorer stability across your real workloads, not a five-minute test, is the evidence that matters, and our crash guide explains how to use that evidence. If you later return to SageThumbs, install fresh from the verified installer sagethumbs_2.0.0.23_setup.exe (2,242,393 bytes, SHA-256 705d743e28b487e34a4a7245a0dbc303a10e45ba0fd9e4da4101c8cdf506839a), restart Explorer, and reapply any settings you noted. Fresh installations after a complete uninstall and cleanup succeed in cases where quick reinstalls failed, precisely because no damaged registration or stale cache survives to greet the new copy. Keep this guide’s order if you ever remove it again: uninstaller first, restart second, residue last, judgement after real use.
Frequently asked questions
Will uninstalling SageThumbs delete my images or PSD files?
No. SageThumbs is a preview extension; uninstalling removes its components, registrations and caches. Your image files, folders and projects are not modified in any way.
Explorer still shows PSD thumbnails after uninstalling. Why?
Either Explorer has not restarted since the uninstall, the Windows thumbnail cache is still serving previews generated earlier, or another installed tool also handles PSD. Restart the PC, run Disk Cleanup for thumbnails, and recheck before assuming the uninstall failed.
Can I just disable SageThumbs instead of uninstalling?
For short tests, narrowing the formats SageThumbs handles in its settings can approximate a disable for those formats. For a conclusive test or a permanent change, a complete uninstall with a restart is the cleaner instrument, because it removes the extension from Explorer’s process entirely.
Related guides
Keep exploring with these guides from this site:
- SageThumbs Freezing or Crashing Explorer? How to Fix It
- What Is sagethumbs.db3?
- How to Install SageThumbs on Windows 10
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.