Forum Widgets
Latest Discussions
VERY SLOW "Processing changes"
Hello, In a completely random manner and without any identifiable common denominator, I frequently have users who synchronize with OneDrive at a snail’s pace. The library in question contains 60,000 items and is sometimes extremely slow to synchronize (it can take 3 days :///). We have well‑managed computers, powerful configurations, and good internet access. We also comply with all Microsoft prerequisites on this matter. (please look vidéo). Best regards, A. W11 - 24H2 up to date Version de OneDrive : Build 26.007.0112.0002 (64 bits) https://uploadnow.io/fr/files/3BKnQ9N
# 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.
URGENT: OneDrive Restore Completed but Files Missing – No Engineer Assigned Since Dec 27
Hello, I am posting here as a last resort after more than 6 weeks of unresolved support. On December 26, 2025, I accidentally deleted a large number of files and emptied the Recycle Bin. On December 27, 2025, I immediately initiated a full OneDrive restore to a snapshot from December 19, 2025. The restore job shows: • Restore status: Completed • Thousands of restore events processed • However, hundreds of events failed (Save Conflict, Item Not Found in Recycle Bin) My storage usage dropped significantly (from 10+ GB to ~2.7 GB), and thousands of photos never reappeared. Restore logs show: • Multiple “Save Conflict” errors • Multiple “Item Not Found in Recycle Bin” errors • Backend SharePoint references (SPException) I opened an official support case on December 27, 2025. The current status still says: “A support agent is being assigned to your request.” No OneDrive engineer has contacted me in over a month. I am a paying Microsoft 365 subscriber. My questions: 1. Is there a way to confirm whether backend snapshot data still exists? 2. Does “Restore Completed” guarantee that the backend restore fully executed? 3. Can Save Conflict errors prevent large portions of data from being re-materialized? 4. Is escalation to the OneDrive backend team still possible beyond front-line support? This is not a basic user error case. The restore logs clearly show backend-level operations. If anyone from the OneDrive engineering team is monitoring this forum, I am urgently requesting technical escalation. Thank you.3 file limit error in Personal Vault in spite of 1TB family subscription
I am having issues with my Personal Vault on One Drive. Its giving me error that I have hit 3 files limit in the Personal Vault on One Drive. In order to use more than 3 files , I have to upgrade to a 1TB plan. I am already a part of the Family Subscription and have 1 TB of space. I have just used 46GB of 1TB. Support is barely able to help me. Best they could do was tell me to logout and login. I have uninstalled and reinstalled my One Drive, and after setting up the Personal Vault, I am seeing the same issue. On 1TB , I can save as many files on Vault but I cant do for some reason now. It was working fine for last so many years but just today it broke after I edited and saved a file. Family subscription with 1TB allows unlimited files on Personal vault but basic plan allows only 3 files. Please help if anyone has a solution.
Has OneDrive changed the way it handles conflict issues? Because it's losing my data this way...
In the past, when OD had trouble syncing a file due to conflicts (it wasn't sure what was really the most recent), it would leave the original file intact and create a "-machinename" version of the file as well. So, if I have a file voice1.mp3, and, on one of the computers (say, "pc1"), it couldn't figure out whether the version I was saving was the latest, I'd end up with this: voice1.mp3 voice1-pc1.mp3 Which is fine. I'd have to resolve the conflict. Recently, what it seems to do is create the "-machinename" file and DELETE the original file. So, I end up with this: voice1-pc1.mp3 The first time it happened, I thought it must be something I had done, so I pulled back the original file from my backups (this is one of MANY reasons when MS should NOT bill OD as a "backup". "Backups" are copies that are INDEPENDENT of the original file. But, I digress...). But now I'm seeing it all over the place. It seems that whenever it finds a conflict, it creates the -machinename file and NUKES the original file. Anybody else seen this or know how to stop it? Thanks!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
