Did you install LPP KB4575903? can you show this command result? Code: reg query HKLM\SOFTWARE\Classes\CLSID\{6ACB028E-48C0-4A44-964C-E14567C578BA}\InprocServer32
abbodi1406: A fresh clean install of Windows 7 Professional SP1 64-bit was done in this specific desktop on February 17, 2023. My DVD install media had been created with this ISO file: and with the Simplix Update Pack for February 2023, along with its add-ons: Today was the first time that Windows Update was deployed to see if it would detect and install the March 2023 updates. The new KB5023769 security monthly quality rollup failed to be detected, even after deploying Win7_WU_ESU_Patcher for Windows 7 Embedded, so I manually installed it.
Update: On this specific desktop, the July 2020 KB4575903 ESU LPP update is installed. However, the August 2022 KB5016892 ESU LPP update is NOT installed. Should I install the newer version and then reboot and then load Windows Update and see if it works properly?
LPP KB5016892 is needed only for Server 2008 category (although you can install it anyway) what's the reg query command result? or this command: Code: wmic path SoftwareLicensingProduct where "(ID='4f1f646c-1e66-4908-acc7-d1606229b29e') and PartialProductKey is not null" get /value
I checked one of my other desktops that had Windows 7 Professional SP1 64-bit installed in it in July 2020, and Windows Update does the same thing. The KB5023769 SMQR update manually installed in it just fine. I have no problem with doing a manual install every month, so I am not going to make a big deal about this. Thanks for your help anyway.
Hello, friends! Some fiddeling this time for me but a little of tial and error i am running again. I've got all the updates. Windows 7 is by far the best OS ever ! Thank you boys for BypassESU v12_u + WU_ESU_Patcher Best wishes from Benny in Sweden.
Among undocumented issues is that the supersedence and detection are seen differently in WSUS than in Windows Update even after importing KB3125574 in WSUS. However, I take your recommendation on board and not investigate any further, while using Windows Update as reference.
Interesting and very useful to know. I have always thought that WU does metadata supersedence as well. A bit late now because Windows 7 is on its last legs while the current versions of Windows 10/11 have already moved on.
I only ment for KB3125574 case only WU indeed does metadata supersedence, for published updates WU don't have or get any metadata for KB3125574, installing it manually don't make a difference while WSUS get all the metadata (listed superseded updates) when you import it
Thanks for clarifying. Edit: The interesting thing is that for KB3125574 the catalog actually has supersedence metadata documented which is reflected in WSUS after importing (supposedly, as I have never compared the information in both). Because it is not offered directly on WU, it behaves in this peculiar way which you mention and which makes complete sense.