none
.net Framwork 4 Intall Issue/ RRS feed

  • Question

  • OS Version = 6.0.6002, Platform 2, Service Pack 2
    OS Description = Vista - x64 Home Premium Edition Service Pack 2
    CommandLine = C:\9c814eaf4b77311a9097fe314a\\Setup.exe /x86 /x64 /ia64 /web
    TimeZone = Central 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: Disabled
    Number of applicable items: 12
    Exe (C:\9c814eaf4b77311a9097fe314a\SetupUtility.exe) succeeded.
    Exe Log File: dd_SetupUtility.txt
    ServiceControl operation succeeded!
    ServiceControl operation succeeded!
    Exe (C:\Users\Lisa\AppData\Local\Temp\Microsoft .NET Framework 4 Setup_4.0.30319\Windows6.0-KB956250-v6001-x64.msu) failed with 0x1 - Incorrect function. .
    Exe (C:\9c814eaf4b77311a9097fe314a\SetupUtility.exe) succeeded.
    Exe Log File: dd_SetupUtility.txt
    MSI (C:\Users\Lisa\AppData\Local\Temp\Microsoft .NET Framework 4 Setup_4.0.30319\netfx_Core_x64.msi) Installation failed. Msi Log: Microsoft .NET Framework 4 Setup_20120601_155451182-MSI_netfx_Core_x64.msi.txt
    Exe (C:\9c814eaf4b77311a9097fe314a\SetupUtility.exe) succeeded.
    Exe Log File: dd_SetupUtility.txt
    MSI (C:\Users\Lisa\AppData\Local\Temp\Microsoft .NET Framework 4 Setup_4.0.30319\netfx_Core_x64.msi) Installation failed. Msi Log: Microsoft .NET Framework 4 Setup_20120601_155451182-MSI_netfx_Core_x64.msi.txt
    Final Result: Installation failed with error code: (0x80070643), "Fatal error during installation. " (Elapsed time: 0 00:03:56).

    And.. here is the full log if this is any help... Log

    Basically I must have installed .net framework 4 extended beta 2 at some point, but not the client, and it wouldn't let me uninstall. So what I did was I deleted the registry keys that I was told to delete, which didn't work, so I completely cleared the file it's self, ".net framework v4" basically.. so yeah.. what do I have to do to get this installed on my computer so I can get back to working with Visual C++?

    Friday, June 1, 2012 9:04 PM

Answers

  • If you installed betas of .NET 4.0 on your system and cannot completely remove them, you may have to reinstall your OS to correct the situation. That's why installing beta software on a production system is a high risk maneuver.

    The core error is "INSTALLMESSAGE_ERROR [The Installer has insufficient privileges to modify this file: C:\Windows\system32\en-US\dfshim.dll.mui.]".

    Can we assume you ran the full installer As Administrator?

    You can try this .NET Framework cleanup tool as a last resort (fair warning, this tool might cause collateral damage):

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

    Then,

    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:

    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://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.

    Saturday, June 2, 2012 1:26 PM

All replies

  • If you installed betas of .NET 4.0 on your system and cannot completely remove them, you may have to reinstall your OS to correct the situation. That's why installing beta software on a production system is a high risk maneuver.

    The core error is "INSTALLMESSAGE_ERROR [The Installer has insufficient privileges to modify this file: C:\Windows\system32\en-US\dfshim.dll.mui.]".

    Can we assume you ran the full installer As Administrator?

    You can try this .NET Framework cleanup tool as a last resort (fair warning, this tool might cause collateral damage):

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

    Then,

    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:

    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://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.

    Saturday, June 2, 2012 1:26 PM
  • Hi rf456ti81,

    Welcome to the MSDN forum.

    It seems that core issue for you is about beta software installed.

    I agree to MVP that maybe you need to consider repair your OS.

    But before this, have you the solution listed on this link

    http://social.msdn.microsoft.com/Forums/en/netfxsetupprerelease/thread/5b528a65-9449-4a9f-8445-dd86ee077bfb

    In normal installations, it is not required to remove Beta 2 before installing RC.  But you have removed it, and we do not know whether you have completely removed it completely. It is hard for us to detect what remains on your OS.

    If you have tried all solution from that post, please backup some files then fix your OS, either repair or reinstall.

    Thanks,


    Barry Wang [MSFT]
    MSDN Community Support | Feedback to us

    Monday, June 4, 2012 3:27 AM
    Moderator