.Net 4.0 install fails sporadically with "Generic trust" failure - by Roman П

Status : 

  Not Reproducible<br /><br />
		The product team could not reproduce this item with the description and steps provided.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 652816 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 3/22/2011 7:56:27 AM
Access Restriction Public


Installing .Net 4.0 as part of VS2010 deployment to x64-bit Windows7 is failing sporadically with "Signature verification for file SetupUtility.exe  failed" error in log. 
Install succeeds sometimes if retried (using the same exact source file), however, it is not clear what exactly gets changed on a system.   Behavior is easily reproduced with antivirus disabled on a system with UAC off.

The issue is blocking reliable admin deployment of VS2010 installations.

Is there a way to disable signature verification via command line switches?
Is there a known procedure or a hotfix to fix this type of failures?

Sign in to post a comment.
Posted by GarryWroe on 5/23/2012 at 5:59 AM
Many thanks, Matt. I've been experiencing 'generic trust failure' issues for months on my XP system. Your solution has resolved those issues and I've now installed a number of previously problematic net framework updates.

Thanks again.

Posted by Matt Cofer on 8/2/2011 at 1:46 PM
I was able to resolve the generic trust issue related to a different install package from Microsoft by running the following commands as described @ http://support.microsoft.com/kb/956702. You may want to review the website and consider trying the fix it describes. Note: This fixed the issue on a Windows XP machine but did not fix it on a Windows 7 machine. I could not determine what the difference was nor have I been able to fix the issue on the Windows 7 machine at all.

Click Start, click Run, type cmd, and then click OK.
At the command prompt, type regsvr32 Softpub.dll /s, and then press ENTER.
At the command prompt, type regsvr32 Wintrust.dll /s, and then press ENTER.
At the command prompt, type regsvr32 Initpki.dll /s, and then press ENTER.
At the command prompt, type regsvr32 Mssip32.dll /s, and then press ENTER.
Posted by Microsoft on 3/24/2011 at 2:49 AM
Thanks again for your feedback.
Could you please try the workaround in the forums (http://social.msdn.microsoft.com/Forums/en/netfxsetup/thread/2107384c-e030-48d9-9e4d-02537bf3b755)?
Posted by Roman П on 3/23/2011 at 10:22 AM
I believe the issue is similar to http://support.microsoft.com/kb/944752
Posted by Microsoft on 3/22/2011 at 9:45 PM
Thanks for reporting the issue.
Could you please upload a setup log file to help us investigate the issue?
You can get the log files with the following steps:
1) Download collect.exe from the link below. http://go.microsoft.com/?LinkId=8967043
2) You may choose to save the tool for later use, or to run directly.
3) The utility creates a compressed cabinet of all the VS and .NET logs to %TEMP%\vslogs.cab.

You can get more details about how to get the log files here:

Posted by Microsoft on 3/22/2011 at 8:13 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)