The standard EnterpriseS does not have WindowsApps applications. For versions 19041 and before, Microsoft.SecHealthUI exists in SystemApps, and 22000 is placed in WindowsApps.
22000 currently does not have a separate Microsoft-SecHealth-UI-Package~31bf3856ad364e35~amd64~~10.0.22000.1, only "Microsoft.SecHealthUI_1000.22000.1.0_neutral__8wekyb3d8bbwe" can be used. In other words, when refactoring, just don't remove "Microsoft.SecHealthUI_1000.22000.1.0_neutral__8wekyb3d8bbwe".
22000 have no baseless LCU, and event LCUs dont have components packages for EnterpriseS too. so I think it can be hard.
Hi dear friend @hcvn First of all, I hope that you and all of you are safe and healthy now and forever, as are all forum members and families too. Thank you for your knowledge, But do you know how our friend @xinso did what is in the indicated post? I try but I can't understand how he got to that result... Thanks in advanced Regards
Microsoft-OneCore-DeviceUpdateCenter-Package~31bf3856ad364e35~amd64~~10.0.18362.1 Oh, it has been working in our systems for years. Really? Fact: I depends on whether or not this Product policy is being enabled, e.g. in 19044 IoTEnterpriseS. Code: DeviceUpdateCenter-Supported 1 Duc Update Agent Ocp Update Agent
Comparing 19044.1200 x86 LCU windows10.0-kb5005101-x86.cab (276,313 KB) windows10.0-kb5005101-x86-baseless.cab (43,673 KB) windows10.0-kb5005101-x86-baseless.psf (1,250,582 KB) windows10.0-kb5005101-x86-baseless (3,577,906,285 KB) windows10.0-kb5005101-x86-baseless-Full.ead (1,088,954 KB) windows10.0-kb5005101-x86-baseless-Full.cab (failed)
As usual, Reconstruction of official LTSC image structure does not remove anything but Store, for sake of LCU compatibility. Unless you are able to make custom updates for builds from 18362.1 forward.
Thanks everyone for comments in PM, I appreciate that. For myself the most valuable one was, that I don't need Server2022Eval to extract Microsoft-Windows-WLMS-Package and modify it, just take EnterpriseEval from 1904x, package is always 19041.1. Updated step-by-step. P.S. EntSNEval still cyclic reboot
With EnterpriseS and IoTEnterpriseS, the difference is 5 or 10 years of support now. But you don't need a separate ISO for IoT, take a normal Enterprise (or EnterpriseS) and change serial number. That's it.