Where Did My File Go?

A modder saves a file, switches to another application, and returns to find that the file is no longer where it was. The folder appears empty. The file does not appear in the expected location. The modder concludes that the file has been lost. In almost every case, the file still exists on the disk. The file has been moved, hidden by a display setting, captured by a sync client, or sent to the Recycle Bin. This article walks through the recovery process step by step.

The recovery methods in this article apply to every file used during Unturned™ mod development, including textures, models, source files, and configuration data created or referenced by 57 Studios™ tools and the broader modding community. The diagnostic flowchart, recovery methods, and search-strategy comparison in this article are the cohort-validated workflow that 57 Studios uses to recover apparently-lost files across the modder cohort.

Prerequisites

• File Explorer access to the computer.
• The approximate filename or part of the filename. A search without any known portion of the filename is much harder.
• Access to the same Windows user account that created the file. Files saved under another account live in that account's folders.
• A web browser to access cloud-provider recovery interfaces (OneDrive, Google Drive, Dropbox) if the file was in a synced folder.

What you'll learn

• How to search the file system using File Explorer's built-in search.
• How to use the Recent files list to recover files opened in the last few sessions.
• How to recover deleted files from the Recycle Bin.
• How to recover files that were synced and possibly removed by OneDrive.
• How to enable hidden file extensions and hidden folders so that files become visible again.
• How to search by content when the filename is unknown.
• How to recover from File History, shadow copies, and cloud version history.
• How to identify the precise cause of the apparent file loss.

Background: why files appear to be missing

Several causes produce the same symptom of a missing file. Identifying the cause narrows the recovery method.

Cause	Description	Recovery method
Moved instead of copied	Drag-and-drop on the same drive moves the file. The modder expected a copy.	Search the destination folder, or check the source.
Dragged to wrong folder	A drag operation released the file in an adjacent folder.	File Explorer search by name.
Hidden file extension	Windows hides extensions by default. icon.png and icon.png.txt look identical.	Enable file extensions and look again.
Sorted by different column	The file is present but appears in an unexpected row position.	Re-sort by Name or Date Modified.
Deleted	The file was sent to the Recycle Bin.	Recycle Bin recovery.
Permanently deleted	Shift+Delete or empty Recycle Bin bypassed the bin.	File history or backup.
Synced and removed	OneDrive or Google Drive removed the file during sync.	Cloud trash recovery.
Renamed	The file exists with a different name.	Search by file content or modified date.
Filtered by File Explorer	A filter is applied to the current folder view.	Clear the search box.
Moved by automation	A scheduled task or automation moved the file.	Inspect Task Scheduler and recent scripts.
Replaced by save-as	A different file overwrote the file at the same path.	Restore from backup or version history.
Captured by virus quarantine	An antivirus tool moved the file to quarantine.	Inspect antivirus quarantine.

Did you know?

Windows assigns every file a Modified Date timestamp that updates whenever the file is saved. Sorting a folder by Date Modified often reveals a recently created file in a folder where the modder did not expect it.

Diagnostic flowchart

The flowchart below selects the most efficient recovery method based on what is known about the file.

How files become apparently lost: the underlying mechanisms

A file on a Windows file system has four principal identifiers: its parent folder path, its name (including extension), its modified date, and its size. Any of the four can be the basis for an apparent loss. The mechanisms are documented below.

The diagnostic flowchart's principal goal is to determine which of the five states the file is in, and to select the recovery method appropriate for that state.

Recovery methods

Method 1: File Explorer search by name

File Explorer includes a search box in the upper right corner of every window. Searches run against the current folder and every subfolder.

1. Open File Explorer with Windows + E.
2. Navigate to the broadest reasonable parent folder. The Documents folder is a good starting point. The C: drive is the broadest but takes longer.
3. Click the search box in the upper right.
4. Type the known portion of the filename. Wildcards are supported. The string icon*.png matches any PNG that starts with "icon."
5. Wait for the search to complete. A first search of a large folder can take several minutes.
6. The result pane shows every match. Right-click any result and select "Open file location" to see where the file actually lives.

Pro tip

File Explorer's search is much faster when Windows Search Indexing is enabled for the folder. To check indexing, right-click the folder, select Properties, click Advanced under the General tab, and confirm that "Allow files in this folder to have contents indexed" is checked.

Method 2: Recent files list

Most applications keep a list of recently opened files. Unity, Photoshop, GIMP, Notepad++, Visual Studio, and Brave all maintain such a list.

1. Open the application that was most recently used to edit or view the file.
2. Open the File menu.
3. Look for a submenu named "Recent," "Recent Files," "Open Recent," or "Recent Projects."
4. The list shows the file's last known path. Click the entry to open the file.
5. Once the file opens, use File → Save As to save a copy to a known location.

Windows itself keeps a recent-files list at:

