Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Windows Installation Cabinet File Corrupt

When I attempt to install the SourceTree application, Windows halts about half-way through the installation and presents the following error message


A file that is required cannot be installed because the cabinet file C:\ProgramData\Atlassian\SourceTree 1.6.8\install\ has an invalid digital signature. This may mean that the cabinet file is corrupt.

I have tried installing in multiple locations, attempted to find the file and delete it in hopes of remediation (no file found), tried installing on both C and D drives, and tried restarting and then installing. Nothing works. I have never had such a bizarre problem before, and I severely disappointed that I may not be able to use SourceTree!


I am running 64-bit Windows 10 (Build 9860). I just finished doing a fresh reinstall of Win10 and SourceTree worked fine on my previous Windows 10 installation, but the reinstall seems to have broken it?

3 answers

Have a look at SourceTree won't install on a Windows Server Computer and in particular the Answer from Bhushan.

I have faced the same issue multiple times and this is very annoying. I am also looking for the solution of this problem that is very stressful as the  kitchen cabinet  problem .

I commented on the post you refer to. It seems the installer of version 1.8.3 has the same issues and running the installer As Administrator doesn't solve the problem.

There's a Bug dedicated to this problem: 

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events