Forum Discussion
# OneDrive AutoSave Stopped Working After Update to Version 26.007.0112 on macOS
**Product:** Microsoft 365 and Office | OneDrive | For home | macOS
## Summary
Since OneDrive automatically updated to version 26.007.0112 (26007.0112.0002) a few days ago, I am experiencing multiple issues with how Office files interact with OneDrive on my Mac. AutoSave no longer works, files that are stored locally now take noticeably longer to open, and attempting to work around the problem through Word/Excel directly results in upload failures and outdated file versions. Prior to this update, everything was working perfectly.
## Environment
- **macOS version:** Tahoe 26.1
- **OneDrive version:** 26.007.0112 (26007.0112.0002)
- **Office version:** Version 16.105.2 (26012530)
- **Account type:** Business
## Symptoms
### 1. AutoSave no longer activates when opening files from Finder
Opening any .docx or .xlsx file from the OneDrive folder in Finder results in AutoSave being off. The title bar shows "Saved on My Mac" instead of the OneDrive location. Attempting to toggle AutoSave on prompts me to "upload" the file — even though it is already in the OneDrive sync folder and marked as "Always Keep on This Device."
### 2. Files that are stored locally now open slowly
Previously, opening an Office file from the OneDrive folder in Finder was instantaneous, as you would expect for a file stored on the local drive. Now, even though the files are marked as "Always Keep on This Device" and should be fully available locally, there is a noticeable delay when opening them. It appears that OneDrive or the Office app is downloading or re-fetching the file from the cloud rather than simply opening the local copy, which defeats the entire purpose of keeping files on the device.
### 3. Opening from within Word/Excel results in "Upload Failed" and serves an older version
As a workaround, I tried opening files from within Word using File > Open and selecting the OneDrive location. However, this now produces an "Upload Failed" error message, and the file that opens is an older version — not the most recent version I had been working on. This is extremely concerning, as it suggests the sync between the local copy and the cloud copy may be broken, and there is a real risk of data loss or overwriting recent work with outdated content.
## Steps to Reproduce
1. Ensure files are in the OneDrive folder and marked as "Always Keep on This Device."
2. Open a .docx or .xlsx file by double-clicking it in Finder. Notice: the file takes several seconds to open (previously instant), AutoSave is off, and the title bar says "Saved on My Mac."
3. Close the file. Open Word or Excel, go to File > Open, and navigate to the OneDrive location. Open the same file. Notice: an "Upload Failed" message appears, and the file that opens is an older version, not the most recent one.
## Expected Behavior
- Files stored locally via "Always Keep on This Device" should open instantly, just as any local file would.
- AutoSave should be enabled automatically when opening files from the synced OneDrive folder.
- Opening a file from within Word/Excel via the OneDrive location should open the current version of the file without upload errors.
All of this worked exactly as expected before the update to version 26.007.
## What I've Tried
- Verified that "Always Keep on This Device" is enabled for the affected folders.
- Confirmed I am signed into the same Microsoft account in both OneDrive and the Office apps.
- Verified files are in modern formats (.docx, .xlsx), not legacy formats.
- Checked that OneDrive sync is not paused.
## Impact
This is a severe workflow disruption. The combination of broken AutoSave, slow file access, and the "Upload Failed" error serving stale file versions means I cannot trust that I am working on the latest copy of my documents. There is a genuine risk of data loss — if the cloud version is out of sync with the local version, saving could overwrite recent work with an older copy. I am currently unable to rely on OneDrive for day-to-day work on my Mac.
## Additional Notes
This appears to be a regression introduced by the recent OneDrive update to version 26.007. I have seen numerous other users reporting similar AutoSave and sync issues across Microsoft Q&A, Apple Community forums, and MacRumors, dating back to the original Files On-Demand changes on macOS. However, my setup was working correctly until this latest update.
Relevant threads with related issues:
- https://learn.microsoft.com/en-us/answers/questions/5419331/onedrive-says-saved-on-mac-autosave-not-working
- https://learn.microsoft.com/en-us/answers/questions/5371608/one-drive-auto-save-no-longer-working-on-mac-os
- https://learn.microsoft.com/en-us/answers/questions/5402091/onedrive-app-on-mac-not-working-for-autosave-and-t
- https://forums.macrumors.com/threads/onedrive-autosave-disabled-when-opening-files-from-onedrive-folder.2442775/
I would appreciate any guidance from the community or the Microsoft team. Is this a known regression in version 26.007? Is a fix in progress? Is there a way to roll back to a previous OneDrive version that was working?
Thank you.
2 Replies
This is a known, critical regression affecting the Version 26.007 (Build 26007.0112) release of OneDrive on macOS. You are not imagining it, and it is not your configuration.
Microsoft has acknowledged issues with this specific build regarding Files On-Demand integration and the AutoSave API for Office apps. The "Upload Failed" error combined with opening old versions is particularly dangerous because it indicates a "sync collision" where OneDrive is failing to lock the file for upload, causing Office to revert to the last known cloud state.
Here is a breakdown of how to mitigate this immediately, how to roll back, and how to work around it until a hotfix is released.
Roll Back to a Previous Version (Recommended)
The only way to restore 100% functionality immediately is to downgrade from 26.007.0112 to the previous production build (25.233.x or similar). Microsoft does not provide an official "downgrade" button, but you can do it manually.
- Quit OneDrive completely (Right-click icon -> Quit).
- Download the previous stable standalone installer (version 25.233.1126 or similar). Note: You may need to find this on third-party repositories like "MacAdmins" or "MacUpdate" if Microsoft hasn't archived it officially, as they usually only host the latest.
- OR Use a package manager like Homebrew:
brew install --cask onedrive
(Note: Homebrew cask often lags slightly behind or allows pinning, but currently, they may have pulled the bad build too. Check brew info onedrive).
Immediate Workarounds (If you cannot downgrade)
If you must stay on version 26.007 for now, you must change your workflow to bypass the broken Finder integration.
1. Disable "Files On-Demand" for Active Folders
The bug is triggered when Office tries to verify the "online-only" status. Force the files to be physical.- Select the folder in Finder.
- Right-click -> Always Keep on This Device.
- Note: This will consume significant disk space, but it bypasses the "fetching" delay.
2. Stop Opening Files via Finder
The "Saved on My Mac" error happens because the OS is handing the file path to Office beforeOneDrive has stamped it as "synced."- The Fix: Open Word/Excel first.
- Go to File > Open > Browse.
- Navigate to your OneDrive folder inside the file picker dialog.
- This forces Office to use the WAC (Web App Companion) protocol directly rather than relying on the Finder/macOS file coordinator.
3. Reset Office Auth and Keychain
Sometimes the token between Office and OneDrive gets corrupted by the update.- Open Keychain Access on Mac.
- Search for OneDrive and Office 365.
- Delete all "internet password" and "generic password" entries related to OneDrive/Microsoft.
- Restart Office. You will be forced to sign in again. This often re-establishes the broken handshake.
4. Disable "Open at Login"
- System Settings > General > Login Items.
- Remove OneDrive.
- Launch it manually after you have launched Word/Excel once. This ensures the Office sync plugins load after the core app.
My answers are voluntary and without guarantee!
Hope this will help you.
Was the answer useful? Mark as best response and like it!
This will help all forum participants.
Hello,
Did you receive any update or feedback about this issue?
We are experiencing the same problems, and it doesn’t seem to be related to a specific OneDrive version. We have multiple Macs running different macOS versions and different OneDrive builds, and honestly, the issue appears everywhere. I don’t understand how this feature can be offered on macOS when it clearly doesn’t work reliably.
Everything works fine as long as we only upload new files. But as soon as we start modifying, updating, or saving documents, things become problematic.
Thanks,M