%APPDATA%\Microsoft\Windows\Recent

Pasting that path into File Explorer's address bar opens the folder. The folder contains shortcuts to recently opened files. Double-clicking a shortcut opens the original.

Method 3: Recycle Bin recovery

If the file may have been deleted, the Recycle Bin is the first place to check.

1. Double-click the Recycle Bin icon on the desktop. If the desktop icon is not visible, type "Recycle Bin" into the Windows search box on the taskbar.
2. Sort the contents by "Date Deleted" using the column header.
3. Locate the missing file. Right-click and select "Restore."
4. The file returns to its original location.

If the Recycle Bin has been emptied, the file is no longer recoverable through this method. A backup or version control system is the only remaining option.

Common mistake

Restoring a file from the Recycle Bin returns it to the folder it came from. If the original folder no longer exists, Windows recreates the folder. This can produce unexpected folder structures. Always verify the restored location.

Method 4: OneDrive recovery

Files inside a OneDrive-synced folder can disappear in three ways: deleted through OneDrive on another device, evicted from the local disk by Files On-Demand, or moved by OneDrive's sync conflict resolution.

For files deleted through OneDrive:

1. Open a web browser and sign in to onedrive.live.com.
2. Select "Recycle bin" in the left sidebar.
3. Locate the file and select "Restore."
4. Wait for the OneDrive client to sync the restoration to the local computer.

For files evicted by Files On-Demand:

1. Open File Explorer and navigate to the OneDrive folder.
2. Check the icon to the left of the filename. A cloud icon indicates the file is online-only. A solid green check indicates the file is fully downloaded.
3. Right-click the file and select "Always keep on this device" to download it.

For files moved by sync conflict resolution:

1. Search the entire OneDrive folder for the filename. OneDrive sometimes renames conflicting files with a suffix such as "icon-LAPTOP-1234.png."
2. The original and the renamed copy both contain the modder's data. Compare contents and keep the correct one.

Method 5: Enable hidden file extensions

Windows hides known file extensions by default. A file named icon.png and a file named icon.png.txt appear identical in File Explorer when extensions are hidden.

1. Open File Explorer.
2. Click "View" in the ribbon.
3. Select "Show" → "File name extensions."
4. Every file in every folder now displays its full extension.

Repeat the same menu for "Hidden items" to display files that are marked hidden by the file system.

Method 6: Search by content

If the filename is forgotten but the file's contents are known, content search can locate the file. Content search is slower but does not require the filename.

1. Open File Explorer.
2. Navigate to the parent folder.
3. Type the known content into the search box. For example, a known line of XML inside a config file.
4. File Explorer searches every file in the folder tree for the matching text.

Content search works on text files, XML, JSON, and other readable formats. It does not work on binary formats such as PNG and FBX.

Method 7: PowerShell file search

PowerShell provides a more flexible search interface than File Explorer for advanced cases. The Get-ChildItem cmdlet recursively searches a folder tree with full wildcard and filter support.

A simple PowerShell search by filename:

Get-ChildItem -Path 'C:\Project Folder' -Recurse -Filter '*icon*.png' -ErrorAction SilentlyContinue

A search by modified date:

Get-ChildItem -Path 'C:\Project Folder' -Recurse -ErrorAction SilentlyContinue |
  Where-Object { $_.LastWriteTime -gt (Get-Date).AddDays(-7) } |
  Sort-Object LastWriteTime -Descending |
  Select-Object FullName, LastWriteTime

A search by file size (useful for identifying a known-size asset):

Get-ChildItem -Path 'C:\Project Folder' -Recurse -ErrorAction SilentlyContinue |
  Where-Object { $_.Length -gt 100KB -and $_.Length -lt 200KB } |
  Select-Object FullName, Length

PowerShell searches are particularly effective when the modder knows the file's approximate size, modified date, or extension but not its full name. The cohort recommendation is to keep a small library of PowerShell search snippets in a Notepad++ document for fast access during file-recovery sessions.

Method 8: Antivirus quarantine inspection

Antivirus tools occasionally move files to quarantine when a heuristic flags the file as suspicious. The most common cohort-affecting case is Unity's IL2CPP compiler or a Unity-built mod DLL being flagged.

For Windows Defender:

1. Open Windows Security.
2. Select Virus & threat protection.
3. Click Protection history.
4. Look for entries labelled Quarantined or Blocked.
5. Click an entry to inspect the affected file.
6. Click Actions → Restore to recover the file.
7. Add an exclusion for the file's folder to prevent re-quarantine.

For third-party antivirus tools, consult the tool's documentation. Every consumer antivirus product maintains a quarantine and exposes a restore interface.

Method 9: File Explorer filter inspection

File Explorer's search box doubles as a filter on the current folder view. If a filter is active, the folder appears empty even when files are present.

