Jump to content
ricktendo

[Slim] .NET Framework 4 Full x86/x64 (1-10-2016)

Recommended Posts

With 11-25-2014 version (md5 = 4C78E9AACFDD6E1AD1B9430F53492928)

I got one problem when installating it with dotNetFx40_Full_x86_x64_Slim.exe /ain

 

"Error during execution "C:\Windows\Microsoft .NET\Framework\v4.0.30319\ngen executequeueditems /nologo /silent"

Specified file not found.

 

Testing back the 11-11-2014 version (md5 = 9A73B7E2F4B42ABE0666791F026D11C4) to be sure it's not my WES7 install who is corrupted.

 

 

post-60863-0-75684600-1417017439_thumb.p

Share this post


Link to post
Share on other sites

I just tested the same WES7 x86 image with the 11-11-2014 version (md5 = 9A73B7E2F4B42ABE0666791F026D11C4).

And the installating with dotNetFx40_Full_x86_x64_Slim.exe /ain was successfull, strange.

 

Ricktendo, I can't reply to you question yet without retrying :)

Share this post


Link to post
Share on other sites

Hi @rick, I install 4.5.2 normally and it's good on VM, but with this .NET 4 gives this error when I try to install. MD5 five OK.

 

7lofUfe.png

 

it says: "This patch package could not be opened. Verify that the patch package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer patch package." I paste this from microsoft article for english.

 

 

 

post-6880-0-53579300-1417344389_thumb.pn

Share this post


Link to post
Share on other sites

With 11-25-2014 version (md5 = 4C78E9AACFDD6E1AD1B9430F53492928)

I got one problem when installating it with dotNetFx40_Full_x86_x64_Slim.exe /ain

 

"Error during execution "C:\Windows\Microsoft .NET\Framework\v4.0.30319\ngen executequeueditems /nologo /silent"

Specified file not found.

 

Testing back the 11-11-2014 version (md5 = 9A73B7E2F4B42ABE0666791F026D11C4) to be sure it's not my WES7 install who is corrupted.

 

Good news, no more problem with your latest build :)

MD5 = 4BCF11C4DE8570433EA079717DB4A928

Share this post


Link to post
Share on other sites

I want to build a full net framework 4 (core+extended x86) installer, and I have noticed that when I integrate the same hotfix into both msi (netfx_Core_x86.msi and netfx_Extended_x86.msi) they take the same package code, so when I install them, the .Net Framework 4 Extended is not installed because have same GUID of already installed Client Profile; if I change the package code with InstEd, it install correctly.

 

So my questions:

- There's a way to apply an update (.msp) to an .msi without changing the .msi package code?

- There's a script (.cmd or .vbs) for changing the package code?

 

Share this post


Link to post
Share on other sites

Yes there is a VBS (WiSumInf.vbs) that you can use to edit the Summary Information, you will find it in msi_vbs_examples.zip in any Microsoft Windows SDK

Here is the command I use to repair the Core and Extended MSI's after updating (I also fix the Name and Description):

 

WiSumInf netfx_Core_x86.msi Subject="Microsoft .NET Framework 4 Client Profile" Comments="Microsoft .NET Framework 4 Client Profile; Copyright (C) Microsoft Corporation, All rights reserved." Revision={F3592794-C7C9-495D-8985-EDD0D19ECD10}WiSumInf netfx_Extended_x86.msi Subject="Microsoft .NET Framework 4 Extended" Comments="Microsoft .NET Framework 4 Extended; Copyright (C) Microsoft Corporation, All rights reserved." Revision={6049F8E7-4CD1-48EC-92A9-039B68CD82B3}

Share this post


Link to post
Share on other sites

Yes there is a VBS (WiSumInf.vbs) that you can use to edit the Summary Information, you will find it in msi_vbs_examples.zip in any Microsoft Windows SDK

 

Very helpful, thanks!

In the Windows Installer SDK, there are also other tools for the same task, such as msidb.exe (for exporting and importing the Summary Information stream) and MsiInfo.exe for editing the properties individually.

Personally I prefer to save(before updating) and restore(after updating) all the Summary Information stream with these commands:

:: Export Summary Information stream to text files Core.idt and Extended.idt:msidb -e_SummaryInformation -f"folder_where_to_store_text_file" -dnetfx_Core_x86.msiren _SummaryInformation.idt Core.idtmsidb -e_SummaryInformation -f"folder_where_to_store_text_file" -dnetfx_Extended_x86.msiren _SummaryInformation.idt Extended.idt:: Restore Summary Information stream from saved Core.idt and Extended.idt:msidb -iCore.idt -f"folder_of_Core.idt" -dnetfx_Core_x86.msimsidb -iExtended.idt -f"folder_of_Extended.idt" -dnetfx_Extended_x86.msi

