• Icon: Bug Bug
    • Resolution: Resolved Locally
    • Icon: Highest Highest
    • None
    • 2.5.5, 2.6.10
    • General
    • Standalone SourceTree executable v2.5.5

       

    • Severity 2 - Major

      Have a developer who upgraded his SourceTree to 2.5.5. It states that the application could not be started because it requires .NET 4.7.1. Workstation has 4.7.2 installed so it appears that SourceTree isn't detecting the minor version update. I did the same update and had the same problem occur.

      SourceTree was working on the previous version without issue.

            [SRCTREEWIN-8623] SourceTree doesn't recognize .NET 4.7.2

            minnsey added a comment -

            This was due to a bug in certain Windows 10 Insider Preview builds, now fixed.

            https://blogs.windows.com/windowsexperience/2018/09/07/announcing-windows-10-insider-preview-build-17755/

            minnsey added a comment - This was due to a bug in certain Windows 10 Insider Preview builds, now fixed. https://blogs.windows.com/windowsexperience/2018/09/07/announcing-windows-10-insider-preview-build-17755/

            Stefan - Check out the comments in: SRCTREEWIN-8613. Modifying the .exe.config file works as a workaround.

            Brett Morrison added a comment - Stefan - Check out the comments in:  SRCTREEWIN-8613 . Modifying the .exe.config file works as a workaround.

            Downgrading to v2.4.8.0 fixed it (workaround) for me as well.

            Stefan Glatzel added a comment - Downgrading to v2.4.8.0 fixed it (workaround) for me as well.

            Hi @mmins,

            Just installed the beta and reinstalled the stable, neither of them created a setup log file in the locations you indicated. Even during uninstall the .NET 4.7.1. not found error is thrown.

            Stefan Glatzel added a comment - Hi @mmins, Just installed the beta and reinstalled the stable, neither of them created a setup log file in the locations you indicated. Even during uninstall the .NET 4.7.1. not found error is thrown.

            minnsey added a comment -

            Hi

            We're investigating this at the moment.

            Can any one provide a copy of the SquirrelSetup.log, I believe it should be in %localappdata%\Sourcetree for GA builds or %localappdata%\SourcetreeBeta for Beta builds.

            Thanks

            minnsey added a comment - Hi We're investigating this at the moment. Can any one provide a copy of the SquirrelSetup.log, I believe it should be in %localappdata%\Sourcetree for GA builds or %localappdata%\SourcetreeBeta for Beta builds. Thanks

            If SourceTree was Open Source, I would fix it myself!

            Brett Morrison added a comment - If SourceTree was Open Source, I would fix it myself!

            Yep, same here. I had to downgrade to v2.4.8.0 to get it running again. https://www.sourcetreeapp.com/download-archives

            Brett Morrison added a comment - Yep, same here. I had to downgrade to v2.4.8.0 to get it running again.  https://www.sourcetreeapp.com/download-archives

            I'm facing the same trying to install it on a freshly installed windows 10 fast insiders build (1809 build: 17755.1)

            Jose M. Villagrá added a comment - I'm facing the same trying to install it on a freshly installed windows 10 fast insiders build (1809 build: 17755.1)

            Since it's been a little while since this was reported I tried to recreate it.

            I'm still seeing it happen on my desktop, but when I try to replicate it on a test VM I'm unable to. SourceTree 2.5.5 and 2.6.9 both work with .NET 4.7.2 in that environment, so I think this is a problem with our corporate desktop environment, not with SourceTree.

            Ticket can be closed as cannot reproduce.

            Larry Peters added a comment - Since it's been a little while since this was reported I tried to recreate it. I'm still seeing it happen on my desktop, but when I try to replicate it on a test VM I'm unable to. SourceTree 2.5.5 and 2.6.9 both work with .NET 4.7.2 in that environment, so I think this is a problem with our corporate desktop environment, not with SourceTree. Ticket can be closed as cannot reproduce.

            minnsey added a comment -

            Hi

            We've not yet tested with 4.7.2, but we will.

            I know upgrading to 4.7.1 required at least one reboot before aps would recognize it. Does that help at all.

            minnsey added a comment - Hi We've not yet tested with 4.7.2, but we will. I know upgrading  to 4.7.1 required at least one reboot before aps would recognize it. Does that help at all.

              Unassigned Unassigned
              9ac25242c950 Larry Peters
              Affected customers:
              1 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: