I was able to get rid of the button like this:
- Open RegEdit
- Go to HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\StorageProvider\OneDrive
- Remove or rename the key StorageProviderKnownFolderSyncInfoSourceFactory
- Restart Windows Explorer
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hello,
In the latest release of Windows Insider Home Preview (I have an option everywhere I go in file explorer to "Start Back Up", clicking on it leads me to the onedrive dialogue to back up folders. This is incredibly annoying and I cannot find out how to disable it, even though all my backup features are off.
How can I disable this?
(Preview build 23481)
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.
I was able to get rid of the button like this:
Or you can do the recommended step someone mentioned earlier and leave the key there, but change it's value to "{null}". That worked for me through reboots (and thanks to the person the recommended that).
Back up the key first if you like.
EDIT: I was wrong, it came back for me on reboot eventually.
Follow the detailed list in the post from "OC_"
This option works for me BUT if I restar my pc its creating a new key in RegEdit and coms back.
YES, but you can deny the creation of new key by modifying permissions.
This option works for me BUT if I restar my pc its creating a new key in RegEdit and coms back.
I was able to get rid of the button like this:
- Open RegEdit
- Go to HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\StorageProvider\OneDrive
- Remove or rename the key StorageProviderKnownFolderSyncInfoSourceFactory
- Restart Windows Explorer
๐๐๐ - THANK YOU!!!
Two things I would suggest however:
- Export/Backup the Key before making any changes.
- I suggest not deleting the key, for a couple of reasons. The first is removing the key completely may have unexpected results at some point. The Second is that there is really nothing that would prevent that key from being restored by a future MS update. Instead, after backing up the key, I replaced the value date with {NULL}, which also fixed the issue, as well as provides for a way to "lock" the key from being modified in the future if needed by restricting the permissions to "read only" and unlocking write permissions to the key only as needed.
Good Call thanks for the update.