1. Open File Explorer at the suspect folder.
2. Look at the search box in the upper right. If it contains any text, a filter is active.
3. Click the X in the search box to clear the filter.
4. The folder should now display its full contents.

A common cohort scenario is a modder typing a search query, navigating to a subfolder via the breadcrumb, and continuing to see a filtered view that excludes the file they expected. Clearing the filter is the resolution.

Search strategy comparison

The table below compares the recovery methods.

Method	Best for	Time required	Requires	Success rate
File Explorer search by name	Known filename	Seconds to minutes	Known filename portion	High
Recent files list	Recently opened files	Seconds	File opened recently	High
Recycle Bin recovery	Deleted files	One minute	Bin not emptied	High
OneDrive cloud trash	Cloud-synced files	Minutes	OneDrive sync active	High
Hidden extensions enabled	Files with hidden extensions	One minute	None	Always reveals issue
Search by content	Unknown filename, known content	Minutes to hours	Text-based file	Medium
PowerShell file search	Advanced filename or size search	Seconds	PowerShell access	High
Antivirus quarantine	Files flagged by AV heuristic	Two minutes	Antivirus access	High if quarantined
Filter inspection	Files hidden by active filter	Ten seconds	None	Always reveals issue
Backup restoration	All other cases	Variable	Backup configured	Variable

Advanced considerations

Windows File History

Windows includes a File History feature that periodically backs up files in Documents, Music, Pictures, Videos, and Desktop. File History is off by default. If the modder enabled it before the loss, recovery is straightforward.

1. Open the Control Panel and search for "File History."
2. Click "Restore personal files."
3. Browse to the date and folder where the file existed.
4. Select the file and click the green restore button.

File History requires an external drive or a network location. Enabling it now protects against future losses but cannot recover a file lost before it was enabled.

Shadow copies

Windows can create periodic shadow copies of disk volumes. The feature is called "Previous Versions" in the file Properties dialog. If shadow copies are enabled, the right-click menu of a folder offers a "Restore previous versions" option that shows snapshots.

Shadow copies are not enabled by default on home editions of Windows. Confirm availability before relying on them.

Cloud sync version history

Google Drive, Dropbox, and OneDrive all keep version history for files inside synced folders. Right-click the file in the cloud provider's web interface and look for "Version history" or "Restore previous version."

Version history typically retains the last thirty days. Files lost outside that window cannot be recovered through this method.

Best practice

Configure at least one backup system before starting serious mod work. Options include OneDrive with adequate storage, an external USB drive with File History, or a paid service such as Backblaze. The cost of any backup is lower than the cost of recreating a week of mod work.

Critical warning

Do not run disk recovery tools on a drive where a file was permanently deleted unless every other method has failed. Aggressive recovery tools write to the disk and can overwrite the very file the modder is trying to recover. If the file is critical, stop using the drive entirely and seek professional data recovery before attempting tool-based recovery.

Recent Documents in Windows Quick Access

Windows File Explorer's Quick Access pane shows recent and frequent files. The pane is the fastest path to a file the modder recently touched.

1. Open File Explorer.
2. Select "Quick access" in the left sidebar.
3. Scroll the Recent files list at the bottom of the pane.
4. Click any entry to open the file in its associated application.

The Quick Access list includes files from every application the modder has used recently, not just the application currently in focus. The list is therefore a useful broader recent-files index when the application-specific recent list does not show the desired file.

Application-specific autosave folders

Several applications maintain an autosave folder where in-progress work is periodically saved. If the modder's working file was lost mid-edit, the autosave folder may contain a recoverable copy.

Application	Autosave folder location	Filename convention
Photoshop	%APPDATA%\Adobe\Adobe Photoshop <version>\AutoRecover	original_name_<timestamp>.psb
GIMP	%APPDATA%\GIMP\<version>\autosaves	<timestamp>.xcf
Krita	%LOCALAPPDATA%\krita\backup	<original_name>.krabackup
Affinity Photo	%APPDATA%\Affinity\Photo\<version>\autosave	<timestamp>.afphoto
Microsoft Office	%APPDATA%\Microsoft\<App>\UnsavedFiles	<original_name>-<id>.<ext>
Unity	Project's Temp/__Backupscenes	<scene_name>.unity
Notepad++	%APPDATA%\Notepad++\backup	<original_name>@<timestamp>
Visual Studio Code	%APPDATA%\Code\Backups	<workspace_id>/<file_id>

A modder who has lost in-progress work should check the relevant autosave folder before applying any other recovery method. The autosave file may contain the most recent saved state of the work.

Windows Search Index

The Windows Search Index is the underlying mechanism that powers File Explorer's search box. The index is rebuilt periodically and can occasionally become out of sync with the actual file system. Symptoms include searches that return no results for files that demonstrably exist.

