A SourceTree upgrade loses project folder

[mnelvers]

I like SourceTree.  I have used it at previous companies and I managed to convince my current company to provide SourceTree as a Git UI option and I am using it.  It has been upgraded twice since the company started allowing it.  Each time, after the upgrade, I had to go through the startup configuration process, again.  I will concede that the second time through, it did automatically populate the fields with my previous entries.  I am not sure why we have to go through the configuration process each time.  There is a Skip button, but I am unclear what that will do.  If this could be clarified or simplified, that would be great.

However, what is lost is the project folder setting.  After an upgrade, when I attempt to clone a new repository, the project folder is changed to some default folder.  I have to go into the Options UI and re-enter my desired folder for that.  It would, also, be nice if this could be corrected.

[Martin Runge]

Hi @mnelvers

Welcome to the Atlassian Community!

Does your company use a software deployment tool to "provide" SourceTree?
If your IT department configures the Sourcetree update package as a clean reinstall rather than an incremental upgrade, the deployment tool could actively wipe out the local directories before applying the new version. This clean-install behavior would destroy the user-specific XML and configuration files that contain your preferences.