none
.NET Framework fails to install (applies to 4.0, 4.5, and all Updates) RRS feed

  • 質問

  • Hi,

    I have trouble isntalling any .NET Framework on my Windows 7 x64 machine, I keep getting the following logfile, what might cause this?

    OS Version = 6.1.7601, Platform 2, Service Pack 1
    OS Description = Windows 7 - x64 Ultimate Edition Service Pack 1
    CommandLine = C:\09b8fe547577883fe82c\\Setup.exe /x86 /x64
    TimeZone = Mitteleuropäische Zeit
    Initial LCID = 1031
    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: AlwaysUploaded
    Number of applicable items: 11
    Exe (C:\09b8fe547577883fe82c\SetupUtility.exe) succeeded.
    Exe Log File: dd_SetupUtility.txt
    ServiceControl operation succeeded!
    ServiceControl operation succeeded!
    Exe (C:\09b8fe547577883fe82c\Windows6.1-KB958488-v6001-x64.msu) failed with 0x240006 - (null).
    Exe (C:\09b8fe547577883fe82c\SetupUtility.exe) succeeded.
    Exe Log File: dd_SetupUtility.txt
    MSI (C:\09b8fe547577883fe82c\netfx_Core_x64.msi) Installation failed. Msi Log: Microsoft .NET Framework 4 Setup_20150116_161918591-MSI_netfx_Core_x64.msi.txt
    Final Result: Installation failed with error code: (0x80070643), "Schwerwiegender Fehler bei der Installation. " (Elapsed time: 0 00:00:11).

    I have pasted a LOGfile from the MSI file, can you please take a look?

    https://paste.ee/p/zXSWH

    
    


    2015年1月16日 15:20

