Error installing Expression blend

Hi Guys

I am trying to install Expression studio and web studio on my machine but i keep on getting the following error.

"Setup encountered and error: The signature of the file 'ExpresssionStudioManifest.cab' could not be verified and the file cannot be trusted.

Has anyone coma across that error before?

Download the ISO file and mount it and install it from there.

The message happens with setup fails to trust a file (via ::WinVerifyTrust()). This can be caused by a number of things...

1. For external customers, we generally see this message if a file has been corrupted, possibly by a bad download or bad media. But we see it most frequently around downloaded ISOs that aren't CRC'ed/Hash checked before being burned to DVD or worse, mounted by 3rd party apps that tend to be unreliable.

2. Internally, it's usually seen when we Test (vs Release) sign a build and the internal users machine does not trust our internal Test certificate, or if a build isn't signed correctly. If one of our Test signed builds got out into the wild (which isn't a bad thing), the world's machine would simply not trust it. You can invoke the same behavior for our released software, by removing trust for the Microsoft Root Authority cert on your system, which is a really bad thing to do (so don't do it). You can rule this out by right-clicking on the file, looking at the Digital Certificate and seeing the certificate chain is trusted all the way up to the root.

http://social.expression.microsoft.com/Forums/en/blend/thread/5dfccb92-c3ab-4d8f-8862-80f1fdf6dc51

http://social.expression.microsoft.com/Forums/en/general/thread/c191b2e0-8ddb-406d-85b7-936f35da13e0

1 Reply

Know the answer? Post it — somebody with the same question will find it here.

15y ago
Download the ISO file and mount it and install it from there.

The message happens with setup fails to trust a file (via ::WinVerifyTrust()). This can be caused by a number of things...

1. For external customers, we generally see this message if a file has been corrupted, possibly by a bad download or bad media. But we see it most frequently around downloaded ISOs that aren't CRC'ed/Hash checked before being burned to DVD or worse, mounted by 3rd party apps that tend to be unreliable.

2. Internally, it's usually seen when we Test (vs Release) sign a build and the internal users machine does not trust our internal Test certificate, or if a build isn't signed correctly. If one of our Test signed builds got out into the wild (which isn't a bad thing), the world's machine would simply not trust it. You can invoke the same behavior for our released software, by removing trust for the Microsoft Root Authority cert on your system, which is a really bad thing to do (so don't do it). You can rule this out by right-clicking on the file, looking at the Digital Certificate and seeing the certificate chain is trusted all the way up to the root.

http://social.expression.microsoft.com/Forums/en/blend/thread/5dfccb92-c3ab-4d8f-8862-80f1fdf6dc51
http://social.expression.microsoft.com/Forums/en/general/thread/c191b2e0-8ddb-406d-85b7-936f35da13e0

0