none
Repair .NET 4 Generic trust failure RRS feed

  • Question

  • I am getting this error when I try to repair the .NET 4 on a 2008 R2 server

    This is the installed version of .NET

    4.0.30319

    Also, this is the error log:

    OS Version = 6.1.7600, Platform 2
    OS Description = Win2K8R2 - x64 Standard Edition
    CommandLine = C:\b332c519427d64fb492e822d\\Setup.exe /x86 /x64
    TimeZone = W. Europe Standard Time
    Initial LCID = 1044
    Using Simultaneous Download and Install mechanism
    Operation: Repairing
    Package Name = Microsoft .NET Framework 4 Setup
    Package Version = 4.0.30319
    User Experience Data Collection Policy: Disabled
    Number of applicable items: 6
    C:\b332c519427d64fb492e822d\Windows6.1-KB958488-v6001-x64.msu - Signature verification for file Windows6.1-KB958488-v6001-x64.msu
    (C:\b332c519427d64fb492e822d\Windows6.1-KB958488-v6001-x64.msu) failed with error 0x80096005 (The timestamp signature and/or certificate could not be verified or
    is malformed.)
    No FileHash provided. Cannot perform FileHash verification for Windows6.1-KB958488-v6001-x64.msu
    File Windows6.1-KB958488-v6001-x64.msu (C:\b332c519427d64fb492e822d\Windows6.1-KB958488-v6001-x64.msu), failed authentication. (Error = -2146869243).
    It is recommended that you delete this file and retry setup again.
    Final Result: Installation failed with error code: (0x800B010B), "Generic trust failure. " (Elapsed time: 0 00:00:04).

    Thursday, March 22, 2012 12:11 PM

Answers

  • Sorry to reiterate, but it appears:

    "If all these things still fail, you are looking at a Windows Installer corruption on your server, IMO, and should consider OS repair/reinstall."

    Friday, March 23, 2012 5:03 PM

