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

[ricktendo]

10-14-2014

Add: 2972106, 2979575

Rem: 2783767

10-15-2014

Add: 2996569

Rem: 2926986

[ricktendo]

11-11-2014

Add: 2978125

Rem: 2931365

[ricktendo]

11-25-2014

Add: 3013383

[rck]

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.

 

 

[ricktendo]

Was .net framework installed?

Check to see if ngen.exe is in that location

Maybe its a problem with your system that ngen is not being seen as ngen.exe

[rck]

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

[ricktendo]

I think its the fact that I don't put .exe, sometimes some computers don't have

PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC

Where it automatically assumes its one of

[ZEUS__]

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.

 

 

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.

 

 

 

[ricktendo]

Crap, forgot msp...

FIXED! (INTL did not have this issue so no change to this installer)

BTW you do know you only need .net 4.5.x if you are using Windows 7, I only maintain 4.x for XP users

[ZEUS__]

OK then,

yes I know, I just put it to my WPI archive.

[rck]

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

[ercofra]

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?

 

[ricktendo]

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}

[ercofra]

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

[ricktendo]

Even better!

[destroychip]

Silent "No GUI" SFX alternative v1.6 link has been dead

[ricktendo]

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

[destroychip]

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

[ricktendo]

Delete *x64.msi & *x64.msp files

Delete \Windows\System64\ & \Windows\Microsoft.NET\Framework64\ folders

No need to edit the SFX, just remove any *x64.msi commands from config.txt and you are good to go

[ricktendo]

1-14-2015

Add: 3031985

Rem: 2974335

[J.J.]

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)"?

[bphlpt]

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

[ricktendo]

It is compatible, only reason to use this post Vista is if your software is not compatible with 4.5.x

[J.J.]

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 March 6, 2015 by J.J.

[vyarthrot]

try....Net Framework step by step

 

Vyar