すべての返信

  • Hi,

    probier mal bitte die im MS KB Artikel vorgeschlagenen Lösungswege.

      https://support.microsoft.com/kb/976982


    Gruß, Stefan
    Microsoft MVP - Visual Developer ASP/ASP.NET
    http://www.asp-solutions.de/ - Consulting, Development
    http://www.aspnetzone.de/ - ASP.NET Zone, die ASP.NET Community

    2015年1月16日 15:46
  • Hi,

    I tried these steps first, completely unintalled all .NET frameworks, but I can only Install Framework 1.1, 3.4 doesn't start, and 4.0 and 4.5 give me still the same error.

    When I look at my log:

    Exe (C:\b71c714f818e4d58e879de830c6584cc\SetupUtility.exe) succeeded.
    Exe Log File: dd_SetupUtility.txt
    Action complete
    Returning IDOK. INSTALLMESSAGE_ERROR [Überlappender E/A-Vorgang wird verarbeitet. ]
    Returning IDOK. INSTALLMESSAGE_ERROR [Überlappender E/A-Vorgang wird verarbeitet. ]
    MSI (C:\b71c714f818e4d58e879de830c6584cc\netfx_Core_x64.msi) Installation failed. Msi Log: Microsoft .NET Framework 4 Setup_20150116_163718319-MSI_netfx_Core_x64.msi.txt
    PerformOperation returned 1603 (translates to HRESULT = 0x80070643)
    Action complete
    OnFailureBehavior for this item is to Rollback.

    Action: Performing actions on all Items

    And the details of my paste:

    https://paste.ee/p/zXSWH

    • MSI (s) (78!78) [16:11:30:749]: SECUREREPAIR: Failed to CreateContentHash of the file: 1033\SetupResources.dll: for computing its hash. Error: 997
    • MSI (s) (78!78) [16:11:30:750]: SECREPAIR: Failed to create hash for the install source files
    • MSI (s) (78!78) [16:11:30:750]: SECUREREPAIR: SecureRepair Failed. Error code: 3e5F7CE34B8
    • Aktion gestartet um 16:11:30: CA_NgenUpdateHighestVersion_I_RB_amd64.3643236F_FC70_11D3_A536_0090278A1BB8.
    • MSI (s) (78!78) [16:11:30:753]:

    I found a lot of information saying this may be caused by

    KB2918614

    so I uninstalled this specific update, but the problem persists.

    Do you have any more ideas?

    2015年1月16日 16:02
  • Hello Jackie_de,

    According to this blog:

    http://blogs.msdn.com/b/vsnetsetup/archive/2014/10/27/error-997-overlapped-i-o-operation-is-in-progress-kb2918614-breaks-windows-installer-service.aspx

    The solution is to apply this update:

    http://support.microsoft.com/kb/3000988

    Have you tried the solution yet?

    I also find the following from your log:

    • MSI (s) (78!78) [16:11:30:749]: SECREPAIR: Crypt Provider not initialized. Error:997
    • MSI (s) (78!78) [16:11:30:749]: SECUREREPAIR: Failed to CreateContentHash of the file: 1033\SetupResources.dll: for computing its hash. Error: 997
    • MSI (s) (78!78) [16:11:30:750]: SECREPAIR: Failed to create hash for the install source files
    • MSI (s) (78!78) [16:11:30:750]: SECUREREPAIR: SecureRepair Failed. Error code: 3e5F7CE34B8
    • Aktion gestartet um 16:11:30: CA_NgenUpdateHighestVersion_I_RB_amd64.3643236F_FC70_11D3_A536_0090278A1BB8.

    The problem seems pending on Crypt Provider which may related to temporary profile.

    Best regards,



    Barry
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    2015年1月20日 8:54
    モデレータ
  • Hi Barry,

    yes, I have tried both, uninstalling KB 2918614, and also installing it again and applying patch 3000988, since this is the only information one can find concerning Securerepair issues.Strangely, none of these fix my problem. Besides, I am not using temporary userprofiles, so I am wondering if it has actually to with this problem.

    This is so strange, any other ideas what I could try?

    2015年1月20日 13:55
  • Jackie,

    I've been struggling with this same problem and what (probably temporarily) fixed it was to follow these instructions to whitelist the installer for .net (found at http://answers.microsoft.com/en-us/windows/forum/windows8_1-windows_install/kb2918614-breaks-windows-installer-service/3d75a1c2-114a-4241-a527-35b536edc158?page=7):

    Workaround 2: Whitelisting.

    Only if you trust the application that it is always digitally signed and doesn't contain anything malicious(even in the future).

    Step 1: Enable Whitelisting

    Under Key “HKLM\SOFTWARE\Policies\Microsoft\Windows\Installer”, create a DWORD: “SecureRepairPolicy” and set its Value to 2.

    Step 2: Add the application to the whitelist

    Create a new key “SecureRepairWhitelist” under "HKLM\SOFTWARE\Policies\Microsoft\Windows\Installer” and create StringValues with the product codes(Including flower brackets {}) of the product.

    -------

    In my case, I was trying to install .net 4.5.2 using the full installer (NDP452-KB2901907-x86-x64-AllOS-ENU.exe). The product ID is {26784146-6E05-3FF9-9335-786C7C0FB5BE}. After following the instructions to whitelist this product ID, the install ran to completion. BTW, I did this with KB 2918614 uninstalled.

    I know this doesn't fix the problem, but it should allow you to install .net and get on with your day.

    • 回答としてマーク Barry WangModerator 2015年1月27日 10:03
    • 回答としてマークされていない Jackie_de 2015年1月27日 16:23
    2015年1月20日 18:36
  • Thanks a lot for that workaround JohnL, it actually worked the way you described. So I was able to install this update  which is good news :)

    But two questions do remain:

    1.) (small one): how do you figure out the "product ID" if that happens with another product? I.e., how do you know this specific piece of installer has the ID {26784146-6E05-3FF9-9335-786C7C0FB5BE}?

    2.) (big one, important for me): why is this necessary, why do so many MSI setups work, but .Net installer does not? Why does SecRepair not work on my machine, regardless of the state of KB 2918614? Did Microsoft actually do a bad job with this update and break more than they actually fixed? Is there any explanation for the problem I am experiencing?

    Thanks for your support, I really do appreciate it :)

    2015年1月20日 19:51
  • Jackie,

    As far as question 1, I found that info in the txt log file that was created when the software failed to install and gave me the error. Here's a section of the log file (Microsoft .NET Framework 4.5.2 Setup_20150120_095339708-MSI_netfx_Full_GDR_x64.msi.txt):

    MSI (s) (00!C8) [09:53:59:708]: PROPERTY CHANGE: Adding SourcedirProduct property. Its value is '{26784146-6E05-3FF9-9335-786C7C0FB5BE}'.
    MSI (s) (00!C8) [09:53:59:708]: SOURCEDIR ==> C:\6558ee80bcc3df47dbf7fa989bb0\
    MSI (s) (00!C8) [09:53:59:708]: SOURCEDIR product ==> {26784146-6E05-3FF9-9335-786C7C0FB5BE}
    MSI (s) (00!C8) [09:53:59:739]: SECREPAIR: CryptAcquireContext: Could not create the default key container
    MSI (s) (00!C8) [09:53:59:739]: Determining source type
    MSI (s) (00!C8) [09:53:59:739]: Source type from package 'netfx_Full_GDR_x64.msi': 0
    MSI (s) (00!C8) [09:53:59:739]: SECREPAIR: Hash Database: C:\Windows\Installer\SourceHash{26784146-6E05-3FF9-9335-786C7C0FB5BE}
    MSI (s) (00!C8) [09:53:59:739]: SECREPAIR: SourceHash database file already exists. Deleting it.
    MSI (s) (00!C8) [09:53:59:754]: Note: 1: 2262 2: SourceHash 3: -2147287038
    MSI (s) (00!C8) [09:53:59:770]: SECREPAIR: New Hash Database creation complete.
    MSI (s) (00!C8) [09:53:59:770]: SECREPAIR: Crypt Provider not initialized. Error:0
    MSI (s) (00!C8) [09:53:59:770]: SECREPAIR: Crypt Provider not initialized. Error:0
    MSI (s) (00!C8) [09:53:59:770]: SECREPAIR: Crypt Provider not initialized. Error:0
    MSI (s) (00!C8) [09:53:59:770]: SECREPAIR: Crypt Provider not initialized. Error:0
    MSI (s) (00!C8) [09:53:59:770]: SECREPAIR: Crypt Provider not initialized. Error:0
    MSI (s) (00!C8) [09:53:59:770]: SECREPAIR: Crypt Provider not initialized. Error:0
    MSI (s) (00!C8) [09:53:59:770]: SECREPAIR: Crypt Provider not initialized. Error:997
    MSI (s) (00!C8) [09:53:59:770]: SECUREREPAIR: Failed to CreateContentHash of the file: 1030\SetupResources.dll: for computing its hash. Error: 997
    MSI (s) (00!C8) [09:53:59:770]: SECREPAIR: Failed to create hash for the install source files
    MSI (s) (00!C8) [09:53:59:770]: SECUREREPAIR: SecureRepair Failed. Error code: 3e5EFB634B8

    The value is in the third line that is in italics.

    As far as your second question, I have no idea. The fixes I read seemed to tell me that removing 2918614 would stop the installer from checking the hash and that is obviously not true. The other thing that is odd is that I have run the 4.5.2 update on four machines and only one failed. I have no way of knowing what is different about the one machine other than it has many more programs on it. The versions of Windows 7 are virtually identical and the same updates have been installed on all of them, including 2918614. Hopefully someone here has a better answer to this question.

    I'm glad I was able to help you as far as I did. I was just about to give up when I discovered the fix.

    • 回答としてマーク Barry WangModerator 2015年1月27日 10:04
    • 回答としてマークされていない Jackie_de 2015年1月27日 16:24
    2015年1月21日 2:01
  • Just in case somebody is interested, I am facing exactly the same problem, but only with .NET Framework 4.5.2 update suggested by Windows Update. Error 997, and whitelisting actually did the job for me, but the question is:

    - Why does KB3000988 (hotfix for KB2918614) not fix this?

    - Why does uninstalling KB2918614 not fix this?

    - Does this, at all, have anything to do with temporary userprofiles? As far as I understand, none of us, neither me nor the original poster do use temporary userprofiles.

    So I guess there are more bugs in the SECREPAIR / Cryptprovider changes made in the last few months. Can anybody who is more familiar with these topics (I am not unfortunately) explain what is actually going on here, and why this whole process fails?

    Since .NET framework 4.5 and 4.5.1 did install correctly when they were released, I tried the following:

    - made a complete backup of my whole system partition

    - uninstalled .NET 4.5 and 4.5.1

    - and bingo, now REINSTALLING fails with the same error code.

    So, to sum up:

    - installation did work a few months ago, but doesn't now

    - so some update or some system change broke that whole process.

    Btw, very poor performance by Microsoft, haven't ever had so many problems with Windows updates than in the last few months :(


    • 編集済み Erik78 2015年1月23日 7:21
    • 回答としてマーク Barry WangModerator 2015年1月27日 10:04
    • 回答としてマークされていない Jackie_de 2015年1月27日 16:24
    2015年1月23日 7:21
  • I wonder why somebody marked several posts in this thread as "Answer", maybe to satisfy some statistics, but although there are many helpful attempts here, none really answers what is actually going on, and all of them are only workarounds that disguise the main problem by whitelisting (and therefor not performing Secrepair at all), but the next software will have exactly the same issues.

    If at all there is something that could be described as an answer, it is the following (thanks to a thread over there at Stackoverflow), it is the fact that obviously, a third "Microsoft Update" (KB3008627) is somehow involved in this whole fiasco.

    So in fact, you have to uninstall three Windows security updates to make the whole process work correctly again:

    KB2918614, KB3000988 and KB3008627 need to be uninstalled.

    This worked for me, of course it does not at all explain why these three updates actually cause the behaviour that we see, but in my eyes, it is the best workaround, until Microsoft gets their Updates tested and working properly!

    2015年1月27日 16:31
  • Another me too post.

    Same errors as Jackie_de & Erik78 attempting to install .NET 4.5.2 on Win7x64. KB3000988 didnt help.  Whitelisting was the workaround, sadly. 

    2015年1月29日 22:35
  • M$ fail.

    rename C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18 to C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18.bak

    2016年3月22日 6:23
  • M$ fail.

    rename C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18 to C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18.bak


    I can't believe this easy fix is actually the only thing that helped me. Thank you so much Sarah Conner, I struggled with this problem for a whole year at least.
    • 回答の候補に設定 gjmartinez 2017年7月25日 22:03
    2016年4月2日 11:27
  • this solution also worked for me, thanks a lot.
    2017年7月25日 22:04