Forum Discussion
Mac: OneDrive Couldn't Start: Please restart your computer and try again
When OneDrive updated on 9/11, with build 26158.0816, I started to get this error:
OneDrive Couldn't Start: Please restart your computer and try again. Error codes: FilterStatus::-3 (0xfffffffd) [Permanent] [SyncRootManagerTools.cpp:128 `Odfs::Fs::CommonPlaceholders::CommonSyncRootRegisterVnop`]
I have powered off my Mac and rebooted. Restarting OneDrive does nothing. It keeps giving me this error and as a result, I also cannot live edit docs using the thick clients (Word, Excel, etc). Files I have modified with them are stuck on my Mac.
I am looking for tips. Please do not ask me to unlink/de-register all of my Onedrive sync'd shares.
29 Replies
- OldTrout55Occasional Reader
It seems clear that there is no single solution that works for everyone and that OneDrive currently has a range of issues, both in standalone and O365 versions. Could we please have information on when this is likely to be fixed.
- JeremyGuthrieBrass Contributor
I am hoping this reply (3rd time trying to post) makes it...
I blew away everything and I'm seeing this now:[ mylaptop myuser 08:39:52 ]:~/Library/CloudStorage # ls -la
total 40
drwxr-xr-x+ 19 myuser mygroup 608 Sep 24 08:34 .
drwx------@ 108 myuser mygroup 3456 Jun 30 22:27 ..
-rw-r--r--@ 1 myuser mygroup 18436 Sep 23 16:52 .DS_Store
drwx------@ 167 myuser mygroup 5344 Sep 23 16:44 OneDrive-mycompany
lrwxr-xr-x 1 myuser mygroup 96 Sep 23 16:51 OneDrive-SharedLibraries-mycompany -> /Users/myuser/Library/CloudStorage/OneDrive-SharedLibraries-OneDrive-SharedLibraries-mycompany
drwx------@ 41 myuser mygroup 1312 Sep 23 16:45 OneDrive-SharedLibraries-mycompany 2
lrwxr-xr-x 1 myuser mygroup 121 Sep 23 16:52 OneDrive-SharedLibraries-OneDrive-SharedLibraries-mycompany -> /Users/myuser/Library/CloudStorage/OneDrive-SharedLibraries-OneDrive-SharedLibraries-OneDrive-SharedLibraries-mycompany
drwx------@ 45 myuser mygroup 1440 Sep 23 16:51 OneDrive-SharedLibraries-OneDrive-SharedLibraries-mycompany 2
drwx------@ 2 myuser mygroup 64 Sep 23 10:09 OneDrive-SharedLibraries-OneDrive-SharedLibraries-mycompany2
drwx------@ 2 myuser mygroup 64 Sep 23 10:09 OneDrive-SharedLibraries-OneDrive-SharedLibraries-mycompany22
drwx------@ 2 myuser mygroup 64 Sep 23 10:09 OneDrive-SharedLibraries-OneDrive-SharedLibraries-mycompany222
lrwxr-xr-x 1 myuser mygroup 146 Sep 24 08:30 OneDrive-SharedLibraries-OneDrive-SharedLibraries-OneDrive-SharedLibraries-mycompany -> /Users/myuser/Library/CloudStorage/OneDrive-SharedLibraries-OneDrive-SharedLibraries-OneDrive-SharedLibraries-OneDrive-SharedLibraries-mycompany
drwx------@ 47 myuser mygroup 1504 Sep 24 08:29 OneDrive-SharedLibraries-OneDrive-SharedLibraries-OneDrive-SharedLibraries-mycompany 2
drwx------@ 2 myuser mygroup 64 Sep 23 10:09 OneDrive-SharedLibraries-OneDrive-SharedLibraries-OneDrive-SharedLibraries-mycompany22
lrwxr-xr-x 1 myuser mygroup 171 Sep 24 08:33 OneDrive-SharedLibraries-OneDrive-SharedLibraries-OneDrive-SharedLibraries-OneDrive-SharedLibraries-mycompany -> /Users/myuser/Library/CloudStorage/OneDrive-SharedLibraries-OneDrive-SharedLibraries-OneDrive-SharedLibraries-OneDrive-SharedLibraries-OneDrive-SharedLibraries-mycompany
drwx------@ 50 myuser mygroup 1600 Sep 24 08:30 OneDrive-SharedLibraries-OneDrive-SharedLibraries-OneDrive-SharedLibraries-OneDrive-SharedLibraries-mycompany 2
drwx------@ 2 myuser mygroup 64 Sep 23 10:09 OneDrive-SharedLibraries-OneDrive-SharedLibraries-OneDrive-SharedLibraries-OneDrive-SharedLibraries-mycompany22
drwx------@ 52 myuser mygroup 1664 Sep 24 08:34 OneDrive-SharedLibraries-OneDrive-SharedLibraries-OneDrive-SharedLibraries-OneDrive-SharedLibraries-OneDrive-SharedLibraries-mycompany 2
drwx------@ 53 myuser mygroup 1696 Sep 24 08:34 OneDrive-SharedLibraries-OneDrive-SharedLibraries-OneDrive-SharedLibraries-OneDrive-SharedLibraries-OneDrive-SharedLibraries-OneDrive-SharedLibraries-mycompany
- arambau-wgfsCopper Contributor
I can confirm that this morning, when version 26.158.0816.0003 deployed (I believe through automated updates that I didn't initiate), the issue was resolved.
- alexrambauCopper Contributor
I think we can all agree that a "reset" is not a resolution, it's a "we absolutely can't wait to fix" stop gap measure. Too often this response is used to correct what is poor quality control and an unguarded software failure. This is now a widely known issues, there is no excuse for the release to still be rolling out (https://learn.microsoft.com/en-us/sharepoint/sync-release-notes?tabs=macos) when it is clearly defective. We can't be the only people to have encountered this.
What is interesting is that in my personal life, version 26.158.0816.0003 is deployed and is not exhibiting this behavior.
- DPufferTRVCopper Contributor
I can confirm this worked for me and several other employees, though a slightly more involved fix.
Identify what folders they have syncing before runningStep 1 — Fully quit OneDrive
Click the OneDrive cloud icon in the menu bar → Quit OneDrive
Open Activity Monitor (Spotlight → "Activity Monitor") and confirm nothing named OneDrive is still running; force-quit any strays
Step 2 — Get to the reset scripts
Open Finder → Applications
Right-click OneDrive → Show Package Contents
Navigate to Contents → Resources
Step 3 — Remove cached credentials
Double-click RemoveOneDriveCreds.command
A Terminal window opens and runs briefly, then closes
Step 4 — Run the full reset
Still in that same Resources folder, double-click ResetOneDriveAppStandalone.command
Terminal opens again and clears out local app state, sync database, and the local OneDrive folder registration
Step 5 — Relaunch and set up fresh
Open OneDrive from Applications (or Spotlight)
Sign in with the Altus account
Since you're mid-tenant-spinout, double check it's authenticating against the right tenant before you pick folders to sync
Choose sync scope (Files On-Demand vs. sync everything) and let it re-download
- JeremyGuthrieBrass Contributor
yeah, hard reset is not what I need here. :(
- ConoriscoCopper Contributor
Can confirm no issues last 24 hours so long as no sharepoint folders are synced (which defeats the purpose) as soon as more than one folder which is not in the primary onedrive is synced things start to break down, folder is linked in user folder but actual path gets ammended to add a 2 or simply duplicated string of final folder name to laughable length e.g. company name - company name - company name - company anme or company name 2 2 2 2 - I've seen it all. It's not worth the hassle - th ecompany provide it for free but given the European sovereignty movement I see a vibe shift. I use Dropbox for legacy company work and we don't have this issue. It might be only 1-2 days work but muliplied by 5-6 people the cost solution is obvious
- ConoriscoCopper Contributor
Incredible - will be removing team from sharepoint - everyone is messed up cannot access critical shared files - I have tried the below and it worked and 1 day later it unlinked again - just not worth the hassle, we now have arcane file names "2" duplicatoin of stings in names, folders we cannot delete to resync loss of multuple sharepoints - I have instructed my entire team to stop working.
For me this file did not exist:
"/Applications/OneDrive.app/Contents/StandaloneUpdater.app/Contents/MacOS/OneDriveStandaloneUpdater"
Reset ondrive script worked but a new error appears today.
The route folders of my sharepoint works however consitutent folders are syncing from a seperate location on the filesystem not user/library/Cloudstorage/whatever onedrive but rather inside
…/Group Containers/XXXXXX.OneDriveStandaloneSuite/XXXXX.noindex/…/XXXXXX - Documents/my folder - Dolly1Copper Contributor
for me a hard reset seemed to have done the trick, but it does remove all your synced drives unfortunately..
Run from Terminal:
/Applications/OneDrive.app/Contents/Resources/ResetOneDriveAppStandalone.command - TimDoeCopper Contributor
A clean-reinstall approach helped me to get it working even at the same build 26158.0816.002 (downloaded from official Microsoft site). Files were retained, no need to worry when it offers to Erase and Connect again. Still recommend backing up.
Instruction:1. Quit OneDrive (Activity Monitor force-quit if needed).
2. Drag OneDrive.app to Trash (don't empty yet).
3. Remove leftover support files via Terminal:- rm -rf ~/Library/Application\ Support/com.microsoft.OneDrive
rm -rf ~/Library/Application\ Support/OneDrive
rm -rf ~/Library/Caches/com.microsoft.OneDrive rm -rf ~/Library/Application\ Scripts com.microsoft.OneDrive*
rm -rf ~/Library/Application\ Scripts/*.OneDriveStandaloneSuite
4. Restart the Mac (clears any lingering File Provider registration state tied to the old install).
5. Download a fresh installer directly from microsoft.com/onedrive (not the App Store) and install.
6. Sign back in and reconnect folder. - rm -rf ~/Library/Application\ Support/com.microsoft.OneDrive
- DanielTDSCopper Contributor
What worked for me was switching to the insider preview and then invoking the updater via the terminal:
"/Applications/OneDrive.app/Contents/StandaloneUpdater.app/Contents/MacOS/OneDriveStandaloneUpdater"
Fixed it in 5 mins- DGKLBOCopper Contributor
How do you switch to the insider preview if you can't launch the app?
- DanielTDSCopper Contributor
I have four instances of the OneDrive running: one for each org and one personal.
Only one of the instances / orgs had this issue with the exact error message. So, I switched to the insider preview on a working account, then ran that command in terminal. After a while I saw OneDrive quit then reopen and the problematic account took a while to work but it restored itself fully.
- timmiami2Tin Contributor
same issue here, very annoying.