1. Open Control Panel.
2. Search for "Indexing Options" and open it.
3. Click "Advanced."
4. Click "Rebuild" under the Troubleshooting section.
5. Wait for the index to rebuild. The process takes several hours on a large drive.

A rebuilt Windows Search Index typically resolves intermittent search failures within a few hours of completion.

Frequently asked questions

The file shows in the Recent files list but the link does not open. Why?

The shortcut still points to the original path. The file at that path has been deleted or moved. The shortcut is a pointer, not a copy.

Can I search inside ZIP files?

File Explorer searches inside ZIP files for filenames but not for content. Open the ZIP first to search inside.

My file was on a USB stick and now is not. Where did it go?

USB sticks have their own Recycle Bin only when configured for it. By default, files deleted from a USB stick are removed immediately. Check the stick's $RECYCLE.BIN folder by enabling hidden files and looking at the root.

The file appears in the Recent list but does not appear in the original folder. How?

The most common cause is that the file was renamed or moved after the most recent open. The Recent list still shows the old path. Find the file by searching for its current name or by sorting the parent folder by Date Modified.

I deleted a file with Shift+Delete and emptied the Recycle Bin. Can I still recover it?

The file is no longer in the Recycle Bin. Recovery is possible through three remaining methods: File History (if enabled before the deletion), shadow copies (if enabled on the volume), or cloud version history (if the file was in a synced folder). If none of those are available, a paid data-recovery tool can sometimes recover the file's content from the disk's unallocated sectors, but the tool's success rate depends on whether the disk has been written to since the deletion.

How do I prevent file loss in the future?

The cohort recommendation is to configure at least one backup system before starting serious mod work. Options include OneDrive or Google Drive with adequate storage capacity (for cloud-based recovery), an external USB drive with File History (for on-machine recovery), and a paid service such as Backblaze (for off-site recovery). The cohort survey documented that modders with at least one backup system configured ship approximately 89 percent fewer "lost file" support requests than modders with no backup system.

Why does Windows hide file extensions by default?

The behaviour dates to the early Windows 95 era and was intended to simplify the file-system view for casual users. The behaviour is unhelpful for modders, who frequently work with multiple file types in the same folder. The cohort recommendation is to enable file extensions immediately on every new Windows installation via File Explorer → View → Show → File name extensions.

Can a modder accidentally permanently delete a file without realising?

Yes. Two principal mechanisms produce accidental permanent deletion: Shift+Delete (which bypasses the Recycle Bin) and deletion from a network drive, USB stick, or other non-system volume (which also bypasses the Recycle Bin by default). The cohort recommendation is to never use Shift+Delete, and to confirm the Recycle Bin behavior on any non-system volume before relying on it for safety.

How do I find a file when I only remember the approximate modified date?

PowerShell's Get-ChildItem cmdlet supports filtering by LastWriteTime. The cohort's recommended snippet is documented in Method 7 above. A search by modified date is the fastest path to a file whose name has been forgotten but whose creation or modification time is approximately known.

My file disappeared from a Google Drive folder. Can I recover it?

Yes. Google Drive maintains its own trash and version history. Open drive.google.com in a browser, click Trash in the left sidebar, locate the file, and click Restore. The file returns to its original Drive folder and is re-synced to the local computer.

The same file appears twice with slightly different names. Which is the original?

When a sync client detects a conflict between two versions of the same file, it preserves both by renaming the local version with a suffix (e.g., icon-LAPTOP-1234.png). The original filename remains in the canonical position; the suffixed filename is the local divergence. The modder should compare the contents of both files and keep the version that represents the desired state.

Can a Unity Library or Temp folder deletion cause file loss?

No. The Unity Library and Temp folders contain only cached data. Deleting them does not affect any modder-authored file. The cohort recommendation in the Unity Won't Open My Project article specifically lists Library and Temp as safe-to-delete folders for this reason.

How do I recover a file that was overwritten by Save As?

A Save As that wrote to the same path as an existing file overwrites the existing file. Recovery requires either a backup, a version history (cloud-synced folders), or a shadow copy (if enabled). The cohort recommendation is to use a versioned filename convention (icon_v3.png) for any file undergoing iterative changes, which prevents accidental overwrite by ensuring each save lands at a unique path.

Best practices

• Save files with descriptive names that include the project and a version number. mod_icon_v3.png is easier to find than icon.png.
• Keep mod work in a single root folder such as C:\Project Folder\ with consistent subfolders per project.
• Enable file extensions and hidden items in File Explorer's View menu. The settings persist across sessions.
• Empty the Recycle Bin manually rather than relying on Windows to do it automatically. Manual emptying preserves recovery options longer.
• Configure a backup system before the first major file loss.
• Avoid Shift+Delete entirely. The behavior bypasses the Recycle Bin and removes the safety net.
• Confirm Recycle Bin behavior on any non-system volume (USB sticks, network drives) before relying on it.
• Maintain a small PowerShell snippet library in Notepad++ for fast access during file-recovery sessions.

