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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2018-02-07T14:42:27+00:00

    It is literarily a virus because it even duplicates itself! Last night it automatically created a new OneDrive version directory with FileCoAuth.exe intact - after I changed it to FileCoAuth.exe.old

    Your script works well as long as FileCoAuth.exe is not running yet - permission denied issue if it is already running.

    EDIT: It looks like the script doesn't work because as soon as the FileCoAuth.exe was deleted a minute later a new version folder was created and OneDrive reboots itself with new version. 0_0

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-02-07T05:20:26+00:00

    Bob,

    No, the production ring has the same problem.  So long as FileCoAuth.exe is in your OneDrive folder it will continue to happen.  Deleting or renaming the file solves it, until Microsoft puts another copy of that malicious file on your system with an unwanted OneDrive update then you have to either have a script that automatically deletes it or you'll have to remove it yourself.

    BSB

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-02-07T05:13:49+00:00

    You're kidding right?  How about we do this.  You setup a PC and I'll setup a GoToMeeting where you can share your desktop with me and I will show you what happens because it's becoming painfully clear Microsoft has no desire to replicate this or Microsoft doesn't know how to replicate the issue that many of us can duplicate on 100% of systems.  Literally I have 9 Dell PCs in my office and I can reproduce it on 100% of them.  I can reproduce this on 100% of our client systems that I've tried it on as well.  So please stop wasting our time with your claims that you cannot reproduce this and put let me prove it too you.  

    So send me a PM and I'll send you my phone number.  Anyway, if you'd like to actually see it in action, try this:

    As you can see, I am running a fully patched version of Office 2016:

    The build of OneDrive is very clear in the video I uploaded.  I also proved my Office Save Options are setup correctly to save to the local disk.  The ONLY solution thus far to this MASSIVE BUG is to rename or delete the malicious FileCoAuth.exe file.

    [Video link is masked by forum moderator, as it contains PII info]

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-02-07T00:30:17+00:00

    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

    Was this answer helpful?

    0 comments