Share this post


Link to post
Share on other sites

Because I updated it to 1.7 and forgot to edit the link. Fixed!

thanks a lot ricktendo. İ wanna ask a question. if i want a slim package as x86 how should i edit sfx and config.txt.. i researched but couldn't find it, sorry

Share this post


Link to post
Share on other sites

Is this pack no longer compatible with the crossed out OS's?

OS: Windows XP SP3 Windows Vista/Server 2008 SP2 x86/x64 or Windows 7/Server 2008 R2 SP1 x86/x64

 

If running Vista or newer should I just install the "[slim] .NET Framework 4.5.2 Full x86/x64 (2-11-2015)"?

Share this post


Link to post
Share on other sites

AFAIK, it is not that this pack is not compatible with Vista and later, I think it would install just fine, it's just that the 4.5.2 version completely supersedes and replaces it, making the 4.0 version unnecessary if you are going to install 4.5.2.  So, yes, I think you should just install 4.5.2 if running Vista or later.  On the other hand, for XP version 4.0 is the latest version of .NET that will install and function correctly.

 

Cheers and Regards

Share this post


Link to post
Share on other sites

AFAIK, it is not that this pack is not compatible with Vista and later, I think it would install just fine, it's just that the 4.5.2 version completely supersedes and replaces it, making the 4.0 version unnecessary if you are going to install 4.5.2.  So, yes, I think you should just install 4.5.2 if running Vista or later.  On the other hand, for XP version 4.0 is the latest version of .NET that will install and function correctly.

 

Cheers and Regards

 

It is compatible, but unless your software does not work with 4.5.x then go with the higher version

 

excellent! Thanks for the prompt responses.

Edited by J.J.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Similar Content

    • By abbodi1406
      Description:
       
      The .NET Framework is a popular development platform for building apps for Windows, Windows Store, Windows Phone, Windows Server, and Windows Azure. The .NET Framework platform includes the C# and Visual Basic programming languages, the common language runtime, and an extensive class library. read more.
       
      Info: The .NET package will be slipstreamed as pre-installed
      OS: Windows 7 SP1
      Notes:
      - The addon will conflict with some Windows Updates (.NET 3.5 Family), so leave the addon's integration to the last.
      - Add main addon first before LangPack addon, to get ASP.NET service localization properly.
      - To function properly, .NET 4.7.x require D3DCompiler_47.dll component, which is found in either the current "Monthly Quality Rollup" or "update KB4019990". It is recommended to integrate it first, or you can install it later.
      Windows6.1-KB4019990-x64.msu
      Windows6.1-KB4019990-x86.msu
      .NET 4.8:
      .NET 4.7.2:
      Languages Codes Reference:
       
    • By hkroiss
      Hi, since around 1.5 half years i am integrating Updates into our Windows Image at our Company. However i have noticed that even when all the latest Updates are integrated after installing the OS it shows a few ".NET Framework" Updates that couldn't be integrated (see Attachment). A year ago it were only around 10, now around 15. So its getting more and more, it hinders the usfulness of the Slipstreaming process a bit.
      Did anyone of you find a way to integrate this pesky ".NET" Updates into the Image?
      Thanks for the help.

    • By niTe_RiDeR_Pr0
      Adobe Shockwave Player v12.2.4.194 - Slim RePack [Installer]
      About RePack: Deleted Shockwave Player 10 files (that is required only is some old games/content) & improved/enhanced the compression (LZMA2). Reduced file size from 23.6 MB to 12.4 MB (11.2 MB Decreased). The installer source is Adobe's official distribution msi, so unlike the .exe installers, it DOES NOT CONTAIN ANY ADWARE/CRAPWARE/USELESS JUNK.

      Optional Command-Line Switches: 

      DOWNLOAD: https://mega.nz/#!YkhyDZRL!5eJLeCyKIdHyBFr3uYIKauybxn5HyBwJ2u6t78hs3Vs
      File Name:  ShockwavePlayer_12.2.4_Full.RePack.exe
      File Name: 12.4 MB
      File Hashes: http://pastebin.com/vP41LLC7
       

      Enjoy!

      Cheers & Regards...
×
×
  • Create New...