none
Unable to install .Net Framework 4, 4.5.2, or 4.6.1 RRS feed

  • Question

  • Hello,

    I've been trying and failing to install any version of the .NET Framework 4.x on Windows 7 Pro SP1 (with all updates installed).  I really need just 4.5.2, but it appears none of the version 4 installers work.

    If I try to install 4.5.2 or 4.6.1 or the Windows 4 client profile via Windows Update, it fails with error code 641.  The System event log shows error 0x80070643 for the failed install.  I am able to successfully install other Windows Updates.

    If I try the web installer for 4 or the stand-alone installers for 4.5.x or 4.6.x, they all fail saying the generic message of the Windows Installer Service could not be accessed.  I can install other applications that use the Windows Installer without issue.  The log for the installer doesn't show anything useful:

    [4/15/2017, 13:34:49] === Logging started: 2017/04/15 13:34:49 ===
    [4/15/2017, 13:34:49] Executable: C:\Users\Administrator\Downloads\NDP452-KB2901907-x86-x64-AllOS-ENU.exe v4.5.51209.34209
    [4/15/2017, 13:34:49] --- logging level: standard ---
    [4/15/2017, 13:34:49] Successfully bound to the ClusApi.dll
    [4/15/2017, 13:34:49] Error 0x80070424: Failed to open the current cluster
    [4/15/2017, 13:34:49] Cluster drive map: ''
    [4/15/2017, 13:34:49] Considering drive: 'C:\'...
    [4/15/2017, 13:34:49] Considering drive: 'D:\'...
    [4/15/2017, 13:34:49] Drive 'D:\' is rejected because of the unknown or unsuitable drive type
    [4/15/2017, 13:34:49] Considering drive: 'E:\'...
    [4/15/2017, 13:34:49] Drive 'E:\' is rejected because of the unknown or unsuitable drive type
    [4/15/2017, 13:34:49] Considering drive: 'Q:\'...
    [4/15/2017, 13:34:49] Drive 'C:\' has been selected as the largest fixed drive
    [4/15/2017, 13:34:49] Directory 'C:\b4201c4da5be318b38e766a508\' has been selected for file extraction
    [4/15/2017, 13:34:49] Extracting files to: C:\b4201c4da5be318b38e766a508\
    [4/15/2017, 13:35:13] Extraction took 23.993 seconds
    [4/15/2017, 13:35:13] Executing command line: 'C:\b4201c4da5be318b38e766a508\\Setup.exe   /x86 /x64 /redist'

    I can remove and re-add .NET 3.5 without issue.

    Here's what I've tried:

    1) Repairing the Windows Installer

    2) Repairing Windows Update

    3) Using the stand alone installer

    4) Removing the antivirus

    5) The .NET Framework Repair tool (which I allowed to run for over 24 hours during the second stage when it tries to collect the logs, then I cancelled it)

    6) The .NET Cleanup Tool

    The system itself checks out fine in all hardware tests, including surface and file issues with the hard drive.

    I think for debugging purposes, it's best to focus on the stand alone installer so we can exclude Windows Update issues.  I'm not really sure how to proceed so any help is appreciated!

    Thanks,

    Joe

    Sunday, April 16, 2017 9:10 PM

All replies

  • Hi Joe,

    Thank you for posting in MSDN forum.

    >>it's best to focus on the stand alone installer so we can exclude Windows Update issues

    The precondition of installing .Net Framework is that the OS is healthy, you mentioned that you used the Cleanup tool, If I were you, I wouldn't use it, because it's powerful enough that could uninstall some system files and registry key. it could lead that some application can't run properly.

    >>Error 0x80070424: Failed to open the current cluster

    Code 0x80070424 usually means  that Windows Update and defender. Please follow the article to solve this system environment problem:

    https://answers.microsoft.com/en-us/windows/forum/windows_7-security/windows-defender-does-not-respond-error-0x80070424/22fee7e9-1599-4efe-a2d9-b5d1020a8009

    Once you ensure that your Win 7 is clean, then try to install the .Net 4.X again.

    Best Regards,


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Monday, April 17, 2017 8:10 AM
    Moderator