@abbodi1406 KB2603229 & KB3046269 KB2603229 will correct HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\currentversion\RegisteredOrganization HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\currentversion\RegisteredOwner But when I install other patches except KB2603229，The above registry will still be corrected，So there is no need to install it again KB3046269 addresses the vulnerability by ensuring that the known invalid Windows Defender task is either not present on or removed from affected systems. But after I installed this patch, the tasks has not changed
@DUT microsoft-windows-shell-comctl32-v5_31bf3856ad364e35_6.1.7601.23039 microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.23039 those two provide different functions, even if comctl32.dll is the same in both KB3059317 is the only/last update that have the second component KB3046269 remove the tasks only if WD is active (not disabled)
I know they are different emmm。 Actually，when I installed KB3125574/KB4556836,then installed KB3059317 the files in winsxs： winsxs\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.24483_none_e372d88f30fbb845 file version：6.10.7601.24483 winsxs\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.24483_none_2b200f664577e14b file version：6.10.7601.24483 winsxs\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.23403_none_e36ad4593102f066 file version：6.10.7601.23403 winsxs\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.23403_none_2b180b30457f196c file version：6.10.7601.23403 winsxs\amd64_microsoft-windows-shell-comctl32-v5_31bf3856ad364e35_6.1.7601.23403_none_98555f8107adb131 file version：5.82.7601.23403 winsxs\x86_microsoft-windows-shell-comctl32-v5_31bf3856ad364e35_6.1.7601.23403_none_3c36c3fd4f503ffb file version：5.82.7601.23403 It seems that KB3059317 did not take effect
Dear @abbodi1406,for KB3059317, I did two tests test 1，I installed KB3125574,then installed KB3059317 test 2，I installed KB3059317,then installed KB3125574 Then I copied the comctl32.dll separately from C:\Windows\System32 and C:\Windows\SysWOW64 to another folder The comctl32.dll in C:\Windows\System32 version：5.82.7601.23403 619KB The comctl32.dll in C:\Windows\SysWOW64 version：5.82.7601.23403 518KB The comctl32.dll in C:\Windows\System32 is same as the comctl32.dll in winsxs\amd64_microsoft-windows-shell-comctl32-v5_31bf3856ad364e35_6.1.7601.23403_none_98555f8107adb131 file version：5.82.7601.23403 The comctl32.dll in C:\Windows\SysWOW64 is same as the comctl32.dll in winsxs\x86_microsoft-windows-shell-comctl32-v5_31bf3856ad364e35_6.1.7601.23403_none_3c36c3fd4f503ffb file version：5.82.7601.23403 Test 1 and Test 2 are both such results But if I view the properties of the comctl32.dll in C:\Windows\System32，instead of copying it to another folder The version of comctl32.dll in test 1 is 5.82.7601.17514 The version of comctl32.dll in test 2 is 5.82.7601.18837 Then I used the hash tool to view the properties of the comctl32.dll in C:\Windows\System32 / C:\Windows\SysWOW64 / x86_microsoft-windows-shell-comctl32-v5_31bf3856ad364e35_6.1.7601.23403_none_3c36c3fd4f503ffb file version：5.82.7601.23403 The results show that the properties of the comctl32.dll in the above these folders are exactly consistent This is a really strange result！ But I found that the comctl32.dll 5.82 is always associated with the comctl32.dll 5.82.7601.23403，instead of 5.82.7601.18837 and 5.82.7601.23039
@mattew, it's probably not good to use the ESU bypasses this way, it has to do some licensing stuff to get the ESU updates into the, officially, unsupported HomePremium. I would just use simplix update pack or W7ESUI to offline integrate the ESU updates. Maybe @abbodi1406 has a solution for you.
@DUT thanks for the tests i think it would be safer to just keep KB3059317 @mattew Home and Starter editions are changed n registry to Professional to recieve ESU updates via WU it's not advisable to create sysprep image of it remove WU ESU patcher before sysprep then use Wim-Integration.cmd to integrate WU ESU patcher into install.wim
is it possible to hide updates kb4493132 and kb976932? Exist a script that i can integrate to install.wim?
Is there a list of updates known to contain telemetry crap? I'm rebuilding the ISO and want to avoid them
Sorry, but I don't know ... In particular, I use Simplix's UpdatePack and MDL Win 7 Tool for SiMPLiX UpdatePack AiO ISO (with install.wim/esd) Creation v2.0 de Enthousiast. I'm very pleased!
From a decade long Windows 7 user, I've never seen they release a new SSU that often! Is that the only way to update a Win7 machine which last updated in 2 years ago is to update everything to Jan 2020, then install Rollup/Security Only Update from Feb and follow by SSU from Feb and repeat the steps with Rollup/Security Only Update and SSU from March to June? Thanks!
latest SSU is enough and latest Monthly Rollup / .NET Rollup if you are Security Only Update user, latest SSU is also enough, and latest IE11 cumulative but you need every security only update
After a clean install with an ESU ready wim and adding .NET with NET Framework 4.8 Slim which includes KB4532941 from 2020-01, I am still being offered 4532941 even though it seems to be in installed correctly registry wise. Shouldn't I have been offered 4552921 from 2020-05 instead, which I thought replaces 4532941?