Forum Discussion
AutoSave disabled when opening SharePoint-synced files from Finder after macOS Tahoe 26.6 update
Think I found the problem using Claude...
The root folder created by OneDrive must not contains any non-ASCII characters.
Switch OneDrive application to English (System settings > General > Language and region > Applications > + > OneDrive > English) and restart the app. Root folder should now be named "OneDrive - Shared Libraries - xxxxxx". Wait fot sync to complete. Open an Office doc. Autosave should be on now.
- koklucinarAug 27, 2026Brass Contributor
Hi Levitas, thanks for the suggestion but unfortunately it didn't work for me.
I even tried resyncing everything after applying English from the L&R menu, but still no luck.
- qostech_madionSep 02, 2026Copper Contributor
I suggest you put more time on this because I see results on my side, but I need to try a lot more stuff to actually figure it out. (This is an early comment on my journey to a solution)
Here is what I had to do and what I ended up with:
1. Did the language change to English as mentioned above (didn't work)
2. Because my users are French I changed it back but instead of French - Canada, I landed on French - French (from France I guess)
step 2 made me notice a different loading compared to the first language change from step 1, I have no idea if this is an actual noticeable and reproducible prompt with other language selections
3. opened a file again just to try it out and autosave was actually enabled (was able to do it for 2 users so this must be somewhat working)Now I'll skip a lot of figuring stuff out because all of it was really troubling by the end of it but hour 1 hypothesis is :
1. This solution is unreliable and complicated at best and was not required just a month ago or for the last years of working this exact same way.
2. We have multiple SharePoint sites with different names and there may be a second layer to this because sites with regular names are seemingly working (i was actually told just now that even these sites may not work fully either) but sites with special characters in their names aren't.
Meaning that, this fixes the root of your path but later down the line it can still fail depending on your sites display name i guess ??Let's work this out together and maybe we'll see the end of it; I'll be waiting for your inputs.
- bbenoistAug 26, 2026Copper Contributor
Any one else confirmed the fix? For us it might be more difficult as the company name has a non-ASCII character... 😬