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-08T05:02:04+00:00

    Here's proof the registry changes do NOT fix the problem.  Oh, and now I've been told by a Tier II support rep that I'm not important enough to escalate this past him.  Guess how warm and fuzzy that made me feel?  I'm thinking the press are the next people who need to hear about this.

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

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-02-07T21:14:00+00:00

    I concur.  I swear I tested that with the rep on the phone but it clearly continues to do the same thing.  Gotta love the competency of MS documentation of late.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-02-07T20:56:57+00:00

    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

    I changed those registries on my system and the problem is still there. AutoSave is unrelated unfortunately.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-02-07T18:19:38+00:00

    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 BSB, 

    I admit autosave is a problem but I am not sure how that relates to the problem in this thread? Is autosave connected to FileCoAuth.exe and thus the sync process for new files?   -Bob

    Was this answer helpful?

    0 comments No comments