Windows 11 24H2 update deletes configurations.

I am using Duplicati as a Windows service, upgrading to Windows 11 24H2 deletes the configurations that are in:
C:\Windows\System32\config\systemprofile\AppData\Local

Access rights to these folders are also lost.

Is there any way to avoid this?

Thank you very much.

Welcome to the forum @EddieK

First please see if the old Windows folder is now in C:\Windows.old and if so, save its Duplicati folder before Windows automatically deletes Windows.old roughly 10 days after upgrade date.

IMO this is quite a destructive thing for Windows to do, but there seems to be no way to avoid it short of not installing the occasional version upgrade that is trying to set up for version rollback:

Go back to the previous version of Windows

I would expect new access rights to set up the same way as before, meaning it’s restricted here:

C:\Windows\System32>cd config
Access is denied.

and you must use Command Prompt (Admin) or similar, or maybe ask File Explorer to let you in.

Since it seems like Microsoft insists on doing this, even though the SYSTEM user (and its profile) aren’t exclusively for Windows use that I can see, an avoidance is to move to a different location.

C:\ProgramData\Duplicati is one that some people use. You install Duplicati service again, using:

--server-datafolder: Duplicati needs to store a small database with all settings. Use this option to choose where the settings are stored. This option can also be set with the environment variable DUPLICATI_HOME.

Moving the Duplicati-server.sqlite DB will let the service start up with old job config, but Database screen will have to be used to point the individual random-letters.sqlite job DBs to the new paths.

You can edit the Local database path to change the first part to the new home, then Save that.

When done, consider changing permissions on the new folder to prevent unauthorized access, as original location was protected (except from Windows) by being in a protected config folder.

is the issue looking for some code change to at least warn the user, and maybe do more to help.

Thank you very much for your answer, it is very useful.