How to Fix Excel and OneDrive Files Not Opening After Mac Migration
Question details
Users are unable to open specific SharePoint and OneDrive Excel files using the desktop application after migrating to new MacBooks, encountering file path and access errors.

- Product
- Microsoft Excel, OneDrive
- Device & OS
- macOS
- Scenario
- Opening synced SharePoint or OneDrive Excel files on a new MacBook after a system and profile migration.
- Observed behavior
- Excel displays an error stating it cannot access the file path, claiming it doesn't exist, is in use, or shares a name with an open workbook. The issue persists offline and after reinstalling the application, though copy-pasting the file locally allows it to open.
Ensure your MacBook has a stable internet connection and that macOS, OneDrive, and Microsoft Office are fully updated to the latest versions to rule out basic compatibility issues.
Reset OneDrive and Clear Office Credentials
Resetting the OneDrive application forces it to rebuild its synchronization cache, which often resolves lingering file path metadata issues after a macOS migration.
During a Mac migration, cached credentials and broken synchronization links can carry over. Completely resetting OneDrive clears out old directory data so Excel can properly locate the file paths again.
Click the OneDrive cloud icon in your Mac menu bar, select the gear icon (Settings), and click 'Quit OneDrive'.
Open Finder, go to the 'Applications' folder, right-click on 'OneDrive', and select 'Show Package Contents'. Navigate to 'Contents' > 'Resources' and double-click the 'ResetOneDriveApp.command' or 'ResetOneDriveAppStandalone.command' file.
Open 'Keychain Access' from your Mac's Utilities folder. Search for 'Microsoft Office' and delete any cached credential entries to force a fresh sign-in.
Relaunch the OneDrive app, sign back in with your account, and wait for the SharePoint and OneDrive files to fully synchronize locally before attempting to open them in Excel.

Duplicate the File to a Local Directory
If you need immediate access to a locked Excel file, duplicating it manually bypasses the restricted metadata causing the path error.
Escalate to Microsoft 365 Support
If standard troubleshooting and reinstalls fail, the migration may have caused tenant-level metadata corruption requiring administrative intervention.
Use WPS Office as a Reliable Alternative for Mac
If Microsoft Excel continues to struggle with OneDrive file path errors and synchronization bugs on your Mac, consider switching to WPS Office. It provides a lightweight, highly compatible alternative for opening, editing, and saving your spreadsheets locally or in the cloud without the complicated sync issues caused by system migrations.
- 1. Download WPS Office: Visit the official WPS website and download the macOS version of WPS Office.
- 2. Install the Software: Open the downloaded package and follow the on-screen instructions to install WPS Office on your Mac.
- 3. Open Your Spreadsheets: Launch WPS Spreadsheets and open your .xlsx files directly without worrying about Microsoft's path restriction errors.

Frequently Asked Questions
Why does Excel on Mac say 'The file name or path does not exist' for OneDrive files?
This error usually indicates a broken OneDrive synchronization link, cached metadata issues after a system migration, or an issue where Excel believes a background process is locking the file. It rarely means the file is actually missing.
Does uninstalling and reinstalling Microsoft Office fix file path errors?
Typically, no. As observed during Mac migrations, this specific error stems from background sync processes, cached credentials, and OneDrive directory indexing rather than corrupted Excel application files themselves.
How can I quickly access a blocked OneDrive Excel file?
A proven temporary workaround is to use Finder to copy the affected file to a new, local directory (like your Desktop) and open the copied version. This bypasses the locked metadata tied to the OneDrive folder.
What causes Runtime Error 53 in Excel for Mac?
Runtime Error 53 occurs when a required dynamic link library (DLL) or specific file path cannot be found. On Mac, it is often triggered by incompatible add-ins attempting to load, or broken file links resulting from a recent macOS migration.




