• Icon: Bug Bug
    • Resolution: Resolved Locally
    • Icon: Highest Highest
    • None
    • None
    • None
    • Windows 10 Build 1478.

    • Severity 2 - Major

      After I've updated to source tree 2.5.5 it prompted me:

      ---------------------------
      SourceTree.exe - This application could not be started.
      ---------------------------
      This application requires one of the following versions of the .NET Framework:
      .NETFramework,Version=v4.7.1

      Do you want to install this .NET Framework version now?
      ---------------------------
      Yes No
      ---------------------------

      However I CAN'T install this .Net FW  version because my Windows 10 version, which is controlled by my company, doesn't support this FW version.

      Version 4.6.2 is the last supported by this windows 10 Build 1478.

      https://docs.microsoft.com/en-us/dotnet/framework/get-started/system-requirements

       Please, roll back the support for .Net 4.6.2 OR prompt-me to install a new dotnet version BEFORE upgrading source tree version, it's in an unusable state

            [SRCTREEWIN-8613] Source tree requires .NET 4.7.1 AFTER update

            Typical Atlassian nonsense.

            James Jordan added a comment - Typical Atlassian nonsense.

            tedyeh added a comment - - edited

            Great.

            tedyeh added a comment - - edited Great.

            The originally reported issue was not about the conflict between .NET versions 4.7.1 and 4.7.2, but rather that requiring at least 4.7.1 excludes a large batch of users on early versions of Windows 10 from using the software. Our corporate systems lock us at a certain version of Windows on which .NET 4.7+ can't be installed.

            https://docs.microsoft.com/en-us/dotnet/framework/get-started/system-requirements

            So we're just moving on to other tools. If you'd like us to use Sourcetree, you should evaluate whether you really need to require .NET version 4.7+.

            Riley Major added a comment - The originally reported issue was not about the conflict between .NET versions 4.7.1 and 4.7.2, but rather that requiring at least 4.7.1 excludes a large batch of users on early versions of Windows 10 from using the software. Our corporate systems lock us at a certain version of Windows on which .NET 4.7+ can't be installed. https://docs.microsoft.com/en-us/dotnet/framework/get-started/system-requirements So we're just moving on to other tools. If you'd like us to use Sourcetree, you should evaluate whether you really need to require .NET version 4.7+.

            T Ngo added a comment -

            Adding the two registry entries keys from the bottom of this page (see the known issues section) worked for me.

            T Ngo added a comment - Adding the two registry entries keys from the bottom of this page (see the known issues section) worked for me.

            minnsey added a comment -

            This is due to a bug in a release of Windows 10 Insider Preview, this shoudl now be fixed in the latest releases.

            https://blogs.windows.com/windowsexperience/2018/09/05/announcing-windows-10-insider-preview-build-17754/#KWZJ5ZZjSFBEE5aB.97

            minnsey added a comment - This is due to a bug in a release of Windows 10 Insider Preview, this shoudl now be fixed in the latest releases. https://blogs.windows.com/windowsexperience/2018/09/05/announcing-windows-10-insider-preview-build-17754/#KWZJ5ZZjSFBEE5aB.97

            Vinay Chandra added a comment - - edited

            Do not update the file.

            SourceTree\SourceTree.exe.config
            

            You should update the config in this file

            SourceTree\<LatestVersion>\SourceTree.exe.config
            

            Vinay Chandra added a comment - - edited Do not update the file. SourceTree\SourceTree.exe.config You should update the config in this file SourceTree\<LatestVersion>\SourceTree.exe.config

            You need to put only one supportedRuntime, this config solve my problem

             
            <startup>
            <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.7.2"/>
            </startup>

            Elias Rincon added a comment - You need to put only one supportedRuntime, this config solve my problem   <startup> <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.7.2"/> </startup>

            Patrick Skjennum added a comment - - edited

            Using the "SourceTree.exec.config" only prompts an error:

            Patrick Skjennum added a comment - - edited Using the "SourceTree.exec.config" only prompts an error:

            lukevp added a comment - - edited

            If 4.7 is required, the change to Version=v4.7 that Paul mentioned would be the preferred fix so it will run on any version of 4.7 rather than just on the .1 minor release, but just as a guess I would say they're probably using a .NET Standard 2 library to code share with the Mac release, which requires targeting 4.7.1 or newer.  If that's the case, they really do need to restrict to 4.7.1 or greater, and they will have to do it like this:
             

            <startup>    
                <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.7.1"/>        
                <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.7.2"/>  
            </startup>

             

            Sometimes it's really surprising and disappointing the quality of releases that come out for SourceTree.  I remember the weird animation issue that caused all the text to be blurred for 2-3 seconds every time you transitioned screens and it took several months for that to be fixed.  My team's already moved away from Atlassian products except SourceTree, and we're all finding ourselves using GitKraken and GitExtensions a lot more these days, which is a shame.  SourceTree is my favorite but I can't convince my team to use them when we keep having breaking workflow issues like this.

             

            lukevp added a comment - - edited If 4.7 is required, the change to Version=v4.7 that Paul mentioned would be the preferred fix so it will run on any version of 4.7 rather than just on the .1 minor release, but just as a guess I would say they're probably using a .NET Standard 2 library to code share with the Mac release, which requires targeting 4.7.1 or newer.  If that's the case, they really do need to restrict to 4.7.1 or greater, and they will have to do it like this:   <startup> <supportedRuntime version= "v4.0" sku= ".NETFramework,Version=v4.7.1" /> <supportedRuntime version= "v4.0" sku= ".NETFramework,Version=v4.7.2" /> </startup>   Sometimes it's really surprising and disappointing the quality of releases that come out for SourceTree.  I remember the weird animation issue that caused all the text to be blurred for 2-3 seconds every time you transitioned screens and it took several months for that to be fixed.  My team's already moved away from Atlassian products except SourceTree, and we're all finding ourselves using GitKraken and GitExtensions a lot more these days, which is a shame.  SourceTree is my favorite but I can't convince my team to use them when we keep having breaking workflow issues like this.  

            This change also worked for me too

            // edit file SourceTree.exe.config
            
              <startup>
                <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.7"/>
              </startup>
            

             can we see this is captured in the next release

            Paul Maxfield added a comment - This change also worked for me too // edit file SourceTree.exe.config <startup> <supportedRuntime version= "v4.0" sku= ".NETFramework,Version=v4.7" /> </startup>  can we see this is captured in the next release

            minnsey added a comment - - edited

            For what its worth .NET framework should be backwardly compatible, e.g. 4.7.1 builds should run on 4.7.2.

            Indeed it appear Sourcetree for Windows 2.4.8, which requires 4.5.2, is running OK on 4.7.2

            Something odd is going on somewhere.

            minnsey added a comment - - edited For what its worth .NET framework should be backwardly compatible, e.g. 4.7.1 builds should run on 4.7.2. Indeed it appear Sourcetree for Windows 2.4.8, which requires 4.5.2, is running OK on 4.7.2 Something odd is going on somewhere.

            I changed the 4.7.1 to 4.7.2 and that also worked.

            Brett Morrison added a comment - I changed the 4.7.1 to 4.7.2 and that also worked.

            minnsey added a comment -

            Hi jay2002663784

            Thanks for the update.

            minnsey added a comment - Hi jay2002663784 Thanks for the update.

            Thanks Jay! Confirmed working.  For me: SourceTree.exe.config file was located here: %userprofile%\AppData\Local\SourceTree\app-2.6.10

            Brett Morrison added a comment - Thanks Jay! Confirmed working.  For me: SourceTree.exe.config file was located here: %userprofile%\AppData\Local\SourceTree\app-2.6.10

            https://stackoverflow.com/questions/44237105/this-application-requires-one-of-the-following-versions-of-net-framework

             

            SourceTree.exe.config, change the 4.7.1 to 4.7 and the app works.  Easy workaround, took me a lot of messing around to find a solution, so hope it helps someone.

            Jay Beeckman added a comment - https://stackoverflow.com/questions/44237105/this-application-requires-one-of-the-following-versions-of-net-framework   SourceTree.exe.config, change the 4.7.1 to 4.7 and the app works.  Easy workaround, took me a lot of messing around to find a solution, so hope it helps someone.

            Yep, same here. Can't get past it.

            Brett Morrison added a comment - Yep, same here. Can't get past it.

            TheDM128 added a comment -

            Newest updates on Win10 was installed today and Sourcetree can't run with reporting same error. Actual framework into system is 4.7.2

            TheDM128 added a comment - Newest updates on Win10 was installed today and Sourcetree can't run with reporting same error. Actual framework into system is 4.7.2

            rb0urd0n added a comment -

            Same for me: I can't install SourceTree due to this FW.

            Installing an old version is really a bad-quick fix, I hope it will be resolved soon...

            rb0urd0n added a comment - Same for me: I can't install SourceTree due to this FW. Installing an old version is really a bad-quick fix, I hope it will be resolved soon...

            Having same issue Source tree was just not running. Tried installing from fresh setup but it doesn't even get install and just gave the same error on setup. Although I already have .NET Framework version installed.

            mohit lanxess added a comment - Having same issue Source tree was just not running. Tried installing from fresh setup but it doesn't even get install and just gave the same error on setup. Although I already have .NET Framework version installed.

            Erik B added a comment - - edited

            Just ran into this myself. Solution is simple, but stupid: download and install SourceTree 2.4.8.0 from the version archive and never update again. Not a very future proof solution but this is where we're at with this.

            [On Windows 10 build 1607]

            Erik B added a comment - - edited Just ran into this myself. Solution is simple, but stupid: download and install SourceTree 2.4.8.0 from the version archive and never update again. Not a very future proof solution but this is where we're at with this. [On Windows 10 build 1607]

            Chris King added a comment -

            Same problem on Windows 8, which can not install this version of .net (ever)

            https://docs.microsoft.com/en-us/dotnet/framework/install/on-windows-8?utm_source=getdotnet&utm_medium=referral

             

             

            Chris King added a comment - Same problem on Windows 8, which can not install this version of .net (ever) https://docs.microsoft.com/en-us/dotnet/framework/install/on-windows-8?utm_source=getdotnet&utm_medium=referral    

            Gazmataz added a comment -

            Same here, I've used SourceTree with no problems for two years on this laptop.

            A crash last week meant I spent the weekend doing a factory reset.

            Came back to the website to download again today and now it's incompatiable with my Windows version?

             

            Incidently the release notes for the latest release or any requirements aren't easy to find when hitting the website for a new download directly; it's just click here to install.  This is the best I could find without guessing the url based on the file download:

            https://www.sourcetreeapp.com/download-archives

             

             

            Gazmataz added a comment - Same here, I've used SourceTree with no problems for two years on this laptop. A crash last week meant I spent the weekend doing a factory reset. Came back to the website to download again today and now it's incompatiable with my Windows version?   Incidently the release notes for the latest release or any requirements aren't easy to find when hitting the website for a new download directly; it's just click here to install.  This is the best I could find without guessing the url based on the file download: https://www.sourcetreeapp.com/download-archives    

            Same thing here. The auto-update has downloaded the update without checking if .NET 4.7.1 could be installed. Now I don't have Sourcetree anymore, and can't upgrade PC because Windows updates are controlled by our system administrators.

            Will need to find an alternative to get the job done.

            Laurent Debacker added a comment - Same thing here. The auto-update has downloaded the update without checking if .NET 4.7.1 could be installed. Now I don't have Sourcetree anymore, and can't upgrade PC because Windows updates are controlled by our system administrators. Will need to find an alternative to get the job done.

            what the solution. I am facing same issue in windows 10 pro.

            erum hannan added a comment - what the solution. I am facing same issue in windows 10 pro.

            vstelmakh added a comment -

            Release notes says that "this release requires .NET 4.7.1 or higher for installation". It's "for installation", not "for running after we installed the app". Agree with reporter.

            vstelmakh added a comment - Release notes says that "this release requires .NET 4.7.1 or higher for installation". It's "for installation", not "for running after we installed the app". Agree with reporter.

            Also for me, it either auto-updated, or it was an accidental click to upgrade. It's funny, I did avoid trying to update the first few times. Either way, how can I force install an older version until my company also supports 4.7.1? (Currently we also only go up to 4.6.x)

            Eric Sender added a comment - Also for me, it either auto-updated, or it was an accidental click to upgrade. It's funny, I did avoid trying to update the first few times. Either way, how can I force install an older version until my company also supports 4.7.1? (Currently we also only go up to 4.6.x)

            The message says .Net 4.71 is required, but doesn't mention that some windows 10 versions won't install this .Net version.

            Andrey Santanna added a comment - The message says .Net 4.71 is required, but doesn't mention that some windows 10 versions won't install this .Net version.

            karl wiggisser added a comment - - edited

            To be honest, it's written in the release notes, in **BOLD RED**. I'm sure you have read them, before installing an update to an application crucial for your workflow ...

            karl wiggisser added a comment - - edited To be honest, it's written in the release notes, in ** BOLD RED **. I'm sure you have read them, before installing an update to an application crucial for your workflow ...

              Unassigned Unassigned
              c22cc50ff2ee Andrey Santanna
              Affected customers:
              15 This affects my team
              Watchers:
              32 Start watching this issue

                Created:
                Updated:
                Resolved: