ESU bypass for Windows POSReady 7?

downgrade from windows 10 ltsc to 7 => clean install

upgrade from posready 7 to win10 ltsc clean install

upgrade not works !

 

The bypass only allows to install 7 posready updates manually. WU will show the updates but will not install them.

 

BypassESU v11 worked on POSReady 7,but cannot get hotfixes after October 2021 through Windows Update(though you manually installing them)
It seems that the original author may have not take this version into consideration?

 

The Embedded version cannot upgrade to client version...

 

https://forums.mydigitallife.net/posts/1696622/
https://forums.mydigitallife.net/posts/1630914/

 

Thanks,I have not read that before

 

Is this still the latest news?

 

Yes, apply to POSReady 7 too

the only way to override this is to create "in memory patcher" for wuaueng.dll, similar to WuaCpuFix
but that's out of my scope

 

Thanks man , just one question , ignored wuaueng.dll can I manually Integrate updates and USB3 drivers to the install.wim as following

Examples:
Code:
- Integrate updates into one index:

Code:

UpdatePack7R2.exe /WimFile=C:\win7\install.wim /Index=5

- If you want to specify your own folder for mounting the install.wim(default folder is on your system partition):
[code]UpdatePack7R2.exe /WimFile=C:\win7\install.wim /Index=5 /Temp=N:\examlpe\your_folder
- Integrate updates and USB3 drivers and reduce the final size of the install.wim:
Code:
UpdatePack7R2.exe /WimFile=C:\win7\install.wim /Index=5 /Optimize
- Integrate updates and enable Spectre/Meltdown protection:
Code:
UpdatePack7R2.exe /WimFile=C:\win7\install.wim /Index=5 /FixOn

 

nope

 

Managed to mock up a patch, still prototype (patched sppwmi.dll + redirected slc.dll)

however, apparently sppsvc.exe itself uses sppwmi.dll for various checks, and the new patch/hook will make it slower relatively
don't know if it worth the trouble, or it's best to just use WSUS proxy

it would be more professional to hook fastprox.dll and fake wmi query result, but that too difficult for me

 

- sppvc.exe slowness (high cpu usage) is not caused by hooking itself into slc.dll or sppwmi.dll
but it depend on the WMI query parameters, and the number of installed productSkuId licenses

- productSkuId licenses:

represent the installable keys allowed (e.g. KMS, OEM SLP, or ESU key...)

SkuId's for Windows 7 out of the box:

Code:

Starter 11
HomeBasic 11
HomePremium 15
Professional 20 (+3 for Win8/8.1/10 CSVLK)
Ultimate 12
Enterprise 10 (+3 for Win8/8.1/10 CSVLK)

then, the era of ESU arrived
each ESU Year license adds 3 SkuId licenses = total 18 currently (even on unsupported editions)
Server get extra 2 SkuId licenses for Premium Assurance

for unlucky up-to-date edition like Professional, now it would have 41 SkuId licenses

- WMI query parameters:

when you query for all (or multiple) properties for multiple SkuId's:
software protection (sppvc.exe) check all properties for all SkuId's
each SkuId iteration calls SL functions 45 times (at least)
so, this will take considerable time and high cpu usage to finish

such long slow behavior don't occur if you query for:
all (or multiple) properties for single SkuId
single property for multiple (or all) SkuId's

- Windows Update metadata use the 1st slow scenario unfortunately
it verify ESU keys for "Embedded" or "For Embedded Systems" using generic unoptimized query

Code:

"Select * FROM SoftwareLicensingProduct WHERE (multiple IDs) AND PartialProductKey IS NOT NULL"

and it's repeated for each ESU year, that's triple the cost

this verification occur at the beginning of each new scan
although, sometimes if you do multiple scans in the same session, the verification results are cached and only evaluated once

- redirected slc.dll, or avrf hook for wmiprvse.exe would add very little overhead to the process

- p.s. using KMS_VL_ALL AutoRenewal makes things worse and double the check time