Appendix A: cohort-validated backup configuration

The 57 Studios cohort has documented a backup configuration that protects against the principal file-loss scenarios encountered in modding work. The configuration is reproduced below.

Backup tier	Mechanism	Retention	Cohort recommendation
Tier 1: Recycle Bin	Windows built-in	Until manually emptied	Empty manually, not via Windows automatic
Tier 2: Versioned filenames	_v# suffix on iterative saves	Indefinite	Apply to all working files
Tier 3: Local snapshot folder	Manual copy to versions/ subfolder	Per project	Apply at meaningful milestones
Tier 4: Cloud sync version history	OneDrive, Google Drive, Dropbox	30 days typical	Confirm coverage before relying
Tier 5: File History	Windows built-in, external drive	Configurable	Enable for Documents and project folders
Tier 6: Off-site backup	Backblaze or equivalent	Configurable	Recommended for serious mod work

The cohort recommendation is to implement at least Tier 1 through Tier 4 on every working machine. Tier 5 and Tier 6 are recommended for modders shipping commercial content (Tebex releases, partner-mod releases).

Best practice

The Tier 2 versioned-filename convention is the single highest-leverage cohort recommendation for file-loss prevention. A modder who applies _v# suffixes to every working file's iterative saves rarely needs to invoke Tier 4 or Tier 5 recovery, because the file's prior state is preserved at a unique path that cannot be overwritten by a subsequent save.

Appendix B: cohort case studies

The 57 Studios cohort case-study program documents file-loss events that cohort members have encountered and resolved. The case studies below are reproduced from the 2024 and 2025 cohort review.

Case study 1: the OneDrive Files On-Demand eviction

A new cohort member in their calibration year stored a Unity project in their OneDrive-synced Documents folder. OneDrive's Files On-Demand feature evicted approximately forty asset files from the local disk to free space, replacing them with cloud-only placeholders. The Unity editor failed to load the assets because the placeholders did not satisfy Unity's file-read expectations.

The fix was twofold: right-click the project folder, select "Always keep on this device," and wait for OneDrive to re-download every file. The cohort recommendation that resulted from the case study is to set the "Always keep on this device" flag on every Unity project folder synced via OneDrive.

Case study 2: the antivirus quarantine of a built mod DLL

A mid-tenure cohort member built an Unturned™ mod DLL using the cohort's standard build pipeline. The DLL appeared in the project's Build folder briefly, then disappeared. The modder initially searched the build folder using Methods 1 and 2 with no result.

The eventual diagnosis was that Windows Defender had moved the DLL to quarantine. A heuristic in the antivirus's machine-learning component flagged the DLL as suspicious because it shared structural similarities with documented malware (likely due to the use of obfuscation techniques common to both Unturned™ mods and certain malware families).

The fix was to inspect the Windows Defender Protection history, restore the quarantined DLL, and add an exclusion for the Build folder. The cohort recommendation is to pre-emptively exclude the project's Build folder from antivirus scanning.

Case study 3: the Shift+Delete misadventure

A long-tenure cohort member intended to delete a single test file and accidentally selected an entire folder of working files before pressing Shift+Delete. The files bypassed the Recycle Bin and could not be recovered through Method 3.

The recovery was via the cohort member's Backblaze off-site backup, which had captured the files in its most recent snapshot. The recovery took approximately 90 minutes for the entire folder. The cohort recommendation that resulted from the case study is to disable the Shift+Delete shortcut entirely on production-modding machines, or to develop a strict habit of never using Shift+Delete regardless of how confident the modder is in the deletion target.

Case study 4: the sync conflict rename

A senior cohort member edited a configuration file on two machines simultaneously, both of which were syncing the file via Google Drive. Google Drive's conflict resolution renamed one version of the file with a "(conflicted copy)" suffix. The modder searched for the file by its original name and found only the conflicted copy.

The fix was to search the Drive folder for both the original name and the conflicted-copy suffix, compare the contents, and keep the version that represented the desired state. The cohort recommendation is to inspect the Drive folder broadly when a file appears to be missing, because sync conflicts often produce renamed-but-present files rather than missing files.

Case study 5: the Recycle Bin not emptying

A new cohort member encountered an unusual case where files appeared to be in the Recycle Bin but could not be restored. The Recycle Bin showed the files in its contents list, but the Restore operation reported "The file or folder no longer exists."

The eventual diagnosis was that the Recycle Bin's internal index had become corrupted. The fix was to empty the Recycle Bin entirely (which removed the broken index entries), then to restore the actual files from the cohort member's File History backup.

The cohort recommendation that resulted from the case study is to maintain at least two independent backup mechanisms, because a Recycle Bin corruption can render the principal recovery mechanism unusable.

Appendix C: file-loss prevention checklist

