• 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

            Monique Khairuliana (Inactive) made changes -
            Workflow Original: JAC Bug Workflow v3 [ 3454192 ] New: SRCTREE JAC Bug Workflow [ 3743587 ]
            Monique Khairuliana (Inactive) made changes -
            Workflow Original: SourceTree Bug Workflow [ 2669385 ] New: JAC Bug Workflow v3 [ 3454192 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            minnsey made changes -
            Resolution New: Resolved Locally [ 7 ]
            Status Original: Verified [ 10005 ] New: Resolved [ 5 ]

            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.
            Brett Morrison made changes -
            Link New: This issue duplicates SRCTREEWIN-8613 [ SRCTREEWIN-8613 ]

            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 made changes -
            Priority Original: Medium [ 3 ] New: Highest [ 1 ]
            minnsey made changes -
            Affects Version/s New: 2.6.10 [ 81401 ]

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

                Created:
                Updated:
                Resolved: