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 No 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 No comments

84 additional answers

Sort by: Oldest
  1. Anonymous
    2018-02-09T10:19:57+00:00

    Hi Everyone,

    Thanks for all your information.

    This issue has already been escalated to the related team for further investigation. We will let you know the updates/Solutions ASAP.

    Regards,

    Sky

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-02-13T13:42:12+00:00

    Hi Sky, any news on this? Been waiting for support for this for 2 months now and I am still not being taken seriously. Happy to finally find a thread where people are reporting the same issues.

    Making service unreachable to state that there are no issues known or reported... Like a helpdesk with a secret number.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-02-13T17:16:16+00:00

    Just to confirm, at the time of posting:

    Regardless of Office Sync opt-out settings, all Office 2016 applications are exhibiting one of two opposite behaviours when opening and saving files directly from / to a local instance of a OneDrive folder, depending on whether the file is created inside or outside of that OneDrive folder:

    Steps to reproduce:

    Case 1: Office file is created outside of the local instance of a OneDrive folder and moved into it.

       1.) Create and save an Office document in any local folder outside of the local instance of a OneDrive folder.

       2.) Using Windows Explorer, move the file into the local instance of a OneDrive folder.

       3.) Open the file <- Only the local instance is accessed, not the online instance.

       4.) Save the file <- Only the local instance is accessed, not the online instance.

    This is the expected behaviour: all syncing is performed as a background task by OneDrive.exe, not the Office application.

    Case 2: Office file is created within the local instance of a OneDrive folder.

       1.) Create and save an Office document directly within the local instance of a OneDrive folder.

       2.) Close the file.

       3.) Open the file <- Only the online instance is accessed, not the local instance.

       4.) Save the file <- Only the online instance is accessed, not the local instance.

    This is completely undesired behaviour. Office Sync opt-out settings are being ignored and all syncing is being performed at the time of opening and saving by the Office application, not OneDrive.exe.

    I'd just like to confirm that what Jeff Pollard has described is exactly precisely on point. Thanks so much for such clarity Jeff.

    For those who for some reason don't want to delete the FileCoAuth.exe file, a temporary workaround I found useful for me, while Microsoft fixes this issue, has been to cut and paste my problematic file(s) from OneDrive to desktop then back from desktop to OneDrive folder → issue fixed (for that single file). Although, if you have no particular reason to keep FileCoAuth.exe, deleting it is probably a better workaround for the moment.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-02-13T17:42:04+00:00

    Unfortunately, deleting or renaming the filecoauth.exe doesn't work as I first believed.  OneDrive reinstalls itself almost immediately and definitely within 24 hours.  The very behaviour that malware/viruses do to keep themselves on a system.

    Saving files to another folder outside the OneDrive sync folder then copying them back to sync works, but that's not a workable solution for general users.  They will either 1) not do it because it's too cumbersome, or 2) they'll do it and then forget to move the files back to OneDrive so they won't them sync'd.

    Was this answer helpful?

    0 comments No comments