Version History Issues

“Version History Issues” refer to failures in tracking, listing, or restoring previous iterations of synced files. Users may open the “Version History” menu to find it blank, discover that intermediate revisions have been deleted, or encounter errors when restoring old states. This can be caused by application save behaviors that replace rather than modify files, or tenant-level administration policies.

This guide explains how file versioning works, provides steps to audit application behaviors, and outlines administrative overrides on both Windows and macOS.

1. Understand Version History Mechanics

Version tracking depends on specific write signals:

• Atomic vs. In-Place Writes: Some applications (e.g. certain code editors or CAD tools) do not write edits directly to the existing file. Instead, they write to a temporary file, delete the original, and rename the temp file to the original. To the cloud client, this looks like a deletion followed by a new file creation, erasing historical version history.
• Offline Intermediate Saves: If you save a file 20 times while offline, the cloud client only sees the final version when you reconnect. Intermediate versions are not uploaded or recorded.
• SharePoint Minor/Major Versioning limits: Policies in Microsoft SharePoint/OneDrive Business that limit versions to major numbers (e.g. 1.0, 2.0) or restrict the total number of versions stored.

A. Monitor Local File Write Operations

If you suspect an application is deleting and recreating files, use PowerShell to monitor filesystem change notifications in real time:

1. Search for PowerShell in the Start Menu and open it.
2. Run the filesystem watcher script (replace path with your cloud root):

   # Watch folder events to see if apps perform a Delete/Create sequence
   $Watcher = New-Object System.IO.FileSystemWatcher
   $Watcher.Path = "$env:UserProfile\OneDrive\Documents"
   $Watcher.IncludeSubdirectories = $true
   $Watcher.EnableRaisingEvents = $true
   Register-ObjectEvent $Watcher "Deleted" -Action { Write-Host "Deleted: $($EventArgs.FullPath)" -ForegroundColor Red }
   Register-ObjectEvent $Watcher "Created" -Action { Write-Host "Created: $($EventArgs.FullPath)" -ForegroundColor Green }

If a save command triggers both a “Deleted” and “Created” event on the same file, the editing application is resetting version history. Try saving under a different format, or adjust the app’s advanced settings to disable atomic saves.

A. Disable Safe-Saving in Text Editors

If you are using TextEdit or third-party developers tools, look for settings related to backups:

1. In the application preferences, locate the Saving or Backups tab.
2. Uncheck Use Safe Saving or Atomic Save if available.
3. If using Vim or Neovim, disable backups and write-backup features in your config (init.vim):

   set nobackup
   set nowritebackup

# List local APFS snapshots containing historical data
tmutil listlocalsnapshots /

4. Configure Admin Tenant Version Limits

If you are using SharePoint Online or OneDrive Business and version history is missing for all users, check the library configuration:

5. Summary Quick Reference Checklist