← All posts

Files Missing After a Windows Update or "Reset This PC": Which Case Are You In?

September 16, 2026 · DiskRescue Blog

You rebooted after a Windows update, or you ran "Reset this PC" to clear up some unrelated problem, and now the Desktop is bare. Documents is empty. The folder that held eleven years of photos shows nothing at all, and nothing on screen tells you where any of it went.

A few very different things produce that exact screen, and they call for opposite responses. In one, every file is still on the disk untouched and Windows simply failed to load your profile. In another, your files were moved into a folder that has a countdown running on it. In a third, nothing was lost at all — your folders were redirected into OneDrive and haven't finished coming back down. Separating them takes about ninety seconds, and it decides everything after.

Quick answer: Open Command Prompt and run echo %USERPROFILE%. Three outcomes. If it prints something like C:\Users\TEMP or C:\Users\TEMP.000, you are in a temporary profile — save nothing, sign out, and go to the profile section below. If it prints your name with a suffix, like C:\Users\yourname.DESKTOP-4KJ2P1, Windows built you a second, genuine profile: files you save in it do stay, but your old files never moved and are still sitting in the original C:\Users\yourname folder. If it prints the plain C:\Users\yourname, look for C:\Windows.old — your files are likely inside, and Microsoft documents that Windows deletes that folder automatically ten days after an upgrade. If it is already gone, stop writing to the C: drive and run a read-only scan — the DiskRescue trial does this without touching the disk — before anything else claims that free space.

Ninety seconds of diagnosis

Check which profile you are actually in. Press Windows+R, type cmd, press Enter, then type echo %USERPROFILE%. Read the answer against the three cases above: C:\Users\TEMP and its numbered variants mean a temporary profile, a suffixed name means a real new profile created alongside your old one, and the plain path means Windows loaded the profile it was supposed to. In the first two cases your files never moved. Open File Explorer, go to C:\Users, and you will see your original folder still sitting there under its normal name — you can browse straight into it from an administrator account.

Check whether Windows.old exists. Open File Explorer and go to C:\. If a folder called Windows.old sits there, the update or the reset put the previous installation inside it, and that includes the old user profiles. Opening it throws a permission prompt; click Continue and it opens with your administrator rights.

Check whether OneDrive took over your folders. If you signed back in with a Microsoft account after a reset, Desktop, Documents, and Pictures may now be redirected into C:\Users\yourname\OneDrive. A folder looks empty here for one of two ordinary reasons: the sync has not finished pulling your files back down yet, or the folder you are looking at is the old local one while your files now live in the redirected copy. Open C:\Users\yourname\OneDrive\Desktop directly and see whether the names are there. With Files On-Demand switched on they appear as normal entries with a cloud icon in the status column, which means the file exists and downloads when you open it. If the names are missing there too, sign in at onedrive.com and open the recycle bin — on a personal Microsoft account deleted items stay recoverable there for 30 days, and 93 days on a work or school account. Restoring from that page pushes the files back down to the PC on its own.

One case belongs elsewhere: if the drive is clicking, beeping, or spinning up and dropping out, that's mechanical failure. No software fixes it, and repeated scanning makes it worse — take it to a recovery lab.

A temporary profile means nothing was lost

Windows loads a temporary profile when it cannot read your real one — a broken registry entry, a permissions problem on the profile folder, sometimes an antivirus process holding files open at sign-in. You are signed in to the right account the whole time; only the profile failed to load. The desktop looks factory-fresh, the browser has no bookmarks, and Windows may have shown you "We can't sign in to your account" or "You've been signed in with a temporary profile."

The single most important thing here: anything you create or save while in a temporary profile is discarded when you sign out. Don't work in it. Don't save that document "just to be safe." Your actual profile is still sitting at C:\Users\yourname the whole time, readable from an administrator account or from the temporary session itself.

Sign out and sign back in first. It often clears on its own, and it is the cheapest thing you can try. If the temporary profile comes back, the fix is in the registry:

  1. Run regedit and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList.
  2. Click through the S-1-5-21-… keys and read ProfileImagePath in each. Find the one pointing at your profile folder.
  3. If two near-identical keys are there and one ends in .bak, rename the one without .bak by adding .old to the end, then rename the .bak key to remove that suffix. If there is no .bak twin — your SID has a single key, which is common right after a reset — do not invent one. A lone key ending in .bak just loses the suffix; a lone key with no suffix is not renamed at all — check instead that its ProfileImagePath reads C:\Users\yourname, and correct it if it points at a TEMP folder.
  4. Open the key whose name is now the plain S-1-5-21-… SID with no suffix on it — not the .old key you set aside a moment ago — and set State to 0, and RefCount to 0 if it exists. Editing the .old key changes nothing, which is the usual reason people report that the registry fix "didn't work."
  5. Reboot.

Export the ProfileList key first (right-click → Export). Registry edits deserve an undo.

Getting files out of Windows.old before the clock runs out

Windows creates C:\Windows.old during a feature update and during a "Reset this PC" that keeps your files. It holds the previous installation, and inside it, at C:\Windows.old\Users\yourname\, sit your old Desktop, Documents, Pictures, and Downloads.

Microsoft documents the deletion timer for upgrades: ten days after you upgrade to a new build, Windows removes the folder on its own. A Windows.old created by a reset is treated as the same reclaimable space, so plan on the same window rather than counting on more. Storage Sense and Disk Cleanup will also remove it on request, and plenty of people run a cleanup tool while troubleshooting the very problem that hid their files. So copy first, tidy later. Move what you need to an external drive or a second internal disk — not back into the same folders on C:, which complicates any scan you may still need.

