Code: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\C28643E881181F13CBC489DC69571E2C\Patches\79EB7C9295ED2A736A78A2DD351249A8
Also since you are doing this you should also hide Client update KB2539636 (patch ID BCD73DCB974FD4D39AE00A7F7555944C on x64).
Hi, just a quick question; I used burfadel's install script and selected to process all updates (option 1) for Solor's update pack (Have updated it according to changelog) and I noticed that there are double copies of certain updates e.g. KB982018 and KB982018_BF. This is on a fresh copy of Win7 SP1. Is this normal or have I done something wrong? Sorry if this has been asked before.. Cheers
hm... not sure why hiding this patch doesnt not work for me.... hiding KB2468871 works as it suppose to but KB2539636 still shows up on WU.
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?
First file name: C:\Windows\winsxs\amd64_microsoft-windows-mfc42x_31bf3856ad364e35_6.1.7601.21680_none_5174bfdf85884160\mfc42.dll Second file name: C:\Windows\winsxs\amd64_microsoft-windows-mfc42x_31bf3856ad364e35_6.1.7601.21774_none_518392d9857c87f2\mfc42.dll 925194 : 925194 Byte(s) diff 470518 Byte(s) match 1395712 : 1395712 Byte(s) total First file name: C:\Windows\winsxs\amd64_microsoft-windows-mfc42x_31bf3856ad364e35_6.1.7601.21680_none_5174bfdf85884160\mfc42u.dll Second file name: C:\Windows\winsxs\amd64_microsoft-windows-mfc42x_31bf3856ad364e35_6.1.7601.21774_none_518392d9857c87f2\mfc42u.dll 1108884 : 1107860 Byte(s) diff 250988 Byte(s) match 1359872 : 1358848 Byte(s) total in case of mfc42u.dll even size doesnt match
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)
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
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