none
.Net framework error(0x80070643) when trying to install or repair. RRS feed

  • Question

  • Was having trouble getting borderlands 2 to run and there was a suggestion to reinstall .net. After uninstalling it was unable to reinstall so I system restored so i wouldn't have any problems with any thing else i run. Tried just repairing same problem. I've tried installing both from the web installer and the standalone same problem. This is probably gonna be my last attempt at finding a fix before i just reinstall windows(which i dont really wanna do)

    Here's the summary log from the .net error.

    OS Version = 6.1.7601, Platform 2, Service Pack 1
    OS Description = Windows 7 - x64 Home Premium Edition Service Pack 1
    CommandLine = C:\a04574c16b4ea4cb27\\Setup.exe /x86 /x64
    TimeZone = Pacific Daylight Time
    Initial LCID = 1033
    Using Simultaneous Download and Install mechanism
    Operation: Repairing
    Package Name = Microsoft .NET Framework 4 Client Profile Setup
    Package Version = 4.0.30319
    User Experience Data Collection Policy: Disabled
    Number of applicable items: 4
    Exe (C:\a04574c16b4ea4cb27\Windows6.1-KB958488-v6001-x64.msu) failed with 0x240006 - (null).
    MSI (C:\a04574c16b4ea4cb27\netfx_Core_x64.msi) Installation failed. Msi Log: Microsoft .NET Framework 4 Client Profile Setup_20120920_222449080-MSI_netfx_Core_x64.msi.txt
    Final Result: Installation failed with error code: (0x80070643), "Fatal error during installation. " (Elapsed time: 0 00:01:01).

    Here is the logs from the collect.exe

    https://skydrive.live.com/redir?resid=123FFD6CEB1E9083!107



    • Edited by Slawth Friday, September 21, 2012 5:40 AM trying to fix skydive link
    Friday, September 21, 2012 5:37 AM

Answers

  • Give this sequence of steps a try.

    Follow ALL 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:

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

    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://aka.ms/vscollect

    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.

    • Marked as answer by Slawth Saturday, September 22, 2012 4:00 AM
    Friday, September 21, 2012 1:17 PM

All replies

  • Give this sequence of steps a try.

    Follow ALL 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:

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

    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://aka.ms/vscollect

    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.

    • Marked as answer by Slawth Saturday, September 22, 2012 4:00 AM
    Friday, September 21, 2012 1:17 PM
  • That fixed it. I was even able to start up borderlands 2 without a single problem.Was having trouble with typing the command in command prompt, until i realized i could copy&paste it.(Felt dumb for a second) So happy that i don't have to deal with reinstalling windows.

    Thank You

    Saturday, September 22, 2012 4:00 AM