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: Most helpful
  1. Anonymous
    2018-02-01T14:13:31+00:00

    Sky,

    With all due respect, that's a joke, right?  This is happening on 100% of systems internally AND at client locations.  Clients are furious.  We have multiple Office 365 clients ready to leave for Google because Microsoft is so clueless here and just comes back with these laughable replies.  One client with SEVERAL HUNDRED GB of data followed these directions and spent days resync'ing OneDrive.  That's just unacceptable.  You're also running up cell data bills for clients who use hotspots to access the Internet from laptops.  Normally OneDrive waits until a file is closed before sync'ing it from the local disk, but when a 50MB file is open in Excel and every time one clicks save you have to wait for it to WASTE cell data to save the file is just beyond unacceptable.  Time for Microsoft to step up, realize you have a BUGGY product, admit you have a buggy product, and issue a fix.  Get rid of the junk code that even allows Office to save directly to SharePoint if One Drive is running.  Basically you need an If-Then statement.  If OneDrive is running THEN DON'T save to SharePoint.  It's VERY SIMPLE code.  I'm happy to write it for you.

    My apologies for the frustration here, but Microsoft's answers to every issue of late has reverted to the Window 2000-era excuses of, "can't repro" or "by design" and that's no longer acceptable.  You have REAL competition in Google and Google Drive NEVER hijacks Office apps to force this.  You're getting ready to lose customers over poor code and even poorer internal testing and reproduction skills.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2018-01-24T18:39:39+00:00

    I have a client with a very similar issue.

    Every time she opens a file from OneDrive and then goes back to save updates to it (F12), it takes her to the Sharepoint path, instead of the local OneDrive path and she encounters an error that the file already exists and she has to rename it. If she uses the >File>Save As> and then selects OneDrive the issue doe snot seem to occur, but if she then tries to open the file from recent documents list, it take her back to the Sharepoint path and the updates are missing. The synchronization between the local One Drive folder and the Online Sharepoint location seems to be delayed now as well. This all started within the last 2-3 weeks and is impacting all Office applications.

    One Drive App Version: 17.3.7131.1115

    We have tried the same suggestions already as well:

    Turned "Office Sync..." off in OneDrive Settings

    Turned "Office Sync..." back on in OneDrive Settings

    Paused and restarted Sync

    Reset OneDrive sync

    None of these things have resolved the issue.

    The only work around we have found is to use File>Save As, which is multiple additional clicks and is very irritating to the client.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2018-01-10T21:08:14+00:00

    Hi Remboy, 

    I can understand the frustration.  The new OneDrive from the most recent update is definitely causing these problems.  Like you all of us here work directly out of our OneDrive Synched folder and now experience the duplicate files or delay when opening a file depending on how "Use Office 2016 to sync Office files" is checked/unchecked.   It seems many of us just want OneDrive to work similar to DropBox.  The collaboration features MS is trying to add is causing problems for us general users and the option provided to turn that off is not working correctly.   

    -Bob

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2018-01-29T21:59:50+00:00

    Workaround:

    The following steps will prevent the undesired behaviour described above:

    In Task Manager, under the Details tab, check whether a task named 'FileCoAuth.exe' is running. If so, end the task.

    In Windows Explorer, navigate to the following location:

    %localappdata%\Microsoft\OneDrive\

    In that folder, you will find a sub-folder which corresponds to the current OneDrive version number (e.g. 17.3.7294.0108). In that sub-folder, find and rename the following file:

    FileCoAuth.exe -> rename as FileCoAuth.exe.bak

    Now, any Office file created within an Office application will save directly to the local instance of the OneDrive folder, and will continue to do so when re-opened and re-saved, or saved with a new name. OneDrive.exe will continue to perform online syncing independently in the background.

    Furthermore, this restores the ability to save files directly to a local instance of the OneDrive folder from within an Office application, without the requirement to remain permanently signed in (so don't expect this workaround to last for long!).

    Cheers

    Jeff

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments