none
Status of package 'Microsoft .NET Framework 4 (x86 and x64)' after install is 'InstallFailed' RRS feed

  • Question

  • Trying to figure out why this install failed. The user's PC is 32-bit Windows 7 SP1.  Is the command argument 'FullX64Bootstrapper' correct? 

    Installing using command 'C:\Users\XXXXXX~1\AppData\Local\Temp\VSD983D.tmp\DotNetFX40\dotNetFx40_Full_setup.exe' and parameters ' /q /norestart /ChainingPackage FullX64Bootstrapper /lcid 1033'

    LOG:

    The following properties have been set:
    Property: [AdminUser] = true {boolean}
    Property: [InstallMode] = HomeSite {string}
    Property: [ProcessorArchitecture] = Intel {string}
    Property: [VersionNT] = 6.1.1 {version}
    Running checks for package 'Windows Installer 3.1', phase BuildList
    The following properties have been set for package 'Windows Installer 3.1':
    Running checks for command 'WindowsInstaller3_1\WindowsInstaller-KB893803-v2-x86.exe'
    Result of running operator 'VersionGreaterThanOrEqualTo' on property 'VersionMsi' and value '3.1': true
    Result of checks for command 'WindowsInstaller3_1\WindowsInstaller-KB893803-v2-x86.exe' is 'Bypass'
    'Windows Installer 3.1' RunCheck result: No Install Needed
    Running checks for package 'Microsoft .NET Framework 4 (x86 and x64)', phase BuildList
    Reading value 'Version' of registry key 'HKLM\Software\Microsoft\NET Framework Setup\NDP\v4\Full'
    Unable to read registry value
    Not setting value for property 'DotNet40Full_TargetVersion'
    The following properties have been set for package 'Microsoft .NET Framework 4 (x86 and x64)':
    Running checks for command 'DotNetFX40\dotNetFx40_Full_x86_x64.exe'
    Result of running operator 'ValueEqualTo' on property 'InstallMode' and value 'HomeSite': true
    Result of checks for command 'DotNetFX40\dotNetFx40_Full_x86_x64.exe' is 'Bypass'
    Running checks for command 'DotNetFX40\dotNetFx40_Full_setup.exe'
    Result of running operator 'ValueNotEqualTo' on property 'InstallMode' and value 'HomeSite': false
    Skipping ByPassIf because Property 'DotNet40Full_TargetVersion' was not defined
    Result of running operator 'ValueEqualTo' on property 'AdminUser' and value 'false': false
    Result of running operator 'VersionLessThan' on property 'VersionNT' and value '5.1.2': false
    Result of running operator 'ValueEqualTo' on property 'ProcessorArchitecture' and value 'IA64': false
    Result of checks for command 'DotNetFX40\dotNetFx40_Full_setup.exe' is 'Install'
    'Microsoft .NET Framework 4 (x86 and x64)' RunCheck result: Install Needed
    EULA for components 'Microsoft .NET Framework 4 (x86 and x64)' was accepted.
    Copying files to temporary directory "C:\Users\XXXXXX~1\AppData\Local\Temp\VSD983D.tmp\"
    Downloading files to "C:\Users\XXXXXX~1\AppData\Local\Temp\VSD983D.tmp\"
    (1/2/2013 11:09:57 AM) Downloading 'DotNetFX40\dotNetFx40_Full_setup.exe' from 'http://go.microsoft.com/fwlink/?linkid=182805' to 'C:\Users\XXXXXX~1\AppData\Local\Temp\VSD983D.tmp\'
    Download completed at 1/2/2013 11:10:00 AM
    Verifying file integrity of C:\Users\XXXXXX~1\AppData\Local\Temp\VSD983D.tmp\DotNetFX40\dotNetFx40_Full_setup.exe
    WinVerifyTrust returned 0
    File trusted
    Running checks for package 'Microsoft .NET Framework 4 (x86 and x64)', phase BeforePackage
    Reading value 'Version' of registry key 'HKLM\Software\Microsoft\NET Framework Setup\NDP\v4\Full'
    Unable to read registry value
    Not setting value for property 'DotNet40Full_TargetVersion'
    The following properties have been set for package 'Microsoft .NET Framework 4 (x86 and x64)':
    Running checks for command 'DotNetFX40\dotNetFx40_Full_setup.exe'
    Result of running operator 'ValueNotEqualTo' on property 'InstallMode' and value 'HomeSite': false
    Skipping ByPassIf because Property 'DotNet40Full_TargetVersion' was not defined
    Result of running operator 'ValueEqualTo' on property 'AdminUser' and value 'false': false
    Result of running operator 'VersionLessThan' on property 'VersionNT' and value '5.1.2': false
    Result of running operator 'ValueEqualTo' on property 'ProcessorArchitecture' and value 'IA64': false
    Result of checks for command 'DotNetFX40\dotNetFx40_Full_setup.exe' is 'Install'
    'Microsoft .NET Framework 4 (x86 and x64)' RunCheck result: Install Needed
    Verifying file integrity of C:\Users\XXXXXX~1\AppData\Local\Temp\VSD983D.tmp\DotNetFX40\dotNetFx40_Full_setup.exe
    WinVerifyTrust returned 0
    File trusted
    Installing using command 'C:\Users\XXXXXX~1\AppData\Local\Temp\VSD983D.tmp\DotNetFX40\dotNetFx40_Full_setup.exe' and parameters ' /q /norestart /ChainingPackage FullX64Bootstrapper /lcid 1033'
    Process exited with code 5100
    Status of package 'Microsoft .NET Framework 4 (x86 and x64)' after install is 'InstallFailed'

    Wednesday, January 2, 2013 4:55 PM

