none
.Net framwork 4 client profile windows 7 x64 won't repair RRS feed

  • Question

  • Keep trying to install this as my Intuit products won't work with out it.  It installs through windows update and indicates successfull, but when I click on it from the control panel, it needs to be repaired.  When I run the repair tool, it fails during the roll back process.  Here is the log file

     

    OS Version = 6.1.7601, Platform 2, Service Pack 1
    OS Description = Windows 7 - x64 Service Pack 1
    CommandLine = "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\SetupCache\Client\Setup.exe" /repair /x86 /x64 /parameterfolder Client
    TimeZone = Central Standard 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: AlwaysUploaded
     

    Number of applicable items: 4
    Exe (C:\Windows\Microsoft.NET\Framework64\v4.0.30319\SetupCache\Client\Windows6.1-KB958488-v6001-x64.msu) failed with 0x240006 - (null).
    MSI (C:\Windows\Microsoft.NET\Framework64\v4.0.30319\SetupCache\Client\netfx_Core_x64.msi) Installation failed. Msi Log: Microsoft .NET Framework 4 Client Profile Setup_20120124_211011983-MSI_netfx_Core_x64.msi.txt
    Final Result: Installation failed with error code: (0x80070643), "Fatal error during installation. " (Elapsed time: 0 00:00:57).

     

    Have read some of the threads on installing it and have tried a couple of clean up tools and re-install, but having the same problem.  Thoughts?


    • Edited by jbredem Wednesday, January 25, 2012 2:17 PM
    Wednesday, January 25, 2012 3:20 AM

Answers

  • This confuses me:

    "It does install successfully, and all the updates download and install successfully, but its still broken and won't repair when I run the repair tool."

    What is telling you that .NET Framework 4.0 needs repair? TurboTax? When you say "repair tool", are you referring to the repair option offered by the installed programs dialog when you select Microsoft .NET Framework 4.0 in the installed programs list, or to a different tool? If a different tool, what did you use?

    According to your log, .NET Framework 4.0 Client Profile did not install successfully. Here is the core error:

    "INSTALLMESSAGE_ERROR [There is a problem with this Windows Installer package. Please refer to the setup log for more information. ]
     MSI (C:\Windows\Microsoft.NET\Framework64\v4.0.30319\SetupCache\Client\netfx_Core_x64.msi) Installation failed. Msi Log: Microsoft .NET Framework 4 Client Profile Setup_20120204_183019449-MSI_netfx_Core_x64.msi.txt
     PerformOperation returned 1603 (translates to HRESULT = 0x80070643)"

    This indicates an issue with the Winsows Installer on your system if you did follow all steps I provided in my earlier reply.

    Windows Installer issues may require OS repair or reinstallation. Here is an article that may help:

    http://www.sevenforums.com/tutorials/3413-repair-install.html

    • Proposed as answer by Alexander Sun Tuesday, February 7, 2012 8:34 AM
    • Marked as answer by Helen Zhou Thursday, February 9, 2012 8:49 AM
    Sunday, February 5, 2012 2:34 AM

