none
Can't install .NET Framework RRS feed

  • Question

  • I've tried everything. Removed all firewall and antivirus. Removed the Framework 4.o that I had. Everytime I try the cleanup tool it works but trying to install the framework ends with a "Did not succeed" with a 0x80070643 error. I've tried unchecking .NET 3.5 from programs and it acts like it's going to uninstall and on reboot it says it fails, reverting back. I've tried 4.5.1 and it fails. Can anyone help with this?

    Windows 7 SP1

    Log file has this:

    Action: Performing Action on MSI at J:\3894a8b044f086999a\netfx_Core_x64.msi...
    [3/1/2014, 19:3:55]Log File C:\Users\Lillge\AppData\Local\Temp\Microsoft .NET Framework 4 Setup_20140301_190348329-MSI_netfx_Core_x64.msi.txt does not yet exist but may do at Watson upload time
    [3/1/2014, 19:3:55]Calling MsiInstallProduct(J:\3894a8b044f086999a\netfx_Core_x64.msi, EXTUI=1
    [3/1/2014, 19:3:56] Returning IDOK. INSTALLMESSAGE_ERROR [Could not access network location C:/Program Files\.]
    [3/1/2014, 19:3:56] Returning IDOK. INSTALLMESSAGE_ERROR [Could not access network location C:/Program Files\.]
    [3/1/2014, 19:3:56]MSI (J:\3894a8b044f086999a\netfx_Core_x64.msi) Installation failed.  Msi Log: Microsoft .NET Framework 4 Setup_20140301_190348329-MSI_netfx_Core_x64.msi.txt
    [3/1/2014, 19:3:56]PerformOperation returned 1603 (translates to HRESULT = 0x80070643)
    [3/1/2014, 19:3:56] Action complete
    [3/1/2014, 19:3:56]Error 1603:1606 is mapped to Custom Error: Retry
    [3/1/2014, 19:3:56] J:\3894a8b044f086999a\SetupUtility.exe: Verifying signature for SetupUtility.exe...
    [3/1/2014, 19:3:56]J:\3894a8b044f086999a\SetupUtility.exe -  Signature verified successfully for SetupUtility.exe
    [3/1/2014, 19:3:56] J:\3894a8b044f086999a\SetupUtility.exe Signature verified successfully for SetupUtility.exe
    [3/1/2014, 19:3:56]Signature verification succeeded for SetupUtility.exe
    [3/1/2014, 19:3:56]File J:\3894a8b044f086999a\SetupUtility.exe, is verified successfully.
    [3/1/2014, 19:3:56]Created new ExePerformer for Exe item
    [3/1/2014, 19:3:56] Action: Performing Action on Exe at J:\3894a8b044f086999a\SetupUtility.exe...
    [3/1/2014, 19:3:56]Launching CreateProcess with command line = SetupUtility.exe /wireregister
    [3/1/2014, 19:3:56]Exe log file(s) :
    [3/1/2014, 19:3:56]C:\Users\Lillge\AppData\Local\Temp\dd_SetupUtility.txt
    [3/1/2014, 19:3:56]Log File C:\Users\Lillge\AppData\Local\Temp\dd_SetupUtility.txt exists and will be added to the Watson upload list
    [3/1/2014, 19:3:56]Exe (J:\3894a8b044f086999a\SetupUtility.exe) succeeded.
    [3/1/2014, 19:3:56]Exe Log File: dd_SetupUtility.txt
    [3/1/2014, 19:3:56] Action complete
    [3/1/2014, 19:3:56]Helper item execution succeed.
    [3/1/2014, 19:3:56]Delaying for Starting to delay
    [3/1/2014, 19:3:57] Action: Performing Action on MSI at J:\3894a8b044f086999a\netfx_Core_x64.msi...
    [3/1/2014, 19:3:57]Log File C:\Users\Lillge\AppData\Local\Temp\Microsoft .NET Framework 4 Setup_20140301_190348329-MSI_netfx_Core_x64.msi.txt exists and will be added to the Watson upload list
    [3/1/2014, 19:3:57]Calling MsiInstallProduct(J:\3894a8b044f086999a\netfx_Core_x64.msi, EXTUI=1
    [3/1/2014, 19:3:57] Returning IDOK. INSTALLMESSAGE_ERROR [Could not access network location C:/Program Files\.]
    [3/1/2014, 19:3:57] Returning IDOK. INSTALLMESSAGE_ERROR [Could not access network location C:/Program Files\.]
    [3/1/2014, 19:3:57]MSI (J:\3894a8b044f086999a\netfx_Core_x64.msi) Installation failed.  Msi Log: Microsoft .NET Framework 4 Setup_20140301_190348329-MSI_netfx_Core_x64.msi.txt
    [3/1/2014, 19:3:57]PerformOperation returned 1603 (translates to HRESULT = 0x80070643)
    [3/1/2014, 19:3:57] Action complete
    [3/1/2014, 19:3:57]Error 1603:1606 is mapped to Custom Error: Retry
    [3/1/2014, 19:3:57]Retry 1 of 1 of custom error handling
    [3/1/2014, 19:3:57]Retry count over existing limit, not going to retry again.
    [3/1/2014, 19:3:57]OnFailureBehavior for this item is to Rollback.
    [3/1/2014, 19:3:57] Action: Performing actions on all Items...
    [3/1/2014, 19:3:57] Action complete
    [3/1/2014, 19:3:57] Action complete
    [3/1/2014, 19:3:57]Final Result: Installation failed with error code: (0x80070643), "Fatal error during installation. " (Elapsed time: 0 00:00:09).
    [3/1/2014, 19:3:59]WM_ACTIVATEAPP: Focus stealer's windows WAS visible, NOT taking back focus
    • Edited by Joris2705 Sunday, March 2, 2014 1:22 AM
    Sunday, March 2, 2014 1:13 AM

Answers

  • Please try this procedure:

    Please use this tool to remove .NET Framework 4.0 from your system:

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

    Once it is removed, reinstall as follows:

    Follow these steps exactly:

    Before trying to install .NET Framework 4.0, execute this command from an ELEVATED Command Prompt provided by the .NET Framework Team:

    "This issue is likely caused by a bad ACL on assembly\tmp folder. After installing updates, the ACL propagates to installed assembly folders in both 4.0 & legacy GAC.  If those updates were installed by WU or another user, the propagated ACL will prevent install of the same assembly by the current user.

    A work around would be to reset the ACL on GAC dirs.

    for /F %D in ('dir %WINDIR%\assembly %WINDIR%\Microsoft.NET\assembly /s /b /a:d') do takeown /F %D && icacls %D /reset /T"

    After running that command, follow these steps:

    Please follow these instructions exactly:

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

    http://www.microsoft.com/en-us/download/details.aspx?id=24872

    2. 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.

    Sunday, March 2, 2014 3:34 PM