# 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.
Onedrive LOSES my data!
So I spent time adding lots of entries to a stock management spreadsheet, saved it to my onedrive and made sure it said 'saved' at the top of the excel window. Opened the sheet again today to see that all of my changes are gone and I have effectively lost my stock because the absolute imbeciles at Microsoft can't code. How do I get my work back? When are microsoft going to sort their sloperating system out?OneDrive(22.33.213.2) Keeps Crashing on Windows 11
I'm running OneDrive (version 22.33.213.2) on Windows 11, since it was updated to this version, it keeps crashing: Faulting application name: OneDrive.exe, version: 22.33.213.2, time stamp: 0xd37e7e7f Faulting module name: KERNELBASE.dll, version: 10.0.22000.527, time stamp: 0x71a5cb5d Exception code: 0x80000003 Fault offset: 0x00000000000f57a2 Faulting process id: 0x3ec0 Faulting application start time: 0x01d82d935be6f17e Faulting application path: C:\Program Files\Microsoft OneDrive\OneDrive.exe Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll Report Id: ba88d605-2aca-4ae6-a213-ebad354cb4e5 Faulting package full name: Faulting package-relative application ID: I also tried: 1. install in %localappdata% folder (the default path) 2. restart computer 3. reinstall onedrive 4. run a sfc /scannow
MacOS 14.8.1 OneDrive - Timestamped Sync Root directory?
Hello community, Attempted a plethora of web searches to find someone else who may have seen this. I utilize Shared Libraries with my MacOS OneDrive, and it seems within my ./Library/CloudStorage/ there are two versions of the Sync Root: OneDrive-SharedLibraries-*Company*/Directories & OneDrive-SharedLibraries-*Company* (Timestamp)/Directories This Timestamped Sync Root has over 140GBytes of 'reported' storage space consumption. Some of the folders already exist in OneDrive-ShareLibraries-*Company*/Directories, but others do not. Was curious if anyone else has seen this before and knows if the related storage can be 'freed'?How to resolve 'path is too long' error - endless abending loop!
I'm searching for the proper procedure to resolve a OneDrive for Business issue where a file path is too long. Still, when revised in SharePoint, the OneDrive account doesn't sync the changes and continues to alert the path being too long despite being renamed in SharePoint.