All replies

  • Please follow these steps exactly:

    Completely remove .NET Framework 4.0 with this:

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

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

    http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=24872

    2. Before running the installer, apply irarab's fix as follows:

    "I went to "C:\Windows\Microsoft.NET" there is a directory called "assembly".

    I looked in the directory and found some subdirectories with lots of old dot net 4 files. I renamed the directory assembly2 and tried to install Dot Net 4 and it worked!!!!

    (You can't delete the assembly directory unless you take ownership of it but you can rename it.)"

    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.

    If the install fails, provide complete install logs as follows:

    Collect your full 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.

    • Proposed as answer by Alexander Sun Thursday, January 26, 2012 6:32 AM
    Wednesday, January 25, 2012 1:47 PM
  • I did all of this and it said the install was successful, however when I tried to use Turbo Tax, once again it would not run, so I check .Net 4, which needed to be repaired.  It repaired successfully, but still no luck running Turbo Tax, so I did Windows Update and installed 6 .Net updates.  .Net 4 needed to be repaired, which I tried and now it won't repair.  Here is the log file from the attempted repair.

     

    OS Version = 6.1.7601, Platform 2, Service Pack 1
    OS Description = Windows 7 - x64 Service Pack 1
    CommandLine = "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\SetupCache\Client\Setup.exe" /repair /x86 /x64 /parameterfolder Client
    TimeZone = Central Standard 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: AlwaysUploaded
       
     
     
      
       
     
    Number of applicable items: 4
    Exe (C:\Windows\Microsoft.NET\Framework64\v4.0.30319\SetupCache\Client\Windows6.1-KB958488-v6001-x64.msu) failed with 0x240006 - (null).
    MSI (C:\Windows\Microsoft.NET\Framework64\v4.0.30319\SetupCache\Client\netfx_Core_x64.msi) Installation failed. Msi Log: Microsoft .NET Framework 4 Client Profile Setup_20120129_161610159-MSI_netfx_Core_x64.msi.txt
    Final Result: Installation failed with error code: (0x80070643), "Fatal error during installation. " (Elapsed time: 0 00:01:26).

     

     

    now what?



    • Edited by jbredem Monday, January 30, 2012 3:06 AM
    Sunday, January 29, 2012 10:23 PM
  • We need to see the full set of logs, contained in the vslogs.cab file produced by Collect.exe.

    Collect your full 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, January 29, 2012 11:19 PM
  • Here is the vslogs.cab link on skydrive.
    https://skydrive.live.com/redir.aspx?cid=0c54d87fbed7b275&resid=C54D87FBED7B275!104&parid=C54D87FBED7B275!103&authkey=!AJVhTTnDgto8qsU

    Thanks.  I await where I went wrong in all this.

    Monday, January 30, 2012 3:19 AM
  • Hi Huangqijin,

     

    Welcome to the MSDN forum.

     

    Based on your log:

    [1/29/2012, 16:17:21] Returning IDOK. INSTALLMESSAGE_ERROR [There is a problem with this Windows Installer package. Please refer to the setup log for more information. ]

    01/29/12 16:17:21 DDSet_Status: Sleeping 100ms...

    01/29/12 16:17:21 DDSet_Error: Failed to install assembly C:\Windows\Microsoft.NET\Framework\v4.0.30319\ISymWrapper.dll. IAssemblyCache->InstallAssembly() returned -2147024891.

    01/29/12 16:17:21 DDSet_Error: Failed to install assembly 'C:\Windows\Microsoft.NET\Framework\v4.0.30319\ISymWrapper.dll' because of system error: Access is denied.

    Typically transient errors such as this are caused by the file being in use (unlikely; the file shouldn't be installed yet) or if - while copying - something like anti-virus locks the file in use. If you have anti-virus software, try temporarily disabling it / pausing it and see if you're able to get passed this error.

     

    I recommend you try to delete the folder “v4.0.30319” under this path “C:\Windows\Microsoft.NET\Framework\” before you begin to install .NET Framework 4. For more information, you can refer to this page: http://social.msdn.microsoft.com/Forums/en-US/vssetup/thread/8655d21b-259b-449d-a0f4-0b94cdc353a1/

     

    If an assembly file in the GAC (Global Access Cache) has been locked or is "in use" it can cause .NET Framework patches to fail. For more information, you can refer to this page: http://support.microsoft.com/default.aspx?scid=2263996

     

    Then, Secondly, please try using the SubInACL tool to repair file and registry permissionshttp://blogs.msdn.com/astebner/archive/2006/09/04/739820.aspx
    SubInACL tool is most useful when a setup package fails with error code 5 or 0x5 or 0x80070005. All of these error codes mean Access Denied, and this type of error code is often caused by missing ACLs for the Administrators group or the built-in System account.

     

    If you have any other questions, please feel free to let me know.

     

    Best Regards,


    Alexander Sun [MSFT]
    MSDN Community Support | Feedback to us
    Monday, January 30, 2012 8:32 AM
  • I am a little unclear on how you think I should proceed.  Can I try the above fixes and re-run the repair tool, or do I need to remove .Net, do a clean up, then do all these fixes and start over on the install?  Thanks again
    Monday, January 30, 2012 7:03 PM
  • Hi Jbredem,

     

    You are not required to remove other .NET Frameworks you have. Which repair tool do you use?

    You can try the methods above and start installation.

     

    If you have any other questions, please feel free to let me know.

     

    Best Regards,


    Alexander Sun [MSFT]
    MSDN Community Support | Feedback to us
    Tuesday, January 31, 2012 9:38 AM
  • Removed it, tried all of the above again.  It does install successfully, and all the updates download and install successfully, but its still broken and won't repair when I run the repair tool.  Here is the log file.

    One thing that did not work was the SubinACL.  Created the file and everything, but when I run it from the cmd prompt,  i get that SubinACL is not recognized, but I know it downloaded and installed and I can see it in C:\Program Files (x86)\Windows Resource Kits\Tools directory

     

    https://skydrive.live.com/redir.aspx?cid=0c54d87fbed7b275&resid=C54D87FBED7B275!105&parid=C54D87FBED7B275!103&authkey=!ALbNUHcGmV4-zz8

    Any other suggestions are greatly appreciated.

    Sunday, February 5, 2012 1:10 AM
  • This confuses me:

    "It does install successfully, and all the updates download and install successfully, but its still broken and won't repair when I run the repair tool."

    What is telling you that .NET Framework 4.0 needs repair? TurboTax? When you say "repair tool", are you referring to the repair option offered by the installed programs dialog when you select Microsoft .NET Framework 4.0 in the installed programs list, or to a different tool? If a different tool, what did you use?

    According to your log, .NET Framework 4.0 Client Profile did not install successfully. Here is the core error:

    "INSTALLMESSAGE_ERROR [There is a problem with this Windows Installer package. Please refer to the setup log for more information. ]
     MSI (C:\Windows\Microsoft.NET\Framework64\v4.0.30319\SetupCache\Client\netfx_Core_x64.msi) Installation failed. Msi Log: Microsoft .NET Framework 4 Client Profile Setup_20120204_183019449-MSI_netfx_Core_x64.msi.txt
     PerformOperation returned 1603 (translates to HRESULT = 0x80070643)"

    This indicates an issue with the Winsows Installer on your system if you did follow all steps I provided in my earlier reply.

    Windows Installer issues may require OS repair or reinstallation. Here is an article that may help:

    http://www.sevenforums.com/tutorials/3413-repair-install.html

    • Proposed as answer by Alexander Sun Tuesday, February 7, 2012 8:34 AM
    • Marked as answer by Helen Zhou Thursday, February 9, 2012 8:49 AM
    Sunday, February 5, 2012 2:34 AM
  • Based on the link in your reply and what I read, it seems to point to an issue with my Windows installer and Windows 7 OS.  I have been searching for what came with my Dell and have come up empty handed and also never made a restore disk.  Is there anyway through Dell or Microsoft I can get what I need so I don't have to start from scratch?
    Monday, February 13, 2012 2:18 AM
  • Hi Jbredem,

    You can find some information about repair and reinstall
    Windows 7 here: http://answers.microsoft.com/en-us/windows/forum/windows_7-system

    You can also go to the DELL support: http://en.community.dell.com/support-forums/software-os/f/3524.aspx
    I hope this helps.

    Best Regards,


    Alexander Sun [MSFT]
    MSDN Community Support | Feedback to us

    Monday, February 13, 2012 6:46 AM
  • Please help me! I wasn't able to update the windows atualizations. Everytime i shut down the machine its requests 8 updates. So i ended up here and i did everything you said and tried to reinstall the .NET Framework 4.0 but it fails. So..here is my link>

    https://skydrive.live.com/redir?resid=91FB775283EB4226!253&authkey=!AB9DUgRwDwU-cI8

    I REALLY can't afford to reinstall windows right now because its a company pc and it demands a lot of time to do it.

    Thank you!

    Friday, May 18, 2012 10:07 PM
  • You really should start a new thread. Posting to this old, answered thread means that most forum readers will never see your post.

    This symptom, "Everytime i shut down the machine its requests 8 updates" indicates a Windows Update issue.

    Looking at the KB install logs, the issue is this:

    "INSTALLMESSAGE_ERROR [Could not write value runtimeVersion in key \ Software \ Classes \ CLSID \ {8066FB71-AFA1-343E-8070-44AB4F3F85C9} \ InprocServer32 \ 4.0.0.0. Make sure you have sufficient access to that key or contact support personnel.]"

    All the KB's fail for the same reason.

    I suggest you read through this thread and try Alexander Sun's fixes for this type of issue.

    http://social.msdn.microsoft.com/Forums/zh/netfxsetup/thread/652d544a-04a4-4540-be49-6686ea0f17b6

    Friday, May 18, 2012 11:27 PM
  • I did alexanders way but still nothing. I'm still not able to install .NET framework again
    Monday, May 21, 2012 1:50 PM
  • Then, provide the new 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.

    Monday, May 21, 2012 2:02 PM
  • Here! 

    https://skydrive.live.com/redir?resid=91FB775283EB4226!255&authkey=!AOMhjSWX_-QIceM

    Plz take a look! See if you can help me! 

    Thanks!

    Monday, May 21, 2012 6:02 PM
  • From the logs, here's your core issue:

    "Exe (C:\b57028f0e90c411c191064f189cb\Windows6.1-KB958488-v6001-x64.msu) failed with 0x240006 - (null).
    PerformOperation on exe returned exit code 2359302 (translates to HRESULT = 0x240006)

    INSTALLMESSAGE_ERROR [There is a problem with this Windows Installer package. Please refer to the setup log for more information. ]
    MSI (C:\b57028f0e90c411c191064f189cb\netfx_Core_x64.msi) Installation failed. Msi Log: Microsoft .NET Framework 4 Setup_20111014_213020945-MSI_netfx_Core_x64.msi.txt
    PerformOperation returned 1603 (translates to HRESULT = 0x80070643)"

    I suggest you read through this thread, especially Alexander Sun's answer as it pertains to the KB issue.

    http://social.msdn.microsoft.com/Forums/en-US/netfxsetup/thread/9f3e6515-32ce-4163-8496-8d7835de2a55

    I would also ask you to follow all steps in the suggestions I offer in the same thread, as I note from your vslogs that there were several attempts to install .NET Framework 4.0 without clearing your %temp% directory before each attempt.

    As a matter of fact, you should follow the steps below 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/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.

    Monday, May 21, 2012 10:26 PM