Microsoft Word attempts to save to Sharepoint instead of local drive

Anonymous
2018-01-05T00:48:55+00:00

Hi,

When I open a document in Microsoft Word (Office 2016, 365 Pro, Windows 10) and attempt to save it using the F12 save-as function, Word attempts to save the document in Sharepoint, even though I open it on my local drive. I could previously fix this issue by unchecking the "Use Office 2016 to sync Office files that I open" box in OneDrive options. However, this behaviour still happens sometimes. Upon further investigation with a Microsoft support agent (case number 1XXX2), I believe this behaviour now only happens when I just created a document and it is still uploading online.

In other words: if I open a Word document on my local drive but that it is still showing the upload icon (meaning it's uploading to the cloud), then Word will open a Sharepoint version instead. As long as the document remains open, Word will by default propose to save in Sharepoint rather than on the local drive. Is this a glitch or intentional feature?

Thanks,

Microsoft 365 and Office | OneDrive | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2018-03-01T02:17:32+00:00

Hi All,

We'd like to make a summary about the case, so every community member who comes across this thread will easily find the information:

=================

Issue description:

If we uncheck the option : Use Office 2016 to sync Office files that I open in OneDrive sync client and make some changes to a document stored in OneDrive, the changes will attempt to save to SharePoint first. The expected behavior is that changes will be saved to local PC first when we close the document.

Current status:

The issue is fixed in OneDrive version 18.025.0204.0007. You can install it from this article: New OneDrive sync client release notes

=================

Regards,

Sky

Was this answer helpful?

1 person found this answer helpful.
0 comments

84 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2018-02-07T16:15:39+00:00

    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.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-02-07T16:12:09+00:00

    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.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-02-07T16:11:55+00:00

    That's correct, if you manually open the file locally it saves locally, it's only when you create a new document, but people are not going to open files manually, they're going to go to the MRU list and open it from there.  General users aren't going to do it any other way.

    This is bad enough that I have clients saying they're going to Google Apps and dumping Microsoft all together.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-02-07T16:10:28+00:00

    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

    Was this answer helpful?

    0 comments