All replies

  • You can try these fixes:

    http://social.msdn.microsoft.com/Forums/en-US/netfxsetup/thread/25820d13-b96b-40c6-ba69-efe02ecaf652 

    http://social.msdn.microsoft.com/Forums/en-US/netfxsetup/thread/fd50019d-320e-455a-8f39-7415207a8d27 

    I suggest you remove 4.0 using Add/Remove...

    If that fails, use this tool:

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

    Then, reinstall using these steps:

    Please follow these instructions exactly:

    1. Download a fresh copy of the standalone installer for .NET Framework 4.0:

    http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=17718

    2. Before running the installer, apply irarab's fix as follows:

    "I went to "C:\Windows\Microsoft.NET" there is a directory called "assembly".

    I looked in the directory and found some subdirectories with lots of old dot net 4 files. I renamed the directory assembly2 and tried to install Dot Net 4 and it worked!!!!

    (You can't delete the assembly directory unless you take ownership of it but you can rename it.)"

    Also, clear your %temp% directory and disable your AV software.

    The %temp% directory is a reference to the Temp folder associated with the current user. To clear it, do the following:

    Sign on to your system with the Administrator user account you will use to run the installer. Click the Start Orb and type %temp% in the search box. The search results will show the Temp folder you want. Click on the Temp folder to open it in Windows Explorer, then delete the entire contents.

    3. Run the standalone installer from step 1 As Administrator.

    Note: Just using an administrator account is NOT enough. To activate full privileges, you must right-click the installer, then select Run as administrator.

    If the install fails, provide complete install logs as follows:

    Please collect your install logs with this:

    http://www.microsoft.com/downloads/details.aspx?FamilyID=E0DA314F-6216-4A18-BC6B-7D29CF83AF20&displaylang=e&displaylang=en

    After you run Collect.exe, you'll find vslogs.cab in your %temp% directory. Please upload vslogs.cab to a public site, like SkyDrive, and post the link here.

    Thursday, March 22, 2012 2:36 PM
  • I got this error at step nr 3 in your answer


    This is the error summary message from the log:

    OS Version = 6.1.7600, Platform 2
    OS Description = Win2K8R2 - x64 Standard Edition
    CommandLine = C:\e94e750c8a7a0015d122\\Setup.exe /x86 /x64
    TimeZone = W. Europe Standard Time
    Initial LCID = 1044
    Using Simultaneous Download and Install mechanism
    Operation: Installing
    Package Name = Microsoft .NET Framework 4 Setup
    Package Version = 4.0.30319
    User Experience Data Collection Policy: Disabled
    Number of applicable items: 11
    C:\e94e750c8a7a0015d122\SetupUtility.exe - Signature verification for file
    SetupUtility.exe (C:\e94e750c8a7a0015d122\SetupUtility.exe) failed with error
    0x80096005 (The timestamp signature and/or certificate could not be verified or
    is malformed.)
    No FileHash provided. Cannot perform FileHash verification for SetupUtility.exe
    File SetupUtility.exe (C:\e94e750c8a7a0015d122\SetupUtility.exe), failed
    authentication. (Error = -2146869243). It is recommended that you delete this
    file and retry setup again.
    Final Result: Installation failed with error code: (0x800B010B), "Generic trust
    failure. " (Elapsed time: 0 00:00:07).

    The vslogs.cab file is accessable through this link:
    https://skydrive.live.com/redir.aspx?cid=eceae117f919ffdb&resid=ECEAE117F919FFDB!450&parid=ECEAE117F919FFDB!449&authkey=!ABihKUmuw9GK2ig

    What can I do next? This is an administration server, and of course, it needs .NET


    Freddy

    Thursday, March 22, 2012 6:47 PM
  • From the log:

    "Failed to verify and authenticate the file -C:\e94e750c8a7a0015d122\SetupUtility.exe
     Please delete the file, C:\e94e750c8a7a0015d122\SetupUtility.exe and run the package again"

    Did you try this? To be honest, I suspect you'll get the same result, which looks like a corrupted download of the .NET 4.0 installer.

    Did you read/try YiChun Chen's suggestion of using a different browser or different system/connection to download the installer (from my second link in previous response)?

    If all these things still fail, you are looking at a Windows Installer corruption on your server, IMO, and should consider OS repair/reinstall.

    Thursday, March 22, 2012 9:41 PM
  • I have now done both.

    1. Downloaded with Opera, not IE

    2. Execute the dotNetFx40_Full_x86_x64.exe with administrator privileges

    3. Got the same error: "Failed to verify and authenticate the file -C:\e94e750c8a7a0015d122\SetupUtility.exe"

    4. Unpacked the exe file with Universal Extractor to a temp folder

    5. Ran the .exe file again from cmd.exe with administrator privileges, with the same error.

    6. Deleted the SetupUtility.exe and ran the setup.exe file with /64 switch from the unpacked temporary folder and admin privileges.

    7. Got the following error:

    In other words, the suggestion from Microsoft corrumpts the installation.

    What can I do next?

    Friday, March 23, 2012 1:52 PM
  • Sorry to reiterate, but it appears:

    "If all these things still fail, you are looking at a Windows Installer corruption on your server, IMO, and should consider OS repair/reinstall."

    Friday, March 23, 2012 5:03 PM
  • Ladies and Gentlemen,

    I have discovered a solution that works for my systems and servers.

    Go into regedit, and navigate to:

    HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\WinTrust\Trust Providers\Software Publishing

    Find the key for State

    Make a backup of your Registry! Or, at the very least, remember the value that is already in this key

    Modify this key to Decimal 147360 (Hex is 0x00023fa0)

    Now try to install your patch(es). Once completed, restore your registry, or modify the key value back to the original value.

    • Proposed as answer by Beaker609 Thursday, June 14, 2012 10:34 PM
    Thursday, April 12, 2012 2:09 PM
  • Thanks Chief.  This was the only thing that worked for me.  I've tried everything.

    Jack

    Monday, July 16, 2012 10:03 PM
  • Same here - this was the only thing that worked for me & I tried all the tricks under the book including using administrator priviledges, creating an explict admin user, updating my root certificates and more!!!

    Very poor support on this though. This was a brand new install for me (2 servers infact) that had not yet been commisioned as LIVE servers and they came up with these error messages. I had 3 new servers, identical in every way, same domain, permissions, poilicies etc, one work and two others failed. It almost reminds me of the days back in Africa,  when to get a server to work you had to stand in the rain and throw a stone across your left shoulder while counting to 10! It simply does not make any sense why the install fails.

    Does anyone know why this solution worked by the way?

    After 4 hours of trying everything else I am interested in this one.

    Tuesday, August 7, 2012 11:03 PM