Hi Gary, we're aware of this and it's been reported in our bug tracker at SRCTREEWIN-7244. There's a workaround that seems to be working for most of our users, I'll copy it here for you:
From a working install collect the accounts.json and passwd files.
Delete the Atlassian folder from the AppData/Local directory for your user. Run the installer for 2.3.1, close it when you get the blank login window. Place the account.json and passwd files into the Atlassian/SourceTree folder. Rerun the installer. It should detect the account and password from those files and bypass the request for a login.
Some users shared other tips too, so you might want to check this Community thread too.
If this is not working for you, please comment on the bug ticket as this will help our developers get the issue addressed. You can also watch the ticket to be notified of further updates.
If you have any questions, let us know! :)
Regards
Ana
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.