Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configuration "lost" after Windows 10 Anniversary Update when running as a service #1950

BrianLakstins opened this issue Sep 26, 2016 · 6 comments


None yet
7 participants
Copy link

commented Sep 26, 2016

I have:

  • searched open and closed issues for duplicates

Version info

Duplicati Version:
Operating System: Windows 10 Version 1607 (OS Build 14393.187)
Backend: Any

Bug description

After upgrading to Windows 10 (Version 1607), the Duplicati's configuration while running as a service was lost.

Steps to reproduce

  • Install Duplicati as a service on Windows 10
  • Add some configuration
  • Upgrade to Version 1607

Actual result: The Duplicati configuration goes back to what it is after a fresh install
Expected result: The Duplicati configuration should stay the same.


Screenshots would not be applicable.

debug log

A debug log would not be applicable.

More information

The configuration when running as a service using the "System" user is stored in:


The folder is moved to:


during the upgrade. If you run an advaced "Disk Clean", the "c:\windows.old" folder is deleted.

An update to the program could change the default data directory to c:\programdata\Duplicati when running in a non-interactive state (like the WindowsService).

For short term workaround, I'm using the environment variable DUPLICATI_HOME and setting it to a folder that I'm including in my standard backups. This can be done by using the command line:

c:> setx DUPLICATI_HOME c:\programdata\Duplicati /m

It will then have the same configuration for all users on the system. If Duplicati is only running as a service, then that should be fine. If there are multiple users running interactively, then this would probably not be the best solution.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.


This comment has been minimized.

Copy link

commented Apr 11, 2017

Still an issue when upgrading from Anniversary Update to Creators Update.


This comment has been minimized.

Copy link

commented May 4, 2017

I think this would be fixed with #2222


This comment has been minimized.

Copy link

commented Sep 30, 2017

I doubt that #2222 is sufficient to fix this - Windows updates seem to clear out the C:\Windows\System32\config\systemprofile\AppData directory, or at least the Local part of it.

IMO the Windows service should configure the server to store in C:\ProgramData\Duplicati instead of under the system user profile. That way the data will survive Windows updates. Non-service runs should go ahead and use the user's profile directory as they currently do.


This comment has been minimized.

Copy link

commented Oct 19, 2017

I was just hit by this same problem when I upgraded to the Fall Creators Update. The update wiped out all of my Duplicati settings under C:\Windows\System32\config\systemprofile\AppData\Local\Duplicati

I found a backup of them under C:\windows.old and restored from there.


This comment has been minimized.

Copy link

commented Oct 19, 2017

This seems to be a problem in the Windows 10 Upgrade procedure. The upgrade should take care of preserving the contents of the systemprofile folder, but fails in doing so.
Explanation and some workarounds can be found here:


This comment has been minimized.

Copy link

commented Oct 27, 2017

This same thing happened to me when updating to the Fall Creators Update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.