Encryption protects a file while it sits on disk. The moment you open it, a different question takes over: what did Windows, and the app you opened it with, remember about it? The answer is usually “a lot” — 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.
(If you are new to the idea of browsing encrypted files without decrypting them first, our introduction to browsing encrypted files covers the basics. This post goes deeper into what leaks around the edges.)
The threat model in one paragraph
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 — that attacker can just watch your screen. Keep that in mind: the goal here is to stop the PC from keeping a record of private material after you have finished with it.
Leak 1: the thumbnail cache
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:
Get-ChildItem "$env:LOCALAPPDATAMicrosoftWindowsExplorer" -Filter 'thumbcache_*.db' |
Select-Object Name, @{n='MB';e={[math]::Round($_.Length/1MB,1)}}, LastWriteTime
The important property is that these previews outlive the original. Encrypt a holiday photo and delete the original, and a recognisable thumbnail may still sit in thumbcache_256.db or thumbcache_1024.db for months. Forensic tools read these caches routinely.
Clean it: run Disk Cleanup (cleanmgr), tick Thumbnails, and confirm. Windows rebuilds the cache as you browse, so do this after you have encrypted and removed the originals. Prevent it: in Group Policy, User Configuration → Administrative Templates → Windows Components → File Explorer → Turn off caching of thumbnail pictures stops new thumbnails being saved; or simply browse sensitive folders in Details view so no previews are generated.
Leak 2: Recent items and Jump Lists
Every time you open a document through the shell, Windows records it in several places:
| Artifact | Where | What it reveals |
|---|---|---|
| Recent items | %APPDATA%MicrosoftWindowsRecent*.lnk |
Shortcut per file: full path, size, timestamps, even the volume serial number |
| Jump Lists | ...RecentAutomaticDestinations and CustomDestinations |
Per-app history of files opened (the list you see when right-clicking a taskbar icon) |
| RecentDocs | HKCUSoftwareMicrosoftWindowsCurrentVersionExplorerRecentDocs |
Recently opened file names, grouped by extension |
| Open/Save dialog MRU | ...ExplorerComDlg32OpenSavePidlMRU and LastVisitedPidlMRU |
Files picked in common file dialogs and the folders they came from |
| Quick Access | File Explorer home page | Recent files and frequent folders, on screen for anyone who opens Explorer |
Crucially, these entries survive after the file is deleted or encrypted. A shortcut called 2026 salary review.xlsx.lnk tells its own story, whether or not the target still exists. Audit them like this:
# Recent items, newest first, with the real target of each shortcut
$sh = New-Object -ComObject WScript.Shell
Get-ChildItem "$env:APPDATAMicrosoftWindowsRecent" -Filter *.lnk |
Sort-Object LastWriteTime -Descending | Select-Object -First 30 |
ForEach-Object { [pscustomobject]@{ Opened = $_.LastWriteTime; Target = $sh.CreateShortcut($_.FullName).TargetPath } }
# Which file extensions appear in RecentDocs
Get-ChildItem 'HKCU:SoftwareMicrosoftWindowsCurrentVersionExplorerRecentDocs' |
Select-Object PSChildName
Clean it: File Explorer → … → Options → Privacy → Clear wipes File Explorer history and Quick Access recents. Right-click a taskbar icon to unpin or remove individual Jump List entries. Prevent it: Settings → Personalization → Start → turn off Show recently opened items in Start, Jump Lists and File Explorer. That one switch stops most of the shell-level recording.
SafeViewer — No Traces Outside the Vault
SafeViewer applies this checklist to itself. Its own settings — your favorites, recent files and vault folder — are encrypted at rest rather than stored as plain readable paths. Its file pickers (Add Files, Add Folder, Export un-encrypted) stay out of Windows’ recent-documents history, so the plaintext originals you protect do not linger in File Explorer’s Quick Access. And a Remember recent files setting turns its own Recent Files list off and erases what was saved.
Leak 3: app-specific MRU lists
Turning off Windows’ own history does not reach inside applications. Most document apps keep their own “most recently used” list:
- Microsoft Office stores recent files per app under
HKCUSoftwareMicrosoftOffice16.0<App>User MRU…File MRU, and the Office start screen shows them. In Word, Excel or PowerPoint: File → Options → Advanced → Display → set Show this number of Recent Documents to 0, or right-click an entry and choose Remove from list. - PDF readers, image viewers and media players nearly always keep a recent list, and some save a thumbnail or last-viewed page too. Check each app’s settings for a history or privacy option.
- Browsers remember local files opened in them (PDFs especially) in their history.
# List Word's recent-file entries (Office 2016 and later)
Get-ChildItem 'HKCU:SoftwareMicrosoftOffice16.0WordUser MRU' -Recurse -ErrorAction SilentlyContinue |
Where-Object { $_.PSChildName -eq 'File MRU' } |
ForEach-Object { Get-ItemProperty $_.PSPath } | Format-List Item*
Leak 4: temporary copies
This is the leak that actually exposes content rather than names. Many workflows quietly write a full plaintext copy to disk:
- Decrypt-to-open tools 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 — the data remains recoverable until overwritten.
- Opening a file from inside a ZIP extracts it to
%TEMP%first. - Office creates owner files (
~$name.docx), temporary working files, and AutoRecover copies so it can restore unsaved work after a crash. - Email attachments opened directly from a mail client are cached in a temporary folder.
# What has landed in your temp folder in the last 7 days?
Get-ChildItem $env:TEMP -Recurse -File -ErrorAction SilentlyContinue |
Where-Object LastWriteTime -gt (Get-Date).AddDays(-7) |
Sort-Object LastWriteTime -Descending |
Select-Object LastWriteTime, Length, FullName -First 40
Disk Cleanup’s Temporary files option (or Settings → System → Storage → Temporary files) clears most of this. The better fix is a workflow that never creates the copy at all.
SafeViewer — View Without Leaving a Decrypted Copy
SafeViewer opens encrypted images, PDFs, text, Word, Excel, PowerPoint and video in its own built-in viewers. The readable content is decrypted only in memory and never written to disk, and the viewer never launches an external app — so there is no temporary plaintext file for another program to cache, index or remember.
Leak 5: the page file and the hibernation file
Even a viewer that keeps everything in memory is subject to the operating system. When RAM is short, Windows can write memory pages to pagefile.sys; when the PC hibernates (including Fast Startup’s partial hibernation), the contents of memory are saved to hiberfil.sys. Either can hold fragments of whatever was on screen — from any application.
# Is the system drive BitLocker-encrypted? (elevated)
manage-bde -status C:
# Turn off hibernation (removes hiberfil.sys; also disables Fast Startup)
powercfg /hibernate off
# Wipe the page file at every shutdown (slower shutdowns; elevated)
reg add "HKLMSYSTEMCurrentControlSetControlSession ManagerMemory Management" /v ClearPageFileAtShutdown /t REG_DWORD /d 1 /f
Of these, full-disk encryption of the system drive (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 “lost laptop” scenario almost entirely.
Other places worth a look
- Windows Search index can store text extracted from documents. Exclude sensitive folders under Settings → Privacy & security → Searching Windows.
- Clipboard history (Win+V) keeps recent copied text and images; clear it or turn it off under Settings → System → Clipboard.
- Cloud sync folders upload whatever lands in them, including plaintext originals you meant to delete. Check the provider’s recycle bin and version history too.
- Shadow copies and backups may hold the plaintext original from before you encrypted it.
A practical cleanup routine after encrypting sensitive files
- Encrypt the files, verify you can open the encrypted versions, then delete the plaintext originals (and empty the Recycle Bin).
- Clear File Explorer history and Quick Access; turn off recent items in Start if you do not use them.
- Remove entries from Office and other apps’ recent lists.
- Run Disk Cleanup with Thumbnails and Temporary files ticked.
- Make sure BitLocker or Device Encryption is on for the system drive.
- From then on, open the encrypted files only in a viewer that does not write decrypted copies or add them to Windows’ history.
Step 6 is where SafeViewer 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’ recent-documents history. It cannot clean up history that other apps recorded before you started using it — that is what steps 1 to 5 are for — and like any app, its memory is still subject to the page file, which is why step 5 matters.
SafeViewer — View Without Leaving a Decrypted Copy
SafeViewer opens encrypted images, PDFs, text, Word, Excel, PowerPoint and video in its own built-in viewers. The readable content is decrypted only in memory and never written to disk, and the viewer never launches an external app — so there is no temporary plaintext file for another program to cache, index or remember.
Key takeaways
- Encryption protects files at rest; opening them is where traces are created.
- The thumbnail cache keeps recognisable previews long after originals are gone — clear it with Disk Cleanup and browse sensitive folders in Details view.
- Recent items, Jump Lists, RecentDocs and Open/Save dialog MRUs name your files even after deletion; one Start setting stops most of it.
- App MRU lists (Office, PDF readers, players) need cleaning separately.
- Temp copies leak actual content; prefer viewers that never write plaintext to disk.
- Page file and hibernation file can hold memory fragments; full-disk encryption covers them and every other leak above.
- SafeViewer views encrypted files in memory, encrypts its own settings and keeps its file pickers out of Windows’ history.

Leave a Reply