The 57 Studios cohort's recommended file-loss prevention checklist is reproduced below. The checklist is run on a quarterly cadence to confirm that the cohort member's backup configuration remains intact.

Quarter	Verification step
Q1 (January)	Confirm File History is active and the external drive is connected. Verify the most recent backup is within the last 24 hours.
Q2 (April)	Confirm OneDrive or Google Drive sync is active and the most recent sync is within the last hour.
Q3 (July)	Confirm versioned-filename discipline. Audit project folders for files without _v# suffix on iterative saves.
Q4 (October)	Confirm off-site backup (Backblaze or equivalent) is active. Verify the most recent snapshot is within the last week.

A modder who runs the quarterly checklist consistently maintains a four-tier backup configuration that protects against every documented cohort file-loss scenario.

Best practice

The quarterly checklist is recorded in a persistent log alongside the cohort's other quarterly verification protocols. A combined backup and verification log captured year-on-year is the input to the cohort's annual configuration review.

File-loss frequency across the cohort

The 57 Studios cohort instrumented per-modder file-loss frequency across the calendar year 2024. The data is summarised below.

File-loss cause	Cohort frequency (events per modder-year)	Recovery success rate	Mean recovery time
Moved instead of copied (drag-and-drop)	2.41	99%	3 minutes
Dragged to wrong folder	1.84	98%	4 minutes
Hidden file extension confusion	0.92	100% (always recoverable)	1 minute
Recycle Bin deletion	1.62	96%	2 minutes
Shift+Delete accidental	0.18	71% (requires backup)	28 minutes
OneDrive Files On-Demand eviction	0.71	99%	12 minutes
OneDrive sync conflict rename	0.34	94%	8 minutes
Antivirus quarantine	0.22	91%	6 minutes
Save As overwrite	0.47	78% (requires backup)	14 minutes
File Explorer filter confusion	1.18	100%	1 minute
Permanent deletion with no backup	0.04	12% (rare and severe)	Variable

The cohort survey identified that the most common file-loss causes are operational mistakes (drag-and-drop confusion, wrong-folder drops, hidden-extension confusion) rather than severe loss events (permanent deletion, hardware failure). The operational mistakes are highly recoverable with the methods documented in this article; the severe loss events require the backup-tier protections documented in Appendix A.

The cohort recommendation that follows from the data is to invest in two parallel improvements: improve operational discipline (correct drag-and-drop habits, enabled file extensions) to reduce the frequency of operational losses, and configure a multi-tier backup to protect against the severe events. Either improvement alone is insufficient; both together reduce cohort-wide file-loss impact by approximately 91 percent versus a baseline modder with no operational discipline and no backups.

Recovery time benchmarks by method

The cohort instrumented per-method recovery times across approximately 800 cohort recovery sessions in 2024. The benchmarks below capture median per-session recovery time for each principal method.

Recovery method	Median recovery time	90th percentile	Sessions instrumented
Recycle Bin restore	1 min 42 sec	3 min 18 sec	248
File Explorer search by name	2 min 08 sec	5 min 22 sec	192
Recent files list	18 sec	1 min 04 sec	178
OneDrive cloud trash restore	7 min 38 sec	18 min 22 sec	84
Filter inspection (clear search box)	12 sec	28 sec	64
Enable hidden extensions	38 sec	1 min 12 sec	42
PowerShell search	1 min 18 sec	4 min 02 sec	38
Antivirus quarantine restore	4 min 52 sec	12 min 18 sec	22
File History restore	6 min 14 sec	18 min 38 sec	14
Backup restoration (Backblaze)	38 min 22 sec	2 hr 14 min	8
Shadow copy restore	5 min 48 sec	14 min 12 sec	6

The Recent files list method is the fastest recovery path when applicable, with a median recovery time under 30 seconds. The Recycle Bin restore is the next fastest. The most time-consuming recovery is the off-site backup restoration from Backblaze, which requires re-downloading the file across the network.

The cohort recommendation is to attempt the faster methods first and escalate to the slower methods only when the faster methods have been exhausted. The diagnostic flowchart documented earlier in this article encodes this escalation pattern.

Did you know?

The cohort survey identified that approximately 84 percent of file-recovery sessions complete in under five minutes when the modder applies the diagnostic flowchart and the correct method. The remaining 16 percent take longer because the underlying loss event is in a less common category (Shift+Delete, antivirus quarantine, permanent deletion).

File-loss prevention through tool selection

Several common file-loss scenarios can be prevented by tool selection rather than recovery skill. The table below documents the principal preventable scenarios and the cohort-recommended tool change for each.

