I just went to download the new Service Pack for Visual Studio which was released about a month ago. It’s pretty beefy – 430MB to download!
After installing, I got this error:
“The installation source for this product is not available. Verify that the source exists and that you can access it.”
I tried it twice (it sits for about 10 minutes before displaying that error) and cursed a lot more, but finally found the solution which worked for me posted at ScottGu’s blog:
About the â€The installation source for this product is not available†problem – if you are you using Windows Server 2003:
If you extract the .exe file and see the properties on the .msp file under “Digital Signatures” you will see that the signature/certificate is not valid. (ScottGu: I presume this is a bug?).
To â€fix†(ignore) this:
1) Open local security setting: Start -> Programs -> Administrative Tools -> Local Security Policy.
2) Click on “Software Restriction Policies” and if it shows “No Software Restriction Policies Defined” then insert a new (right click the left pane node).
3) 2 x click on the “Enforcement” entry and under “Apply software restriction policies to the following users:” section change to “All users except local administrators”.
4) Maybe reboot
This should solve the problem (it did for me)..
/Anders
About the â€The installation source for this product is not available†problem – if you are you using Windows Server 2003:
If you extract the .exe file and see the properties on the .msp file under “Digital Signatures” you will see that the signature/certificate is not valid. (ScottGu: I presume this is a bug?).
To â€fix†(ignore) this:
1) Open local security setting: Start -> Programs -> Administrative Tools -> Local Security Policy.
2) Click on “Software Restriction Policies” and if it shows “No Software Restriction Policies Defined” then insert a new (right click the left pane node).
3) 2 x click on the “Enforcement” entry and under “Apply software restriction policies to the following users:” section change to “All users except local administrators”.
4) Maybe reboot
This should solve the problem (it did for me)..
/Anders