none
.Net Framework 4 error: Generic trust failure RRS feed

  • Question

  • I'm having the same issue as a lot of other people.  I've downloaded the standalone installed for the .Net Framework 4 (dotNetFx40_Full_x86_x64.exe) and tried installing it both by simply double-clicking the executable and right clicking > Run as Administrator.  Neither are working, they both give the same error, "Generic trust failure."  I've gathered my logs and uploaded them to my personal site, they are located here:

    http://infectionist.com/misc/vslogs.cab

    I guess the installer chose my H: drive as the file xtraction drive, since it's the largest fixed drive (well, the most free space.)  Here are a few lines from dd_dotNetFx40_Full_x86_x64_decompression_log.txt:

    [6/25/2010, 10:24:15] Drive 'H:\' has been selected as the largest fixed drive
    [6/25/2010, 10:24:15] Directory 'H:\d1f8e660ffe46cc42cb6\' has been selected for file extraction
    [6/25/2010, 10:24:15] Extracting files to: H:\d1f8e660ffe46cc42cb6\
    [6/25/2010, 10:24:23] Extraction took 8.440 seconds
    [6/25/2010, 10:24:23] Executing command line: 'H:\d1f8e660ffe46cc42cb6\\Setup.exe  /x86 /x64'

    Then I took a look in the .net installer-generated HTML log file, and the lines of interest are at the very bottom:

    [6/25/2010, 10:21:48]Verifying Digital Signatures: H:\844a21f445080c9a4dc33238fb\SetupUtility.exe
     [6/25/2010, 10:21:48] H:\844a21f445080c9a4dc33238fb\SetupUtility.exe: Verifying signature for SetupUtility.exe...
     [6/25/2010, 10:21:48]Possible transient lock. WinVerifyTrust failed with error: 2148204800
     [6/25/2010, 10:21:48]Possible transient lock. WinVerifyTrust failed with error: 2148204800
     [6/25/2010, 10:21:48]H:\844a21f445080c9a4dc33238fb\SetupUtility.exe - Signature verification for file SetupUtility.exe (H:\844a21f445080c9a4dc33238fb\SetupUtility.exe) failed with error 0x800b0100 (No signature was present in the subject.)
     [6/25/2010, 10:21:48] H:\844a21f445080c9a4dc33238fb\SetupUtility.exe Signature could not be verified for SetupUtility.exe
    [6/25/2010, 10:21:48]No FileHash provided. Cannot perform FileHash verification for SetupUtility.exe
    [6/25/2010, 10:21:48]File SetupUtility.exe (H:\844a21f445080c9a4dc33238fb\SetupUtility.exe), failed authentication. (Error = -2146762496). It is recommended that you delete this file and retry setup again.
    [6/25/2010, 10:21:48]Failed to verify and authenticate the file -H:\844a21f445080c9a4dc33238fb\SetupUtility.exe
    [6/25/2010, 10:21:48]Please delete the file, H:\844a21f445080c9a4dc33238fb\SetupUtility.exe and run the package again
    

    I notice a few things.  First, "Possible transient lock."  What does that mean?  I disabled my antivirus (I use AVG 9 Free) and tried again with the exact same result.

    Another thing, "No filehash provided."  I'm not 100% sure what this means, but I know that if I right click the SetupUtility.exe and click properties, go to the Digital Signature tab, there is a Microsoft signature there.

    Also, on the second line from the bottom, the path is shown as "-H:\844a21f445080c9a4dc33238fb\SetupUtility.exe", why would it put a minus sign in front of the path?

    Finally, last line, it tells me to delete the file and try the installation again.  Knowing that that was a stupid request, but wanting to get the issue resolved, I tried a few things.  First I tried simply renaming it to SetupUtility_.exe, then I tried replacing it with the SetupUtility.exe that I had gotten from an extract of the package, and finally I tried actually deleting it.  None of these things worked, it still tried to verify it, it still failed with the same errors, even though the file was not there.

     

    Funny thing is, I had this installed and I accidentally uninstalled it when I was uninstalling Silverlight 4 stuff, now I can't get it back.

    Oh, I also tried the .Net Framework Cleanup Tool here:

    http://blogs.msdn.com/b/astebner/archive/2008/08/28/8904493.aspx

    And it successfully removed whatever was left of the .Net Framework 4.  This is getting really really frustrating.  Without this I can't debug in Visual C# 2008 (for some reason) and I can't do anything in Visual C# 2010.  I need those programs to work.

    Friday, June 25, 2010 4:04 PM

