A customer in Haddington rang last October in a proper state. She’d left her laptop on overnight to finish a Windows update — the kind you agree to at nine at night and forget about — and signed in at breakfast to find her Documents folder empty. Twenty years of Open University coursework, family photos, tax returns for a small consultancy she runs from a home office off Court Street. Gone, apparently, in the space of one reboot. She was ten minutes away from ringing the bank to check her cloud subscriptions when she rang us instead. Half an hour later we had every file back. This guide is what we now tell every Haddington caller who lands on the same screen.
If you’re staring at an empty Documents folder right now, close the laptop lid, don’t reboot again, and read on. Nine cases out of ten, the files are still on the drive and the recovery is straightforward — but a few things you might reflexively try next can quietly make it harder. If you’d rather someone else drive, book our data recovery team and we’ll walk it back with you on the bench or at the kitchen table.
What Really Happens When Your Documents Folder Looks Empty
Windows “feature updates” — the twice-yearly big ones, not the monthly security patches — do far more than a normal restart. They lift the entire operating system out, drop in a new one, and try to slot your user profile back on top of it. Two things go wrong more often than Microsoft would like to admit. The User Profile Service can fail to load your real profile in time and quietly sign you into a temporary one instead — a brand-new empty account that looks like yours but points at a different folder on the disk. Or the update leaves your real profile intact but redirects the Documents, Desktop and Pictures shell folders to somewhere different, usually because a OneDrive folder redirection didn’t re-establish itself cleanly.
In neither case are the files deleted. They’re sitting exactly where they always were — usually at C:\Users\<yourname>\Documents — and the empty folder you’re looking at is a different, near-identical folder somewhere else on the drive. That is why the first rule is: don’t create new files, don’t reboot, and don’t “reset” anything yet.
A Haddington Bench Story
The Haddington case above is the one that changed how we run this diagnostic. The customer’s laptop had signed her into a temporary profile without warning — the Windows lock screen was still her wallpaper, Chrome still opened to her tabs from the day before (because those are stored per-machine, not per-profile), and File Explorer even displayed her real user icon. Every visible sign said she was in her own account. Only the empty folders and the little Windows toast tucked away in Action Centre — “We can’t sign in to your account” — gave it away.
What we now do before touching anything: open the Start menu, type whoami /user in a PowerShell window, and read the SID. A temporary profile has a SID that ends in .bak or is a fresh one that doesn’t match the folder name of the real profile on disk. That thirty-second check tells us whether we’re about to walk down the temp-profile path or the folder-redirection path — and doing that check first, rather than second, is the difference between a half-hour recovery and an afternoon of hunting. It’s a small thing, but it’s the kind of small thing you only start doing once a case has taught you why.
Before You Touch Anything: The First Ten Minutes Matter
These are the moves that keep options open:
- Don’t reboot again. The temporary profile can be cleared with the right registry edit while it’s still loaded; a second reboot sometimes locks the state in more firmly.
- Don’t create or save anything new in the empty folders. If the files are hidden by a shell-folder redirection, writing into the placeholder can complicate merging later.
- Don’t “reset” the folder location from the Documents Properties — Windows will happily overwrite one folder with the empty other one.
- Don’t empty the Recycle Bin, run Disk Cleanup, or accept any “clean up disk space” prompt. Windows.old is the thing you most want to preserve, and Disk Cleanup will offer to delete it in a single click.
- Do open File Explorer, tick View → Hidden items, and check every drive. The files may already be visible — you just needed to be looking in the right folder.
The Four Places Your Files Are Almost Certainly Still Sitting
On the bench we run through these in order, because each is a bigger commitment than the last.
1. The real user profile folder. Open C:\Users\ and look at the subfolders. If you see two with almost the same name — say Alex and Alex.TEMP or Alex.PC-NAME — the top one is your real account and the bottom one is the temporary profile you’re currently signed into. Copy Documents, Desktop, Pictures and any other folder you care about from the real one to a USB stick before you do anything else. Belt-and-braces: do this before attempting to fix the profile itself.
2. C:\Windows.old. Every feature update creates a full snapshot of the pre-update Windows install here and keeps it for ten days. Inside you’ll find Windows.old\Users\<yourname>\Documents, Desktop, Pictures, Downloads — the whole profile. If Windows Update ran less than ten days ago, this is usually where the recovery actually happens.
3. Previous Versions and File History. Right-click a folder that has files in it that you know are older than the update, choose Properties, and open the Previous Versions tab. If File History was ever turned on (or if System Protection is running), Windows will list restore points from before the update. Even if File History was off, Volume Shadow Copies from before the update sometimes survive.
4. OneDrive online. If any of the missing folders were syncing to OneDrive, sign in at office.com from a different device and use the Restore your OneDrive feature to roll the whole drive back to a point in time before the update. This works even when the local sync client has been reset by the update.
Recovering Files From Windows.old
The Windows.old route is the workhorse. Open File Explorer, navigate to C:\Windows.old\Users, and you’ll see a folder for each account that existed before the update. Inside your account you’ll find every shell folder as it was on the morning of the update. Select what you want — usually Documents, Desktop, Pictures, Downloads, Videos, and any custom folders under C:\Users\<you>\ — and copy them to a safe holding place first (an external drive, or a fresh folder on the desktop of your current profile).
Two gotchas we watch for on the bench. First, Windows sometimes refuses access to Windows.old files with a permissions prompt — click Continue and it takes ownership; if it still refuses, right-click Windows.old, Properties, Security tab, and add your current user with Full Control before copying. Second, Windows.old auto-deletes at ten days. If the update happened a week ago and you’re only reading this now, drop everything and pull the folders out today. We’ve had customers ring on day eleven and it’s a different, much harder recovery from that point on. If the folder has already been cleared, our post on files missing after CHKDSK covers the raw-recovery scan approach we’d use next.
If You’re Signed Into a Temporary Profile
The registry fix for a stuck temp profile lives at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList. Under it are subkeys named after each account’s SID. A broken profile shows up as two keys with the same SID — one with .bak on the end and one without. Deleting the non-.bak key and renaming the .bak one back to itself, then rebooting, usually restores the real profile at next sign-in. In practice we don’t send customers to registry edits over the phone — a wrong key on this hive can make Windows refuse to boot — but that’s the fix. If you’re not comfortable with the registry, this is where our software troubleshooting service takes over: we drive the profile repair, verify the files copied cleanly, and only then reboot.
If the whole update itself is limping and Windows keeps re-signing you into a temp profile, a targeted repair install — running setup.exe from a mounted Windows ISO with the “Keep personal files and apps” option — will often clear it without touching your data. That’s a step we’d fold into a proper OS installation and repair job rather than something we’d walk anyone through blind.
Previous Versions, File History and OneDrive Rewind
File History is the quiet hero of these cases when it was turned on. In Settings → Update & Security → Backup, if you had it enabled, a whole point-in-time browser opens up: pick any date before the update and pull individual files or the whole folder back with one button. Even without File History, System Protection can leave Volume Shadow Copies that show up on the Previous Versions tab of any folder’s Properties dialog.
OneDrive is worth checking even for people who don’t think of themselves as OneDrive users — a lot of Windows setups quietly sync Desktop, Documents and Pictures by default. Sign in at onedrive.com, click the gear, and choose Restore your OneDrive. You can wind the entire drive back to a specific hour on a specific day and undo the update’s effect on any file that was syncing. If files went missing after an OneDrive sync error rather than a Windows update, our post on OneDrive sync deletions is a closer match.
When Files Really Have Gone (and What Still Works Then)
The unhappy version of this story is a laptop where the update ran the built-in reset, or where Windows.old was deleted by a well-meaning Disk Cleanup before we got to it, or where the drive is a modern NVMe SSD with TRIM aggressively wiping erased blocks in the background. In that world, file-by-file recovery scans (PhotoRec, R-Studio) still find plenty on a spinning hard drive but drop off sharply on an SSD, because the blocks the files lived in have already been zeroed.
The honest bench answer at that point is: we run the deep scan, we tell you truthfully how much came back with useful filenames versus how much came back as anonymous JPGs and DOCXs to sort through, and you decide whether to keep going. It’s not a sales moment — a modern SSD after ten days without a shadow copy is a genuinely hard job and we’d rather set expectations at the door than mid-invoice.
How to Stop It Happening Next October
Feature updates ship in the autumn and spring. Two small habits close most of this off:
- Turn File History on and point it at an external drive. Every hour by default, silently, no effort after setup. It’s the single change that turns “disaster” into “annoyance” on this kind of case.
- Delay feature updates by fourteen or thirty days. Windows Pro can do this from Windows Update settings; Windows Home users can get similar breathing room by pausing updates for a week whenever a big one lands. It gives Microsoft time to pull a bad ring before it reaches your machine.
- Keep OneDrive Documents-and-Desktop backup switched on if you already use OneDrive — it’s a rewindable cloud copy for any file inside those folders, and it survives most local profile catastrophes.
- Store one full copy of anything irreplaceable on a drive that isn’t inside the laptop. An external hard drive kept in a drawer, or a NAS, or a second computer — anything not connected to the same profile Windows might trip over.
When to Bring the PC In
Try the top-of-list checks yourself — the hidden items view, the Windows.old copy, the OneDrive rewind. If the files are there, you’ll be back in business inside an hour. Bring the machine to us when you’re looking at a temporary profile that won’t clear, a Windows.old that’s already been deleted, an SSD past the ten-day window, or anything work-related where you’d rather not gamble on your own registry edits. We handle these at the workshop and via data recovery in Haddington, and for immobile PCs we can run the same recovery in your kitchen with our home and office callout service. Small businesses around Haddington, Tranent and North Berwick sometimes prefer that route so the machine never leaves the desk it lives on — the same logic behind our post on Office breaking after a Windows update in Haymarket. Stay calm, check the four places first, and don’t let Disk Cleanup near Windows.old until you’ve pulled what matters out.
Last updated: 27 September 2026