Windows 7 Hotfix repository

This works for me to silence WU about KB2539636:

x64:

Code:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Updates\Microsoft .NET Framework 4 Client Profile\KB2539636]
"ThisVersionInstalled"="Y"

x86:

Code:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Microsoft .NET Framework 4 Client Profile\KB2539636]
"ThisVersionInstalled"="Y"

Of course it would be great/best to have this included in the .mst's Ricktendo is working on, but we could also add in and run reg tweaks with the installer if need be.

 

That's fine! In the example for KB982018, the update just labelled KB982018 is the GDR(or LDR only) component, and the KB982018_BF is the force LDR update component. When installing, both the KB982018 and KB982018_BF components need to be installed for 'consistency'. The LDR stream is the 'higher level of updatedness' stream, which is the one you want to be using (and is the one utilised when the '_BF' version of the update is installed where available).

 

So to summarize, this is all I need to silence WU on KB's 2539636 and 2468871 for NET4 Client (just tested on x86 and x64 Win7):

x64:

Code:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Updates\Microsoft .NET Framework 4 Client Profile\KB2539636]
"ThisVersionInstalled"="Y"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\DFC90B5F2B0FFA63D84FD16F6BF37C4B\Patches\79EB7C9295ED2A736A78A2DD351249A8]
"State"=dword:00000001

x86:

Code:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Microsoft .NET Framework 4 Client Profile\KB2539636]
"ThisVersionInstalled"="Y"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\5C1093C35543A0E32A41B090A305076A\Patches\4A3FC9E53BDA08038AFB79A682437085]
"State"=dword:00000001

 

Quite right the file versions and sizes are the same for both dates, however KB2584577 does have newer file dates. Without doing a side by side comparison, I suspect if you do a file compare of the two updates you'll find they are different. The versioning of the files is different to the normal Windows components.

mfc42.dll, mfc42u.dll
6.6.8064.0

KB 2566205-v2 ntoskrnl.exe LDR file version
6.1.7601.21789

See how the mfc42.dll & mfc42u.dll don't have a build number specified?

 

ok thanks for the explanation

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

Do you mean AIO x86/x64 or FULL x64, in both cases you need ALL the files and subfolders because the x64 installers (for compatibility reasons) install both the x86 and x64 files...doing a second admin install (uniextract to subdir) will grab all the files each installer needs, if you are doing only x86 or only client the admin install will leave the unneeded extended or x64 files behind

This is also how you do an admin install (you can also apply the transforms during your admin install and you wont need to aggain)

Code:

<msi_name>.msi TARGETDIR=C:\dotNet4

w/ transform

<msi_name>.msi TARGETDIR=C:\dotNet4 TRANSFORMS=<mst_name>.mst

BTW you install the netfx_core_x*.msi first, followed by netfx_extended_x*.msi (use either x86 or x64 installers not both)

 

You need to login to view this posts content.

 

Mine does not have any updates other than KB971891 applied (so you can integrate LDR files) to it & its not packaged as a SFX silent installer, you apply SoLoR's updates yourself and manually run each installer

 

You need to login to view this posts content.

 

Did you install both client+extended and if so did you apply both MST's?

Can you post the reg you added to clear it up

You know sometimes after a fresh install of .net4 updates show up in WU, you have to rescan for updates to be sure

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

Should work with the standard package as well

BTW I hope the KB2468871 fix does not cause the update to be blocked even if you dont integrate the MSP's, I know the KB2539636 fix wont cause an issue because the "trick" will only work if you add a equal or superseding hotfix...this is why I would have not applied the MST's to the default package, I would have applied them when they ran the CMD to update (not much of an issue, just saying)

But I guess its easier on the everyday user this way

 

You need to login to view this posts content.