Answers

  • Finally resolved! The root certificates were corrupted. For Windows 7, x64: 

     

    1.    Remove the Microsoft Root Certificates from the Certificate Manager.

    a.    RUN certmgr.msc.

    b.    In Certificate Manger, find certificates from Microsoft and delete them (all except the ones from 1999/2002). You do this by right-clicking and deleting.

     

    2.    Run the root update tool provided by Microsoft (rootsupd.exe).

     

    3.    Disable firewall and real-time virus scan (precaution).

     

    4.    Remove old files related to the previous attempts from the User's AppData\Local\Temp folder.

     

    5.    Launch the update from Windows Update.

    • Proposed as answer by Sophie2011 Tuesday, June 29, 2010 12:24 PM
    • Marked as answer by YiChun Chen Friday, July 2, 2010 3:49 AM
    Tuesday, June 29, 2010 12:23 PM
  • Hi HaLo2FrEeEk,

    Thank you for your post.

    Some clarification with you:
    What's is your H drive? External drive?

    I've checked the log files that you posted and found the following error message:

    [6/25/2010, 10:24:38]File SetupUtility.exe (H:\d1f8e660ffe46cc42cb6\SetupUtility.exe), failed authentication. (Error = -2146762496). It is recommended that you delete this file and retry setup again.
    [6/25/2010, 10:24:38]Failed to verify and authenticate the file -H:\d1f8e660ffe46cc42cb6\SetupUtility.exe
    [6/25/2010, 10:24:38]Please delete the file, H:\d1f8e660ffe46cc42cb6\SetupUtility.exe and run the package again

    Based on the error message, it looks like that your issue is related to the signature verification for file SetupUtility.exe.

    Could you please help me to try the following steps one by one to install .NET Framework 4.0?

    - Check whether you can find the file "C:\640b7523c9e5a6956857b54c50\SetupUtility.exe".

      Please also check the hidden files and folders via the following steps:
      1) Click Start, and open Computer.
      2) On the Tool bar, click Organize and choose Folder and Search Options.
      3) Click the View tab, and check to select the Show hidden files and folders option, and click OK.

      If you can find it, please completely remove it.

    - If H drive is the external drive, please remove it from your machine.

    - Download .NET Framework 4.0 Standalone installer
      Note: You can try some download manager software to help downloading.

    - Run the installer to install .NET 4.0 with Administrator Privilege
      Note: Right-click the installer >> "Run as Administrator"

    Hope this helps! If you have any concern, please feel free to let me know.

    Best regards,
    Yichun Chen


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.
    • Marked as answer by YiChun Chen Friday, July 2, 2010 3:49 AM
    Monday, June 28, 2010 12:20 PM