Two gaps worth knowing about if you reset with "Keep my files":

  • Only what sits inside your own profile folder survives. Files parked loose in C:\Users itself, outside any profile folder, are not kept, and neither is C:\Users\Public — the shared folder households use for exactly the kind of files nobody wants to lose is the one that isn't protected.
  • Application data lands in Windows.old rather than being restored. Mail archives, save games, chat histories, and license files live under AppData and have to be pulled out by hand.

When Windows.old is genuinely gone

If the ten days passed, or a cleanup pass removed it, or you chose "Remove everything" rather than "Keep my files," the folder no longer exists and the question changes. Now it is about what remains on the disk and whether anything has overwritten it.

Stop installing software on the C: drive. Every download, every update, every temp file is a candidate to land on the blocks holding your data. If the machine is your only one, work from a second drive, or shut it down and attach the disk to another PC.

Two recovery approaches apply, and on a system drive only one of them is open to you.

Undelete on NTFS reads the file table and rebuilds entries whose records haven't been reused yet. When it works, files come back with their original names and folder structure — which matters enormously when you're hunting one document among forty thousand. This is the approach that runs on a live C: drive: DiskRescue's "Restore deleted files" mode works volume by volume and lists C: alongside every other NTFS volume on the machine.

Carving ignores the file table and scans raw sectors for the signatures that begin a JPEG, an MP4, a PDF, a DOCX. It finds data that undelete has given up on, but it recovers contents only — no original filenames, no folders. It also works on whole disks rather than volumes, and DiskRescue will not point it at the disk Windows is running from: the system disk appears in the list grayed out and marked "System disk — locked." To carve your C: drive you have to shut the machine down, pull the disk, and attach it to another PC as a secondary drive. For a photo library that detour is usually worth it. For a folder of similarly named spreadsheets it's a long afternoon.

An honest limit: if the C: drive is an SSD, and on most machines built in the last decade it is, Windows sends a TRIM command when files are deleted. The drive then treats those blocks as free and typically returns zeros when they're read back. Deleted-file recovery on an SSD system drive is a race against that, and it is often already lost by the time anyone notices. Whether files come back depends on whether they've been overwritten, and nobody — no tool, no lab — can tell you that in advance. If you chose "Remove everything" and the option to clean the drive, the reset deliberately wrote over the whole disk, and no software route leads back from that.

What the free trial actually tells you

Scanning is the diagnosis: before spending anything, find out whether your files still exist.

DiskRescue ships as a single executable, so you can run it from a USB stick instead of installing anything onto the drive you are trying to rescue. Right-click and run it as administrator — reading a volume directly needs those rights, and without them the scan stops at "can't open the drive." With C: as the target, the mode you want is "Restore deleted files." Pick the C: volume and let it read the file table; it opens the volume read-only and never writes to it, so an unsuccessful scan costs nothing but time.

What comes back is a table, and that table is the answer you came for. Every deleted file it found is listed with its original name, its size, the folder it used to live in, and a "Recoverable" column that reads OK, encrypted, sparse, fragmented, or empty for each entry. Before you spend a cent you can scroll that list for the filenames you lost and read, file by file, whether the data behind them is still intact. Then select what you want and save up to 20 files at no charge — no file-size cap, no account, no sharing requirement. Send them to a different drive than the one you scanned; writing recovered files back onto the volume you are recovering from can overwrite the very records still waiting to be read, and the app warns you if you pick the same drive.

If the disk is struggling — stalling, throwing read errors — imaging is the safer route. "Recover safely" copies the whole disk to an .img file once and then recovers from the image, so the failing drive gets read a single time rather than hammered repeatedly. Like carving, it works at the disk level, so it is unavailable while that disk is the one Windows booted from; it becomes an option once the drive is out of the machine and connected to another PC. Budget free space equal to the disk's full capacity, put the image somewhere other than the disk you're rescuing, and expect hours on a large drive — the scan resumes where it stopped, so leaving one overnight is fine.

Judge the whole job on those twenty files. If the Recoverable column reads OK for the names you care about, and the twenty you save open normally in the applications that made them, the rest of the list is in the same condition and a full recovery behaves the same way. If those twenty come back truncated or refuse to open, more of the same list will not come back any better — which is precisely what the trial is there to tell you before you decide anything.

How DiskRescue Compares

On a lifetime license, DiskRescue costs about 1/5 what the big-name recovery suites below charge — paid once and used for life, with no auto-renewal.

DiskRescue EaseUS Data Recovery Wizard Pro Disk Drill PRO
Price $29.99 lifetime — launch price $149.95 lifetime, or $99.95/year $149 lifetime, or $89/year
Billing One-time, lifetime — no auto-renewal Monthly / yearly, or lifetime Yearly, or lifetime
What you get free Preview, then restore 20 free (any size, no share, no sign-up) Preview, then recover 500 MB (2 GB after a social-media share) Preview, then recover 100 MB
Damaged-disk recovery
Deleted-file recovery
Secure erase — (not listed)

Prices, features, and free-tier limits checked on each official site (Windows editions) on July 14, 2026 — they may change with sales or updates. The price comparison uses DiskRescue's launch price ($29.99). EaseUS free recovery is 500 MB by default, expanding to 2 GB after a social-media share (kb.easeus.com); Disk Drill's official free limit is 100 MB (cleverfiles.com).

Further reading