Jump to content

Recommended Posts

Posted (edited)

As a test (Win7 VM), I installed the original .net 4.5 installer (from here: http://www.microsoft.com/en-us/download/details.aspx?id=30653 ).

Then after a restart, checked Windows Update and only got a list of 9 updates to install:

KB2737083

KB2742613

KB2750147

KB2789648

KB2804582

KB2805221

KB2805226

KB2833957

KB2840642

This differs quite a bit from the list of updates you include in your repack.  In fact, KB2519265 doesn't have any M$ page associated with it and isn't available from anywhere other than McRip's archives.

Edited by Mr_Smartepants
Posted

(* = LDR/QFE patch)

KB2519265 comes inside .net 4.5 LDR hotfixes (like KB2848798,) it patches the .net 4.5 MSI to receive LDR files (it changes the ProductVersion from 4.5.50709 to 4.5.50710)

If you don't patch .net 4.5 with KB2519265 then hotfixes like KB2848798 will fail, adding KB2519265 also forces security updates like those you list (which contain both QFE and LDR sets of files) to use their LDR files vs the default GDR

If you only want security fixes (no bug fixes) stick with what WU offers, if you want a more complete list with all possible updates use mine and McRip's

  • 5 weeks later...
Posted

Hi,

 

I'm not able to download Rebuilt Microsoft .NET Framework 4.5 Full x86/x64 Incl. Language Packs,

please can you post a working download link

 

  • 1 month later...
  • 2 weeks later...
Posted

Rick, if I were to extract the rebuilt 4.5.1 exe file and silently install how is it done now?

 

Prior to 4.5.1 I've been doing this:

"%appdir%\output\netfx_Full_x64.msi" EXTUI=1

 

Thanks!

Posted

No, if you are using rebuilt best try (this is what is called when you run the installer) setup.exe /x86 /x64 plus the other switches as needed (run with /? to find them)

I recomend maybe also adding /trainswap to tell it to install the LDR branch

BTW Individual LP's and INTL installers are up

Edit: @biatch, you may also need to add /redist switch as well

rn5b.png

  • 3 months later...
  • 2 weeks later...
Posted (edited)

Rick, I'm confused.  For almost 2 1/2 years all of your .NET packs have always been named something like:

dotNetFx45_Full_x86_x64_xxxxxxxxxxx.exe

but now the downloaded files from the first post are named:

NDP451-KB2925430-x86-x64-AllOS-ENU_REPACK.exe
NDP451-KB2925430-x86-x64-AllOS-INTL_REPACK.exe

 

The last file of yours I downloaded with a similar naming format was in Dec. 2011 - NDP40-KB2599651-x86-IA64.exe.

Are you changing naming scheme? If so, why and can you please explain how your various packs will be named? TIA

 

EDIT:  It seems that the "guilty" party is MS.  They have changed their naming scheme and Rick is merely following it to be consistent with them.  He just adds "_REPACK".

Cheers and Regards

Edited by bphlpt
clarify naming

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.

×
×
  • Create New...