All replies

  • I have exactly the same problem with the update of KB982670. SetupUtility.exe cannot even be extracted when i use the standalone installation. What should i do? Can anyone help?
    Saturday, June 26, 2010 9:31 AM
  • Hi HaLo2FrEeEk,

    Thank you for your post.

    Some clarification with you:
    What's is your H drive? External drive?

    I've checked the log files that you posted and found the following error message:

    [6/25/2010, 10:24:38]File SetupUtility.exe (H:\d1f8e660ffe46cc42cb6\SetupUtility.exe), failed authentication. (Error = -2146762496). It is recommended that you delete this file and retry setup again.
    [6/25/2010, 10:24:38]Failed to verify and authenticate the file -H:\d1f8e660ffe46cc42cb6\SetupUtility.exe
    [6/25/2010, 10:24:38]Please delete the file, H:\d1f8e660ffe46cc42cb6\SetupUtility.exe and run the package again

    Based on the error message, it looks like that your issue is related to the signature verification for file SetupUtility.exe.

    Could you please help me to try the following steps one by one to install .NET Framework 4.0?

    - Check whether you can find the file "C:\640b7523c9e5a6956857b54c50\SetupUtility.exe".

      Please also check the hidden files and folders via the following steps:
      1) Click Start, and open Computer.
      2) On the Tool bar, click Organize and choose Folder and Search Options.
      3) Click the View tab, and check to select the Show hidden files and folders option, and click OK.

      If you can find it, please completely remove it.

    - If H drive is the external drive, please remove it from your machine.

    - Download .NET Framework 4.0 Standalone installer
      Note: You can try some download manager software to help downloading.

    - Run the installer to install .NET 4.0 with Administrator Privilege
      Note: Right-click the installer >> "Run as Administrator"

    Hope this helps! If you have any concern, please feel free to let me know.

    Best regards,
    Yichun Chen


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.
    • Marked as answer by YiChun Chen Friday, July 2, 2010 3:49 AM
    Monday, June 28, 2010 12:20 PM
  • I have the same issue both from Windows Update and the Standalone installer (running as Administrator). I am able to initially locate the SetupUtility.exe in the temporary extraction folder but the installer has already launched at that point. I have checked 'run as administrator' and added the digital certificate attached to the SetupUtility.exe file to the Trusted Root Authority and the install still fails. Also, once the installer has run once, the temporary extraction folder is removed preventing retries. I have also disabled McAfee Total Protection Firewall and Realtime Virus Scan. Please advise.
    Monday, June 28, 2010 8:25 PM
  • Finally resolved! The root certificates were corrupted. For Windows 7, x64: 

     

    1.    Remove the Microsoft Root Certificates from the Certificate Manager.

    a.    RUN certmgr.msc.

    b.    In Certificate Manger, find certificates from Microsoft and delete them (all except the ones from 1999/2002). You do this by right-clicking and deleting.

     

    2.    Run the root update tool provided by Microsoft (rootsupd.exe).

     

    3.    Disable firewall and real-time virus scan (precaution).

     

    4.    Remove old files related to the previous attempts from the User's AppData\Local\Temp folder.

     

    5.    Launch the update from Windows Update.

    • Proposed as answer by Sophie2011 Tuesday, June 29, 2010 12:24 PM
    • Marked as answer by YiChun Chen Friday, July 2, 2010 3:49 AM
    Tuesday, June 29, 2010 12:23 PM
  • I've got the same problem on Windows 7 x64. Tried to install it several times and also tried the advice from Sophie2011.

    Always get the error: Generic trust failure 800B010B

     

    Wednesday, July 7, 2010 1:10 AM
  • I've got the same problem on Windows 7 x64. Tried to install it several times and also tried the advice from Sophie2011.

    Always get the error: Generic trust failure 800B010B

     

    hi, i had this problem and none of the above helped me - i finally fixed it by running System File Checker (sfc /scannow) via the command prompt and then restarting

    see this url for details: http://pcsupport.about.com/od/toolsofthetrade/ht/sfc-scannow.htm

    Sunday, September 19, 2010 10:17 AM
  • I ran into same issue with installing on windows 2008 server on a server that has no outbound connectivity to the internet.  The only way to resolve this was to do the following:

     

    1. copy dotNetFx40_Full_x86_x64.exe to folder of your choice
    2. open cmd prompt and cd to folder
    3. at prompt type >dotNetFx40_Full_x86_x64.exe /x
    4. select netfx_Core_x64.msi and open properties on the file
    5. Click on the Digital Signatures tab
    6. View the Certificates and copy each one out and install to local certstore
    7. you will need to get the CRL for these certs from a box that has network connectivity the crls you will need are:  http://crl.microsoft.com/pki/crl/products/CSPCA.crl and http://crl.microsoft.com/pki/crl/products/tspca.crl  These files need to be brought to the server and installed.
    8. You'll also need to install the Microsoft Time-Stamp Service Cert and cert chain into local store
    9. Once all this is done you can run setup.exe /x86 /x64

    The basic issue here is that my box could not go out and get the updated certs and CRLS.

    Hope this helps.

    • Proposed as answer by rreilly70 Wednesday, September 22, 2010 4:08 PM
    Wednesday, September 22, 2010 4:05 PM
  • Hi Sophie / Microsoft

    What is the link for the LATEST root certificate update tool for Windows Server 2008 R2 64-bit?

    Thanks

    Monday, January 9, 2012 12:51 AM
  • This fixed it. I have been looking and searching for the answer for over a year. 'rootupd.exe' fixed my issue.

    The problem - (Generic Trust Fail - SetupUtil.exe) .Net 4.0 install

    I went to the website, vaildated, downloaded and ran. Nothing poped up, nothing verified that it ran. I tryed the .net install again, and it took!

    Thank you SO much.

    Sunday, May 6, 2012 7:05 PM
  • Thanks for this post. Worked for me and I tried many different "fixes" out on the internet. I would say the the crls after the installed certs was the fix for my isolated network.
    Wednesday, October 10, 2012 2:52 PM
  • the below worked for me from another site, not my fix though just wanted to share:

    Posted by Matt Cofer on 02/08/2011 at 13:46
    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.

    Thursday, July 9, 2015 2:04 PM