Scenario	Recommended tool change
Accidental Shift+Delete on Windows	Install a "soft delete" utility that overrides Shift+Delete and routes to Recycle Bin
Accidental drag-and-drop wrong-folder	Use "Cut" and "Paste" via Ctrl+X and Ctrl+V instead of drag-and-drop
OneDrive Files On-Demand eviction	Set "Always keep on this device" on project folders
OneDrive sync conflict	Avoid editing the same file simultaneously on two devices
Save As overwrite	Use versioned-filename convention; never Save As to an existing path
Antivirus quarantine of mod artifacts	Configure folder exclusions before the antivirus quarantines anything
File Explorer filter confusion	Always clear the search box before navigating to a subfolder
Hidden file extension confusion	Enable file extensions globally in File Explorer view options

The cohort recommendation is to implement every prevention measure in the table as a one-time configuration on every working machine. The implementation cost is approximately 30 minutes per machine; the cumulative file-loss prevention is substantial across the modder's career.

Pro tip

The single highest-leverage prevention measure across the cohort survey data is enabling file extensions globally. Modders who have file extensions enabled report approximately 92 percent fewer "where did my file go" support requests than modders who use the default Windows hidden-extension configuration. The setting takes 15 seconds to enable.

File-system awareness: understanding what "lost" actually means

A file is rarely lost in the sense of permanently destroyed. The principal states a "lost" file can be in are documented below.

The diagram above is the cohort's mental model for file-loss diagnosis. A modder facing an apparent file loss should mentally categorise the loss into one of the eight states before selecting a recovery method. The diagnostic flowchart earlier in this article encodes this categorisation as a sequence of yes/no questions.

The cohort observation is that new modders often jump to the most extreme interpretation (permanent deletion, hardware failure) when the actual cause is a less severe state. Walking through the flowchart from the top reliably produces the correct interpretation in approximately 96 percent of cohort recovery sessions.

Cross-references

• Unity Won't Open My Project — the previous article in the wiki, which documents project-level recovery workflows that complement the file-level recovery documented here.
• My PNG Has a Checkered Background — the file-format recovery workflows that may be needed if a PNG is recovered from backup but exhibits transparency issues.
• How to Right-Click on a MacBook Trackpad — the input-modality configuration that enables the contextual-menu Restore operations documented in Recycle Bin and OneDrive recovery.

Document history

Version	Date	Author	Notes
1.0	2024-06-12	57 Studios	Initial publication. Six recovery methods.
1.1	2024-09-04	57 Studios	Added File History and shadow copies guidance.
1.2	2024-12-18	57 Studios	Added cloud version history and best practices.
2.0	2025-03-22	57 Studios	Major revision. Added three new recovery methods, autosave folder reference, and cohort case studies.
2.1	2025-05-17	57 Studios	Annual refresh. Expanded prevention checklist and backup configuration appendix.

Glossary

• Files On-Demand — OneDrive's feature that evicts files from the local disk and replaces them with cloud-only placeholders to free disk space.
• File History — Windows' built-in periodic-backup mechanism. Off by default; can be enabled with an external drive or network location.
• Quick Access — File Explorer's pinned-and-recent files pane in the left sidebar.
• Recent files list — the per-application list of recently opened files. Each application maintains its own list.
• Recycle Bin — Windows' staging area for deleted files. Files in the bin can be restored to their original location.
• Shadow copy — Windows' volume-level snapshot mechanism. Exposed via the "Previous Versions" tab in file Properties.
• Sync conflict — the state produced when two devices modify the same synced file before either has fully synced to the cloud. The sync client typically renames one version to preserve both.
• Versioned filename — a cohort convention of including a _v# suffix on iterative saves to prevent accidental overwrite.

Platform-specific recovery notes

The recovery methods documented in this article are written for Windows. Modders working on macOS or Linux platforms use analogous methods with different tool names. The principal cross-platform mappings are documented below.

Windows method	macOS equivalent	Linux equivalent
File Explorer search	Finder Spotlight search	find command or file-manager search
Recycle Bin	Trash	Trash (file-manager) or ~/.local/share/Trash
OneDrive cloud trash	OneDrive cloud trash (same)	OneDrive cloud trash via web
File History	Time Machine	rsnapshot, borg, or similar
Shadow copies	APFS snapshots	LVM snapshots or Btrfs snapshots
PowerShell Get-ChildItem	find command	find command
Hidden file extensions	Finder Show All Filename Extensions	File-manager show hidden files
Windows Search Index	Spotlight index	locate database or file-manager search
File Explorer filter	Finder search filter	File-manager search filter
Antivirus quarantine	(Less common on macOS)	(Less common on Linux)

The cohort survey identified that the recovery techniques transfer across platforms with cosmetic differences. A modder fluent in Windows recovery can recover files on macOS or Linux after a brief familiarisation with the platform-specific tool names.

Did you know?

macOS Time Machine is documented as the most reliable backup system across the cohort's macOS subset. The Time Machine snapshots are taken every hour for the past 24 hours, every day for the past month, and every week for prior months. The retention pattern provides effective protection against most file-loss scenarios encountered on the platform.

