{"id":382,"date":"2026-11-17T12:20:00","date_gmt":"2026-11-17T12:20:00","guid":{"rendered":"https:\/\/backendside.com\/blog\/?p=382"},"modified":"2026-11-21T12:17:48","modified_gmt":"2026-11-21T12:17:48","slug":"file-viewer-privacy-leaks-thumbnails-recent-files","status":"publish","type":"post","link":"https:\/\/backendside.com\/blog\/2026\/11\/17\/file-viewer-privacy-leaks-thumbnails-recent-files\/","title":{"rendered":"Your Viewer Leaks Too: Thumbnails, Recent Files and Temp Copies"},"content":{"rendered":"<p class=\"lead\">Encryption protects a file while it sits on disk. The moment you open it, a different question takes over: <em>what did Windows, and the app you opened it with, remember about it?<\/em> The answer is usually &ldquo;a lot&rdquo; &mdash; a thumbnail of the image, the file name in three or four history lists, a temporary decrypted copy, perhaps fragments in the page file. None of this is malicious; it is Windows trying to be helpful. But it means an encrypted folder can be surprisingly easy to describe, and sometimes to reconstruct, without ever breaking the encryption. This is a tour of the main leak vectors, how to audit each one with built-in tools, and how to clean them up.<\/p>\n<p>(If you are new to the idea of browsing encrypted files without decrypting them first, our <a href=\"https:\/\/backendside.com\/blog\/2026\/06\/29\/browse-encrypted-files-without-decrypting-them-first\/\">introduction to browsing encrypted files<\/a> covers the basics. This post goes deeper into what leaks around the edges.)<\/p>\n<h2>The threat model in one paragraph<\/h2>\n<p>These leaks matter to anyone who might lose physical control of the PC: a stolen laptop, a shared family computer, a repair shop, a colleague with an admin account, a device that gets imaged. They do not matter much against an attacker who already has live control of your running session &mdash; that attacker can just watch your screen. Keep that in mind: the goal here is to stop the PC from <strong>keeping a record<\/strong> of private material after you have finished with it.<\/p>\n<h2>Leak 1: the thumbnail cache<\/h2>\n<p>When File Explorer shows a folder in a thumbnail view, it renders a small preview of every image, video and many documents, and stores them in a set of database files so it does not have to render them again:<\/p>\n<pre style=\"background:#1e1d1b;color:#eceae6;padding:1rem 1.15rem;border-radius:8px;overflow-x:auto;font-size:.85rem;line-height:1.5;\"><code>Get-ChildItem \"$env:LOCALAPPDATAMicrosoftWindowsExplorer\" -Filter 'thumbcache_*.db' |\n  Select-Object Name, @{n='MB';e={[math]::Round($_.Length\/1MB,1)}}, LastWriteTime<\/code><\/pre>\n<p>The important property is that <strong>these previews outlive the original<\/strong>. Encrypt a holiday photo and delete the original, and a recognisable thumbnail may still sit in <code>thumbcache_256.db<\/code> or <code>thumbcache_1024.db<\/code> for months. Forensic tools read these caches routinely.<\/p>\n<p><strong>Clean it:<\/strong> run Disk Cleanup (<code>cleanmgr<\/code>), tick <em>Thumbnails<\/em>, and confirm. Windows rebuilds the cache as you browse, so do this <em>after<\/em> you have encrypted and removed the originals. <strong>Prevent it:<\/strong> in Group Policy, <em>User Configuration &rarr; Administrative Templates &rarr; Windows Components &rarr; File Explorer &rarr; Turn off caching of thumbnail pictures<\/em> stops new thumbnails being saved; or simply browse sensitive folders in <em>Details<\/em> view so no previews are generated.<\/p>\n<h2>Leak 2: Recent items and Jump Lists<\/h2>\n<p>Every time you open a document through the shell, Windows records it in several places:<\/p>\n<table>\n<thead>\n<tr>\n<th>Artifact<\/th>\n<th>Where<\/th>\n<th>What it reveals<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Recent items<\/td>\n<td><code>%APPDATA%MicrosoftWindowsRecent*.lnk<\/code><\/td>\n<td>Shortcut per file: full path, size, timestamps, even the volume serial number<\/td>\n<\/tr>\n<tr>\n<td>Jump Lists<\/td>\n<td><code>...RecentAutomaticDestinations<\/code> and <code>CustomDestinations<\/code><\/td>\n<td>Per-app history of files opened (the list you see when right-clicking a taskbar icon)<\/td>\n<\/tr>\n<tr>\n<td>RecentDocs<\/td>\n<td><code>HKCUSoftwareMicrosoftWindowsCurrentVersionExplorerRecentDocs<\/code><\/td>\n<td>Recently opened file names, grouped by extension<\/td>\n<\/tr>\n<tr>\n<td>Open\/Save dialog MRU<\/td>\n<td><code>...ExplorerComDlg32OpenSavePidlMRU<\/code> and <code>LastVisitedPidlMRU<\/code><\/td>\n<td>Files picked in common file dialogs and the folders they came from<\/td>\n<\/tr>\n<tr>\n<td>Quick Access<\/td>\n<td>File Explorer home page<\/td>\n<td>Recent files and frequent folders, on screen for anyone who opens Explorer<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Crucially, <strong>these entries survive after the file is deleted or encrypted<\/strong>. A shortcut called <code>2026 salary review.xlsx.lnk<\/code> tells its own story, whether or not the target still exists. Audit them like this:<\/p>\n<pre style=\"background:#1e1d1b;color:#eceae6;padding:1rem 1.15rem;border-radius:8px;overflow-x:auto;font-size:.85rem;line-height:1.5;\"><code># Recent items, newest first, with the real target of each shortcut\n$sh = New-Object -ComObject WScript.Shell\nGet-ChildItem \"$env:APPDATAMicrosoftWindowsRecent\" -Filter *.lnk |\n  Sort-Object LastWriteTime -Descending | Select-Object -First 30 |\n  ForEach-Object { [pscustomobject]@{ Opened = $_.LastWriteTime; Target = $sh.CreateShortcut($_.FullName).TargetPath } }\n\n# Which file extensions appear in RecentDocs\nGet-ChildItem 'HKCU:SoftwareMicrosoftWindowsCurrentVersionExplorerRecentDocs' |\n  Select-Object PSChildName<\/code><\/pre>\n<p><strong>Clean it:<\/strong> File Explorer &rarr; <em>&hellip;<\/em> &rarr; <em>Options<\/em> &rarr; <em>Privacy<\/em> &rarr; <em>Clear<\/em> wipes File Explorer history and Quick Access recents. Right-click a taskbar icon to unpin or remove individual Jump List entries. <strong>Prevent it:<\/strong> <em>Settings &rarr; Personalization &rarr; Start<\/em> &rarr; turn off <em>Show recently opened items in Start, Jump Lists and File Explorer<\/em>. That one switch stops most of the shell-level recording.<\/p>\n<div style=\"border:1px solid #c5d3f8;background:linear-gradient(135deg,#eef2fd 0%,#ffffff 72%);border-radius:14px;padding:1.5rem 1.65rem;margin:2rem 0;\">\n<div style=\"font-size:.7rem;font-weight:700;letter-spacing:.08em;text-transform:uppercase;color:#2d5be3;margin-bottom:.55rem;\">&#128295; BackendSide Tool<\/div>\n<h4 style=\"margin:0 0 .45rem;font-size:1.15rem;color:#1a1916;font-weight:700;\">SafeViewer &mdash; No Traces Outside the Vault<\/h4>\n<p style=\"margin:0 0 1.05rem;color:#3d3c38;font-size:.92rem;line-height:1.65;\">SafeViewer applies this checklist to itself. Its own settings &mdash; your favorites, recent files and vault folder &mdash; are <strong>encrypted at rest<\/strong> rather than stored as plain readable paths. Its file pickers (Add Files, Add Folder, Export un-encrypted) <strong>stay out of Windows&rsquo; recent-documents history<\/strong>, so the plaintext originals you protect do not linger in File Explorer&rsquo;s Quick Access. And a <strong>Remember recent files<\/strong> setting turns its own Recent Files list off and erases what was saved.<\/p>\n<p>  <a href=\"https:\/\/backendside.com\/safeviewer.php\" style=\"display:inline-flex;align-items:center;gap:.4rem;background:#2d5be3;color:#ffffff;font-weight:600;font-size:.85rem;padding:.6rem 1.2rem;border-radius:6px;text-decoration:none;\">Explore SafeViewer &rarr;<\/a>\n<\/div>\n<h2>Leak 3: app-specific MRU lists<\/h2>\n<p>Turning off Windows&rsquo; own history does not reach inside applications. Most document apps keep their own &ldquo;most recently used&rdquo; list:<\/p>\n<ul>\n<li><strong>Microsoft Office<\/strong> stores recent files per app under <code>HKCUSoftwareMicrosoftOffice16.0&lt;App&gt;User MRU&hellip;File MRU<\/code>, and the Office start screen shows them. In Word, Excel or PowerPoint: <em>File &rarr; Options &rarr; Advanced &rarr; Display<\/em> &rarr; set <em>Show this number of Recent Documents<\/em> to 0, or right-click an entry and choose <em>Remove from list<\/em>.<\/li>\n<li><strong>PDF readers, image viewers and media players<\/strong> nearly always keep a recent list, and some save a thumbnail or last-viewed page too. Check each app&rsquo;s settings for a history or privacy option.<\/li>\n<li><strong>Browsers<\/strong> remember local files opened in them (PDFs especially) in their history.<\/li>\n<\/ul>\n<pre style=\"background:#1e1d1b;color:#eceae6;padding:1rem 1.15rem;border-radius:8px;overflow-x:auto;font-size:.85rem;line-height:1.5;\"><code># List Word's recent-file entries (Office 2016 and later)\nGet-ChildItem 'HKCU:SoftwareMicrosoftOffice16.0WordUser MRU' -Recurse -ErrorAction SilentlyContinue |\n  Where-Object { $_.PSChildName -eq 'File MRU' } |\n  ForEach-Object { Get-ItemProperty $_.PSPath } | Format-List Item*<\/code><\/pre>\n<h2>Leak 4: temporary copies<\/h2>\n<p>This is the leak that actually exposes <em>content<\/em> rather than names. Many workflows quietly write a full plaintext copy to disk:<\/p>\n<ul>\n<li><strong>Decrypt-to-open tools<\/strong> that decrypt a file to a temp folder, launch the default app on it, and try to delete it afterwards. If the app crashes, the PC sleeps, or the tool is killed, the plaintext stays. Even when deleted, it is an ordinary deletion &mdash; the data remains recoverable until overwritten.<\/li>\n<li><strong>Opening a file from inside a ZIP<\/strong> extracts it to <code>%TEMP%<\/code> first.<\/li>\n<li><strong>Office<\/strong> creates owner files (<code>~$name.docx<\/code>), temporary working files, and AutoRecover copies so it can restore unsaved work after a crash.<\/li>\n<li><strong>Email attachments<\/strong> opened directly from a mail client are cached in a temporary folder.<\/li>\n<\/ul>\n<pre style=\"background:#1e1d1b;color:#eceae6;padding:1rem 1.15rem;border-radius:8px;overflow-x:auto;font-size:.85rem;line-height:1.5;\"><code># What has landed in your temp folder in the last 7 days?\nGet-ChildItem $env:TEMP -Recurse -File -ErrorAction SilentlyContinue |\n  Where-Object LastWriteTime -gt (Get-Date).AddDays(-7) |\n  Sort-Object LastWriteTime -Descending |\n  Select-Object LastWriteTime, Length, FullName -First 40<\/code><\/pre>\n<p>Disk Cleanup&rsquo;s <em>Temporary files<\/em> option (or <em>Settings &rarr; System &rarr; Storage &rarr; Temporary files<\/em>) clears most of this. The better fix is a workflow that never creates the copy at all.<\/p>\n<div style=\"border:1px solid #c5d3f8;background:linear-gradient(135deg,#eef2fd 0%,#ffffff 72%);border-radius:14px;padding:1.5rem 1.65rem;margin:2rem 0;\">\n<div style=\"font-size:.7rem;font-weight:700;letter-spacing:.08em;text-transform:uppercase;color:#2d5be3;margin-bottom:.55rem;\">&#128295; BackendSide Tool<\/div>\n<h4 style=\"margin:0 0 .45rem;font-size:1.15rem;color:#1a1916;font-weight:700;\">SafeViewer &mdash; View Without Leaving a Decrypted Copy<\/h4>\n<p style=\"margin:0 0 1.05rem;color:#3d3c38;font-size:.92rem;line-height:1.65;\"><strong>SafeViewer<\/strong> opens encrypted images, PDFs, text, Word, Excel, PowerPoint and video in its own built-in viewers. The readable content is <strong>decrypted only in memory and never written to disk<\/strong>, and the viewer never launches an external app &mdash; so there is no temporary plaintext file for another program to cache, index or remember.<\/p>\n<p>  <a href=\"https:\/\/backendside.com\/safeviewer.php\" style=\"display:inline-flex;align-items:center;gap:.4rem;background:#2d5be3;color:#ffffff;font-weight:600;font-size:.85rem;padding:.6rem 1.2rem;border-radius:6px;text-decoration:none;\">Explore SafeViewer &rarr;<\/a>\n<\/div>\n<h2>Leak 5: the page file and the hibernation file<\/h2>\n<p>Even a viewer that keeps everything in memory is subject to the operating system. When RAM is short, Windows can write memory pages to <code>pagefile.sys<\/code>; when the PC hibernates (including Fast Startup&rsquo;s partial hibernation), the contents of memory are saved to <code>hiberfil.sys<\/code>. Either can hold fragments of whatever was on screen &mdash; from any application.<\/p>\n<pre style=\"background:#1e1d1b;color:#eceae6;padding:1rem 1.15rem;border-radius:8px;overflow-x:auto;font-size:.85rem;line-height:1.5;\"><code># Is the system drive BitLocker-encrypted? (elevated)\nmanage-bde -status C:\n\n# Turn off hibernation (removes hiberfil.sys; also disables Fast Startup)\npowercfg \/hibernate off\n\n# Wipe the page file at every shutdown (slower shutdowns; elevated)\nreg add \"HKLMSYSTEMCurrentControlSetControlSession ManagerMemory Management\" \/v ClearPageFileAtShutdown \/t REG_DWORD \/d 1 \/f<\/code><\/pre>\n<p>Of these, <strong>full-disk encryption of the system drive<\/strong> (BitLocker, or Device Encryption on Windows Home where supported) is the one that matters most. It encrypts the page file, the hibernation file, the thumbnail cache, the temp folder and every history list in one go, so a stolen or imaged drive reveals none of them. It does not help while you are logged in, but it closes the &ldquo;lost laptop&rdquo; scenario almost entirely.<\/p>\n<h2>Other places worth a look<\/h2>\n<ul>\n<li><strong>Windows Search index<\/strong> can store text extracted from documents. Exclude sensitive folders under <em>Settings &rarr; Privacy &amp; security &rarr; Searching Windows<\/em>.<\/li>\n<li><strong>Clipboard history<\/strong> (<kbd>Win<\/kbd>+<kbd>V<\/kbd>) keeps recent copied text and images; clear it or turn it off under <em>Settings &rarr; System &rarr; Clipboard<\/em>.<\/li>\n<li><strong>Cloud sync folders<\/strong> upload whatever lands in them, including plaintext originals you meant to delete. Check the provider&rsquo;s recycle bin and version history too.<\/li>\n<li><strong>Shadow copies<\/strong> and backups may hold the plaintext original from before you encrypted it.<\/li>\n<\/ul>\n<h2>A practical cleanup routine after encrypting sensitive files<\/h2>\n<ol>\n<li>Encrypt the files, verify you can open the encrypted versions, then delete the plaintext originals (and empty the Recycle Bin).<\/li>\n<li>Clear File Explorer history and Quick Access; turn off recent items in Start if you do not use them.<\/li>\n<li>Remove entries from Office and other apps&rsquo; recent lists.<\/li>\n<li>Run Disk Cleanup with <em>Thumbnails<\/em> and <em>Temporary files<\/em> ticked.<\/li>\n<li>Make sure BitLocker or Device Encryption is on for the system drive.<\/li>\n<li>From then on, open the encrypted files only in a viewer that does not write decrypted copies or add them to Windows&rsquo; history.<\/li>\n<\/ol>\n<p>Step 6 is where <strong>SafeViewer<\/strong> fits. Its viewers decrypt in memory and never write the readable content to disk, its own recent-files and favorites lists are encrypted at rest (or turned off entirely), and its file pickers keep the originals you protect out of Windows&rsquo; recent-documents history. It cannot clean up history that other apps recorded before you started using it &mdash; that is what steps 1 to 5 are for &mdash; and like any app, its memory is still subject to the page file, which is why step 5 matters.<\/p>\n<div style=\"border:1px solid #c5d3f8;background:linear-gradient(135deg,#eef2fd 0%,#ffffff 72%);border-radius:14px;padding:1.5rem 1.65rem;margin:2rem 0;\">\n<div style=\"font-size:.7rem;font-weight:700;letter-spacing:.08em;text-transform:uppercase;color:#2d5be3;margin-bottom:.55rem;\">&#128295; BackendSide Tool<\/div>\n<h4 style=\"margin:0 0 .45rem;font-size:1.15rem;color:#1a1916;font-weight:700;\">SafeViewer &mdash; View Without Leaving a Decrypted Copy<\/h4>\n<p style=\"margin:0 0 1.05rem;color:#3d3c38;font-size:.92rem;line-height:1.65;\"><strong>SafeViewer<\/strong> opens encrypted images, PDFs, text, Word, Excel, PowerPoint and video in its own built-in viewers. The readable content is <strong>decrypted only in memory and never written to disk<\/strong>, and the viewer never launches an external app &mdash; so there is no temporary plaintext file for another program to cache, index or remember.<\/p>\n<p>  <a href=\"https:\/\/backendside.com\/safeviewer.php\" style=\"display:inline-flex;align-items:center;gap:.4rem;background:#2d5be3;color:#ffffff;font-weight:600;font-size:.85rem;padding:.6rem 1.2rem;border-radius:6px;text-decoration:none;\">Explore SafeViewer &rarr;<\/a>\n<\/div>\n<h2>Key takeaways<\/h2>\n<ul>\n<li>Encryption protects files at rest; <strong>opening them<\/strong> is where traces are created.<\/li>\n<li>The <strong>thumbnail cache<\/strong> keeps recognisable previews long after originals are gone &mdash; clear it with Disk Cleanup and browse sensitive folders in Details view.<\/li>\n<li><strong>Recent items, Jump Lists, RecentDocs and Open\/Save dialog MRUs<\/strong> name your files even after deletion; one Start setting stops most of it.<\/li>\n<li><strong>App MRU lists<\/strong> (Office, PDF readers, players) need cleaning separately.<\/li>\n<li><strong>Temp copies<\/strong> leak actual content; prefer viewers that never write plaintext to disk.<\/li>\n<li><strong>Page file and hibernation file<\/strong> can hold memory fragments; full-disk encryption covers them and every other leak above.<\/li>\n<li><strong>SafeViewer<\/strong> views encrypted files in memory, encrypts its own settings and keeps its file pickers out of Windows&rsquo; history.<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Encrypting a file protects it on disk, but opening it can scatter copies all over Windows: thumbnail caches, Jump Lists, Recent items, app MRU lists, temp files, the page file and the hibernation file. A tour of each leak vector, how to audit it with built-in tools, and how to clean it up.<\/p>\n","protected":false},"author":1,"featured_media":452,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5,8],"tags":[45,74,67,76,75],"class_list":["post-382","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-security","category-tutorials","tag-encryption","tag-privacy","tag-safeviewer","tag-thumbcache","tag-windows-forensics"],"_links":{"self":[{"href":"https:\/\/backendside.com\/blog\/wp-json\/wp\/v2\/posts\/382","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/backendside.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/backendside.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/backendside.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/backendside.com\/blog\/wp-json\/wp\/v2\/comments?post=382"}],"version-history":[{"count":1,"href":"https:\/\/backendside.com\/blog\/wp-json\/wp\/v2\/posts\/382\/revisions"}],"predecessor-version":[{"id":453,"href":"https:\/\/backendside.com\/blog\/wp-json\/wp\/v2\/posts\/382\/revisions\/453"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/backendside.com\/blog\/wp-json\/wp\/v2\/media\/452"}],"wp:attachment":[{"href":"https:\/\/backendside.com\/blog\/wp-json\/wp\/v2\/media?parent=382"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/backendside.com\/blog\/wp-json\/wp\/v2\/categories?post=382"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/backendside.com\/blog\/wp-json\/wp\/v2\/tags?post=382"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}