What happened to Windows 2.6.3?
Asked by Steven Smith:

I was on Sourcetree 2.6.3 Windows and LFS downloads were incredibly slow. Updating the embedded git would not take me past LFS 2.0.2. I tried re-downloading Sourcetree and installing, but it rolled me back to 2.5.5 and downgraded the embedded git from 2.17 to 2.16, but with LFS still at 2.0.2. I did a complete uninstall of Sourcetree and wiped everything in AppData. I also took the extra step of removing every version of git from my computer and any other source control software that I had.  

I re-downloaded a new installer and am now at 2.5.5.0 with embedded git 2.16 but now I have LFS 2.3.4.  

A co-worker was lucky enough to get a good update to Windows 2.6.3 with embedded git 2.17 and LFS 2.4. His LFS downloads are MUCH faster than everyone on the team.  

Why can I no longer update back to 2.6.3? Why is 2.5.5 the only version offered on the website now?

------------------------------

Update: there is a manual download link for 2.6.3 <https://downloads.atlassian.com/software/sourcetree/windows/ga/SourceTreeSetup-2.6.3.exe>


Answers:
author: Mikael Sandberg
body: 2.5.5 is still being rolled out, Sourcetree moved to staged updates about a year and a half ago, have a look at this [blog post](https://blog.sourcetreeapp.com/2016/11/16/adding-staged-updates-to-sourcetree/) about it. Only once the staged roll out reaches 100% will it be available to download from the website.

comments: author: Mikael Sandberg
body: You can always download and install Git separately instead of using the embedded version. I have been running Git 2.17 for a while now with Sourcetree 2.5.5 without any issues.


author: Steven Smith
body: Thanks for the reply. I tried using system git 2.17 and LFS 2.4 but then sourcetree started giving me password errors. Even when I removed and re-added all user accounts, it wouldn't let me touch my repos on bitbucket. Switching back to embedded fixed this. I could give it another shot with this fresh install.


author: Mikael Sandberg
body: The password errors could be from the Git Credential Manager for Windows, we have had issues with it and I always recommend not to install it, but it is not always that my developers follows my instructions...


author: Steven Smith
body: I installed git with the credential manager disabled (thanks for the tip). Though it still doesn't want to play nice with sourcetree. This time instead of being a password issue, it's a two-factor issue (which is not a problem with embedded).

```
remote: Two-step verification is enabled for this account.
remote: We recommend using SSH when two-step verification is enabled: https://confluence.atlassian.com/x/zYoMEg
remote: To proceed with HTTPS, you must use an app password to authenticate: https://confluence.atlassian.com/x/9DJmMQ
fatal: unable to access '(Removed before posting)': The requested URL returned error: 403
```

I've used SSH in the past but was advised by Atlassian to use OAuth instead for performance reasons with LFS. I'm not sure why this error message is asking me to make an app password.  

Any ideas why system/embedded would behave differently?


author: Mikael Sandberg
body: I am wondering if the embedded version is getting the app password from Sourcetree. You could try and generate a new app password and change your repository URL to this: [https://\[your_user_name\]:\[app_password\]@bitbucket.org/\[your_user_name\]/\[repo_name\].git](https://%5Byour_user_name%5D:%5Bapp_password%5D@bitbucket.org/[your_user_name]/[repo_name].git)