Microsoft Word attempts to save to Sharepoint instead of local drive

After getting a case escalated to Tier II, I'm told this is the "solution":

https://support.microsoft.com/en-in/help/4036334/how-to-disable-autosave-in-office-365-proplus

This is, however, to be quite frank, is garbage.  First, it's ONLY workable on a single domain or computer and not across multiple domains, I have over a thousand Office365 customers so there's NO WAY I can deploy even .reg files to fix this to everyone.  Second, it has to be done for EVERY USER who uses the system so if you have 5 users you have 10 registry keys to change because you have to have it for Word AND Excel.

Next, and this is where it gets fun, I'm told that unless I'm a premiere partner I can't have the case escalated past this point.  The rep was confrontational from the first minute we were on the phone and then tells me this.  As a Microsoft shareholder I will not stand or tolerate this.  I will be moving to file an official shareholder complaint with the FTC and the SEC - Microsoft's investor relations has thus far failed to return my call so that will also be part of the complaint.  This is costing customers time and money and is beyond unacceptable.

That Tier II knew about the issue and claims this is the resolution and yet no one else at Microsoft seems to know about it tells me one hand doesn't know what the other is doing.  That doesn't surprise me one bit.

BSB

Hi EveryOne,

I understand the frustration you experienced. Sorry for the inconvenience about this abnormal behavior. I notice some users even have opened some tickets, but don't get a satisfied answer at last. We will be working with all of you about it till we get a solution finally.

To begin with, we have released a new version of OneDrive, Pleaseupgrade to 17.3.7294.0108 to see if there is any improvement. 

We appreciate all users' effort on providing the reproduce steps. We have tested all of them, but it indeed works on our side that files will be saved to local then SharePoint once we uncheck the option "use Office 2016 to sync Office files that I open". Therefore it may be related to the local environment, Please provide the following information to make us on the same page.

1.Windows version

2.A screenshot of the Office product info and version.  (Please mask your account information in the screenshot)

3.OneDrive version 

4.A screenshot of the symptom "after clicking F12, files will be saved to a SharePoint/OneDrive path not a local path"  (Make sure you have uncheck "use Office 2016 to sync Office files that I open" in OneDrive settings)

Best Regards,

Sky

Hi Sky, 

  ![](https://learn-attachment.microsoft.com/api/attachments/454a7587-7d11-4b37-8464-9f155007aa8b?platform=QnA

"4. A screenshot of the symptom "after clicking F12, files will be saved to a SharePoint/OneDrive path not a local path"  (Make sure you have uncheck "use Office 2016 to sync Office files that I open" in OneDrive settings)"

Thanks for looking in to this and understanding the frustration we are all experiencing.  I am concerned about the wording in your item 4 above and your understanding of the exact problem.  The problem is when you create a new file in Word and save it to a local folder which is currently being synced by OneDrive,  Word starts communicating with SharePoint even though we have the "use Office 2016 to sync Office files" unchecked.   This causes a few problems but for one it slows down the save process especially if you are on a slow internet connection.  If that option is unchecked Word should let OneDrive handle the syncing in the background.  This is what we need fixed.   I would be happy to share screens with you as well as others have offered, just send me a private message.  

Bob

Strange, I've not had that problem. I've been able to rename it without issue.  You could just execute the script every 5 minutes with a taskill.exe command before it to kill any existing instances.

Try changing the script to rename the file rather than deleting it.  I have mine renamed FileCoAuth.exe.old and it does not fire off nor does it reinstall.

BSB

That's what I did initially, and a few hours later (overnight) it had created a "<verNum>_1" folder with FileCoAuth.exe back in action.