For 19044 Enterprise LTSC reconstruction with non-initial packages, it is OK to resetbase without integrity violations. But, the LCU being integrated and "resetted" will have integrity violations issue, even though it will be fixed up by upcoming LCUs down the track.
Code: <selectable disposition="absent"> <detectNone default="true" /> </selectable> Code: <selectable disposition="absent"> <detectNone default="true" /> <mum2:customInformation xmlns:mum2="urn:schemas-microsoft-com:asm.v3"> <mum2:EnableSelectabilityForEditions> <mum2:EnableSelectabilityForEdition name="Microsoft-Windows-IoTEnterpriseSEdition" /> </mum2:EnableSelectabilityForEditions> </mum2:customInformation> </selectable> These two are interesting things. The first one is non-specific, and the second definition specifically refers to "Microsoft-Windows-IoTEnterpriseSEdition". When we remove the defined packet, it does not affect the update。 It can also be removed through cumulative updates (not customized), or manually.
Hint: 1. "22000.1" EnterpriseG has the working feature. 2. If you apply 19044 IoT LTSC Certificates to it, it has the working feature too.
It is the definition of a registry key value, ff and 1, do not do processing, 0 is to remove the corresponding package.
For 20348.1 ServerTurbine Reconstruction, DO NOT reset the reconstructed image base. (The image footprint won't get greater because there are few small packages changed only.) Then, the image base with LCU integrated can be resetted without integrity violations issue upon completion of installation..
ff and 1, do not do processing 0, to remove the corresponding package Good. I'll have it a go someday. Thanks.
1. Official ISO? Really. I have not tested them yet. 2. I have no idea. My 20348.1 ServerTurbineCor and ServerTurbine have no such issues. And, the ServerTurbineCor does not use LCU patch. 3. No. It does not matter.
Thank you! 1. Yes it is! Most of them (except 19041.1 or 19041.264, As some one report that) Spoiler https://forums.mydigitallife.net/threads/msmg-toolkit.50572/page-871#post-1630174 3. Okay!