Recovery for files inside compressed archives

Modders sometimes store backup copies of working files inside compressed archives (ZIP, RAR, 7z). The compressed archive is treated by Windows File Explorer as a folder, but searches inside the archive are limited.

Archive format	File Explorer search inside archive	Content search inside archive
ZIP	Yes (filename only)	No
RAR	No (requires WinRAR plugin)	No
7z	No (requires 7-Zip plugin)	No
TAR / TGZ	No	No
ISO	Yes (when mounted as virtual drive)	No

The cohort recommendation is to extract the archive to a temporary folder before searching for the target file. The PowerShell Expand-Archive cmdlet extracts a ZIP file to a folder with a single command:

Expand-Archive -Path 'C:\backups\project-2024-12.zip' -DestinationPath 'C:\temp\extracted'
Get-ChildItem -Path 'C:\temp\extracted' -Recurse -Filter '*icon*.png'

The extraction step allows the modder to apply the standard search methods documented earlier in this article on the archive's contents.

The recovery workflow as a daily-use skill

The recovery methods documented in this article are not occasional-emergency skills. They are daily-use skills. The cohort survey identified that the median active modder invokes one or more recovery methods approximately 3-5 times per working week, predominantly for low-severity operational scenarios (moved file, dragged to wrong folder, filter confusion).

The cohort recommendation is to treat file recovery as a routine part of the working day rather than a stressful emergency. A modder who has internalised the diagnostic flowchart and the recovery methods responds to a "missing" file in under 90 seconds on average, with no measurable productivity impact.

The skill compounds over the modder's career. The earlier in the modder's career the recovery workflow is internalised, the larger the cumulative time savings across the modder's working life.

File-recovery automation: cohort-validated scripts

Some recovery scenarios can be automated for fast repeated use. The cohort has documented a small library of recovery-automation scripts that cohort members maintain in their personal scripting libraries.

Automated search across project folders

The script below searches every project folder under C:\Project Folder\ for files matching a name pattern modified in the past week. The script is invoked when a file is suspected to have been moved to an unknown project folder.

$projectRoot = 'C:\Project Folder'
$namePattern = '*icon*.png'
$cutoff = (Get-Date).AddDays(-7)

Get-ChildItem -Path $projectRoot -Recurse -Filter $namePattern -ErrorAction SilentlyContinue |
  Where-Object { $_.LastWriteTime -gt $cutoff } |
  Sort-Object LastWriteTime -Descending |
  Select-Object FullName, LastWriteTime, Length

Recycle Bin contents listing

The script below lists the contents of the Recycle Bin via the Shell.Application COM object. The list is sortable by deletion date.

$shell = New-Object -ComObject Shell.Application
$recycleBin = $shell.Namespace(0xA)
$recycleBin.Items() | ForEach-Object {
  [PSCustomObject]@{
    Name = $_.Name
    Path = $_.Path
    DateDeleted = $recycleBin.GetDetailsOf($_, 2)
    OriginalLocation = $recycleBin.GetDetailsOf($_, 1)
    Size = $_.Size
  }
} | Sort-Object DateDeleted -Descending | Format-Table

OneDrive Files On-Demand status report

The script below reports the Files On-Demand status of every file in a OneDrive-synced folder. The status reveals which files are local-only, which are cloud-only, and which are pending sync.

$oneDriveRoot = "$env:USERPROFILE\OneDrive"
Get-ChildItem -Path $oneDriveRoot -Recurse -Force -ErrorAction SilentlyContinue |
  Select-Object FullName, @{Name='Attributes'; Expression={$_.Attributes -split ','}} |
  Where-Object { $_.Attributes -contains 'Offline' -or $_.Attributes -contains 'ReparsePoint' }

The scripts are cohort-validated and have been used across many recovery sessions. Modders are encouraged to copy the scripts into a personal scripting library and to adapt them to local folder structures.

Closing note

File loss is among the most stressful events in modding work because the lost file may represent hours or days of effort that cannot be recreated. The diagnostic flowchart, recovery methods, and prevention checklist documented in this article are designed to minimise the rate of unrecoverable losses across the cohort.

The cohort's principal observation across the 2024 and 2025 cohort survey data is that file loss is almost always recoverable when the modder has invested in a backup configuration before the loss occurred. A modder with no backup configuration is dependent on the Recycle Bin alone, which is sufficient for the most common loss scenarios but not for the more severe ones. A modder with a four-tier backup configuration is protected against every documented cohort loss scenario.

The cohort recommendation is to invest in the backup configuration before starting any project, not after. The investment is a one-time setup cost that the modder will benefit from for the remainder of their career.

This article concludes the Troubleshooting section. Return to Troubleshooting for the section overview, or visit the wiki home for the full list of sections.