Answers

  • This problem apparently stems from the fact that the user lacks permission to install the .NET framework "for all users on this PC".  
    Tuesday, January 8, 2013 7:19 PM

All replies

  • Please retry the install using this procedure:

    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.

    The complete log set is needed for analysis.

    Wednesday, January 2, 2013 11:33 PM
  • Hi,

    Thanks for your post.

    When referring to this page http://msdn.microsoft.com/en-us/library/vstudio/ee390831(v=vs.100).aspx

    You can see that 5100 code means: "The user's computer does not meet system requirements"

    I'm afraid the issue is actually due to your command since .NET 4 can be installed on Win 7.

    But may I ask do you have .NET 4 installed on that OS? What's the result if you just use the standalone installer?

    When you refer to this page http://msdn.microsoft.com/library/ee942965(v=VS.100).aspx, you will also see the following:

    dotNetFx40_Client_x86_x64.exe /q /norestart /ChainingPackage "MyProductName"

    What do you mean of 'FullX64Bootstrapper' ? What's your product name?

    Regards,


    Barry Wang
    MSDN Community Support | Feedback to us
    Develop and promote your apps in Windows Store
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Thursday, January 3, 2013 7:40 AM
    Moderator
  • I used the Publish Wizard in Visual Studio 2010 to initiate a ClickOnce deployment of a WinForms application I've written; the app has been targeted to version 4 of the framework.  The deployment server is an in-house LAN server; the app will be run by our internal users. So, to answer your question, I am not sure what my "product name" is or is supposed to be, as the installation of the .NET framework on the user's PC is being handled by Microsoft's ClickOnce automation mechanisms.

    Thursday, January 3, 2013 4:46 PM
  • Thank you for the detailed set of workarounds.  What is "WU", btw? 

    I am not sure who the "user" is, as the installation process is being handled by the ClickOnce deployment automation. I used the Visual Studio 2010 Publish wizard to deploy a WinForms application (targeted to .NET Framework 4.0) to one of our in-house LAN servers, and the users simply click on the URI to install the program prerequisites onto their PCs.

    Also, I am still wondering why the 64-bit version was being installed, at least that's what seems to be going on.



    Thursday, January 3, 2013 5:25 PM
  • This problem apparently stems from the fact that the user lacks permission to install the .NET framework "for all users on this PC".  
    Tuesday, January 8, 2013 7:19 PM
  • Thanks for sharing your result here.

    Barry Wang
    MSDN Community Support | Feedback to us
    Develop and promote your apps in Windows Store
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Thursday, January 10, 2013 7:04 AM
    Moderator