none
.NET Framework 4 fails to install. Package error. RRS feed

  • Question

  • Hi all,

    The last week I've been trying to install Microsoft .NET Framework 4.
    I've been doing this by using the web installer and (as that didn't work) the full installer downloaded from the official Microsoft pages. Running as an administrator (by right-clicking) this is what happened: The installer tries to unpack, then comes with an error stating

    "Setup encountered an unexpected error in the package contents.
    The package will not be installed.
    Please contact your vendor for a new package."

    The last .html log file shows this:

    OS Version = 6.1.7601, Platform 2, Service Pack 1
    OS Description = Windows 7 - x64 Home Premium Edition Service Pack 1
    CommandLine = D:\114c1ed61252e760b831\\Setup.exe /x86 /x64
    TimeZone = West-Europa (zomertijd)
    Initial LCID = 1043
    LogFileHint [\Temp\dd_SetupUtility.txt] is invalid. First character must not be '*', '?' or '\'.
    Setup encountered an unexpected error in the package contents. The package will not be installed. Please contact your vendor for a new package.
    Final Result: Installation failed with error code: (0x000013ED), "An internal or user error was encountered." (Elapsed time: 0 00:00:00).

    I don't know what to do anymore. Could somebody please help me?

    Regards,

    Rob.



    Wednesday, June 12, 2013 1:06 PM

Answers

  • My problem is solved!
    When locating my TEMP folder with CMD > set it turned out that the temp folder defined in my system was pointing to C:\Temp. The .NET-installer however was using D:\Temp for some reason.

    After using Configuration > System config> Advanced properties to change my system variables to D:\Temp the installer works flawlessly. :)


    Thursday, June 13, 2013 7:49 AM

All replies

  • Sounds like possible download corruption.

    Check your download of the full .NET 4.0 (~48 Meg) against these checksum values.

    MD5 - 251743dfd3fda414570524bac9e55381

    SHA1 - 58da3d74db353aad03588cbb5cea8234166d8b99

    Wednesday, June 12, 2013 2:18 PM
  • Checksums are

    251743dfd3fda414570524bac9e55381 / 58da3d74db353aad03588cbb5cea8234166d8b99

    Checked it with the Microsoft (R) File Checksum Integrity Verifier tool.
    Seems to be correct... :(


    Wednesday, June 12, 2013 3:00 PM
  • In another thread on the same error, these steps solved the issue.

    Please follow the procedure below:

    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.

    Wednesday, June 12, 2013 5:52 PM
  • I did find that thread already and tried that solution, but without any result.
    I'll try it again, though, and post the logs in a couple of minutes.

    Thanks!

    Thursday, June 13, 2013 7:23 AM
  • My problem is solved!
    When locating my TEMP folder with CMD > set it turned out that the temp folder defined in my system was pointing to C:\Temp. The .NET-installer however was using D:\Temp for some reason.

    After using Configuration > System config> Advanced properties to change my system variables to D:\Temp the installer works flawlessly. :)


    Thursday, June 13, 2013 7:49 AM