Stop Office BACKUP THIS DOCUMENT prompt

Anonymous
2023-11-04T15:55:46+00:00

Excel and Word keep displaying a banner when I open a file "BACKUP THIS DOCUMENT - Access this file anywhere with OneDrive included in your subscription"

I have a backup system I use that I like and I don't need OneDrive to backup my files. How do I get OneDrive/Office 365/Windows to stop giving me this prompt?

I click the "X" or Schedule Backup Later to make the banner go away, but it just comes back a little while later. I've opened up the OneDrive app from the system tray and unselected everything from the OneDrive backup, but none of this helps and the prompt keeps coming back.

How do I get this to stop?

Microsoft 365 and Office | Excel | 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

150 answers

Sort by: Newest
  1. Anonymous
    2024-01-16T23:42:38+00:00

    The reason you get no response is the idiots at Microsoft have intentionally done this to entice you to give them all your personal information. Microsoft wants to control you. They won't remove it because they want your data (BIG BROTHER). How do you think they make money? They sell your personal information to advertisers. They won't fix the software because they need you to comply. I just keep hitting the "X". I won't succumb to their BS. As soon as another software company has software that can compete, I'm out of Microsoft entirely.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2024-01-15T18:21:48+00:00

    This has been driving me nuts too. So I uninstalled OneDrive. (And deleted the registry key mentioned in earlier replies).

    Seems to have sorted it for now ... only time will tell.

    I've got Dropbox and IDrive (and I could use Google Drive too if I really needed more cloud storage) so I think I can probably do without OneDrive. And if Microsoft's aim with this infuriating message was to get more customers for OneDrive ... well, they blew it!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2024-01-10T15:51:34+00:00

    It also breaks any program pointing to the location since they move the files to a onedrive folder.

    Took me a few hours to figure out how to revert back to the original file location. Meanwhile - panic.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2024-01-05T19:52:46+00:00

    Oops [insert sheepish look here]. Sorry for the false alarm.

    I see that *did* mess up my script so that the KFM value wasn't being updated.

    Ha -- No problem, glad it is still working.

    At the very least, this will likely need changes with the next major Office 365 release -- as the version number in the registry path will likely increment. And, of course, Microsoft could move to a more complex method that can't be easily circumvented at any time.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2024-01-05T19:44:21+00:00

    It's Baaaack!

    I've been running the registry patch every day to reset the nag date.

    But now, the nag is back in Word (and, I assume, every other Office app).

    There must be some new code that uses a different reminder switch.

    Any ideas?

    Still working for me (so far), in Word and Excel. Are you sure your script is running successfully?

    Check the value at

    HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\KFM, "KFMLastDismissTimestamp"

    You can convert the decimal number (the one in parenthesis) to a standard date using an online converter. Search the web for "epoch time converter", and enter that number. If the corresponding date does not reflect the last time you ran the script, then the script isn't running successfully.

    Oops [insert sheepish look here]. Sorry for the false alarm.

    I see that *did* mess up my script so that the KFM value wasn't being updated.

    Was this answer helpful?

    0 comments No comments