none
.NET Framework Maintenance Repair failed RRS feed

  • Question

  • I was installing one of my games through steam and part of the installation process a Frame work maintenance occers but fails half way through the installation:

    Log file:

    OS Version = 6.1.7601, Platform 2, Service Pack 1
    OS Description = Windows 7 - x64 Home Premium Edition Service Pack 1
    CommandLine = D:\2081cc5802c3e03e9a\\Setup.exe /passive /showfinalerror /norestart /x86 /x64
    TimeZone = GMT Daylight Time
    Initial LCID = 1033
    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: AlwaysUploaded
    Number of applicable items: 6
    Exe (D:\2081cc5802c3e03e9a\Windows6.1-KB958488-v6001-x64.msu) failed with 0x240006 - (null).
    MSI (D:\2081cc5802c3e03e9a\netfx_Core_x64.msi) Installation failed. Msi Log: Microsoft .NET Framework 4 Setup_20120420_001854869-MSI_netfx_Core_x64.msi.txt
    Final Result: Installation failed with error code: (0x80070643), "Fatal error during installation. " (Elapsed time: 0 00:01:41).

    I would unistall and reinstall but rather leave it unless i really have to. Any help would be appreciated. Have tried downloading installer from main site to run repair same issue.



    • Edited by Stephan285 Thursday, April 19, 2012 11:52 PM
    Thursday, April 19, 2012 11:31 PM

Answers

  • You appear to have a Windows Installer problem in your system.

    "INSTALLMESSAGE_ERROR [There is a problem with this Windows Installer package. Please refer to the setup log for more information. ]
     MSI (D:\ab4ef8932fb2f62968da89e0\netfx_Core_x64.msi) Installation failed. Msi Log: Microsoft .NET Framework 4 Setup_20120420_141503968-MSI_netfx_Core_x64.msi.txt"

    But, before you address a possible Windows Installer problem, I am concerned that not all the steps I provided previously were completed. The fact that there were logs from 2 install attempts in your vslogs.cab indicetes that yout %temp% directory was not cleared before each attempt.

    Did you do this before each attempt?

    "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"

    Did you do this before each attempt?

    "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. 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 not, please make sure to complete all steps.

    If you did do all steps and the install fails, you will have to address Windows Installer problems here:

    http://answers.microsoft.com/en-us/windows/forum/windows_7

    Here is a post on those forums that may help:

    http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_install/how-do-i-repair-windows-installer/183fdb1d-96c6-407f-9dcb-df3b4e5b087e

    • Marked as answer by Stephan285 Saturday, April 21, 2012 5:27 PM
    Saturday, April 21, 2012 1:47 PM

All replies

  • To find out if your .NET Framework 4.0 installation is OK,use this tool:

    http://blogs.msdn.com/b/astebner/archive/2008/10/13/8999004.aspx

    Run the tool, selecting .NET Framework 4.0, then post the first 15 lines and last 15 lines of tool output here:

    Look at the last 15 lines of the output where test application results are recorded. If the test app failed (as repair already failed), you have no choice but to remove .NET Framework 4.0, then reinstall using these steps:

    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/download/en/details.aspx?displaylang=en&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://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.

    Once you have .NET Framework 4.0 successfully installed, then install your game.

    Friday, April 20, 2012 12:05 AM
  • No luck have tried removing and reinstalled but having the same issues, rollback and installation error. Log below:

    OS Version = 6.1.7601, Platform 2, Service Pack 1
    OS Description = Windows 7 - x64 Home Premium Edition Service Pack 1
    CommandLine = D:\ab4ef8932fb2f62968da89e0\\Setup.exe /passive /showfinalerror /norestart /x86 /x64
    TimeZone = GMT Daylight Time
    Initial LCID = 1033
    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 (D:\ab4ef8932fb2f62968da89e0\SetupUtility.exe) succeeded.
    Exe Log File: dd_SetupUtility.txt
    ServiceControl operation succeeded!
    ServiceControl operation succeeded!
    Exe (D:\ab4ef8932fb2f62968da89e0\Windows6.1-KB958488-v6001-x64.msu) failed with 0x240006 - (null).
    Exe (D:\ab4ef8932fb2f62968da89e0\SetupUtility.exe) succeeded.
    Exe Log File: dd_SetupUtility.txt
    MSI (D:\ab4ef8932fb2f62968da89e0\netfx_Core_x64.msi) Installation failed. Msi Log: Microsoft .NET Framework 4 Setup_20120420_141503968-MSI_netfx_Core_x64.msi.txt
    Final Result: Installation failed with error code: (0x80070643), "Fatal error during installation. " (Elapsed time: 0 00:01:22).

    Also Collect .exe link: https://skydrive.live.com/?cid=488fbcaf5e175c39#cid=488FBCAF5E175C39&id=488FBCAF5E175C39!143

    Friday, April 20, 2012 1:17 PM
  • Sorry, but we need to see the complete set of logs.

    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.

    Friday, April 20, 2012 2:27 PM
  • Tried SkyDrive again not exactly sure how it works. New link:https://skydrive.live.com/?cid=488fbcaf5e175c39
    Friday, April 20, 2012 2:40 PM
  • You have to share files in your SkyDrive for others to access them.

    Right click on your vslogs.cab, select Share. In the dialog, select Get a link, then make the file public.

    Friday, April 20, 2012 9:21 PM
  • Oh, i see. Every idiot proof...;-)

    https://skydrive.live.com/redir.aspx?cid=488fbcaf5e175c39&resid=488FBCAF5E175C39!151&parid=488FBCAF5E175C39!142&authkey=!AF6uYy_qUO_nsYA

    Friday, April 20, 2012 9:27 PM
  • You appear to have a Windows Installer problem in your system.

    "INSTALLMESSAGE_ERROR [There is a problem with this Windows Installer package. Please refer to the setup log for more information. ]
     MSI (D:\ab4ef8932fb2f62968da89e0\netfx_Core_x64.msi) Installation failed. Msi Log: Microsoft .NET Framework 4 Setup_20120420_141503968-MSI_netfx_Core_x64.msi.txt"

    But, before you address a possible Windows Installer problem, I am concerned that not all the steps I provided previously were completed. The fact that there were logs from 2 install attempts in your vslogs.cab indicetes that yout %temp% directory was not cleared before each attempt.

    Did you do this before each attempt?

    "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"

    Did you do this before each attempt?

    "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. 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 not, please make sure to complete all steps.

    If you did do all steps and the install fails, you will have to address Windows Installer problems here:

    http://answers.microsoft.com/en-us/windows/forum/windows_7

    Here is a post on those forums that may help:

    http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_install/how-do-i-repair-windows-installer/183fdb1d-96c6-407f-9dcb-df3b4e5b087e

    • Marked as answer by Stephan285 Saturday, April 21, 2012 5:27 PM
    Saturday, April 21, 2012 1:47 PM
  • Sucess! Tried installing it the way you said it a couple of times but thirds time was the charm! The issue may have been the fact that i didn't run the installer and/or Command Prompt on administrator, or/and miss inputed the command in the prompt. Thanks for the help!
    Saturday, April 21, 2012 5:27 PM