You must have the sku folder from the same "family" and the newest one available is from 1809 which doesn't work on 2022
using windows 10 enterprise 19041 + EnterpriseS ( certificate shared by @xinso ) + adding SSU + LCU are the Good ways ?
I didn't follow the thread, but, why don't try yourself? Copying SKU/Branding + Slmgr /rilc + slmgr /ipk takes less than one minute of your time. In the worst case the new key is not accepted, that's all
I use it that way you said. I always use the latest Professional version, in my language. So far everything works very well!
Thank you , My method are original based by @whatever127 jobs Thank you @SunLion Your method are more simple
Q: Why 22000 Windows 11 won't show correct IoTEnterpriseS ProductName for some language? It is caused by basebrd.dll.mui, and unknown reason. e.g. en-US ---> Windows 10 IoT Enterprise LTSC zh-CN ---> Windows 10 IoT Enterprise LTSC zh-TW --> Windows 10 Enterprise LTSC --> zh-CN modified to zh-TW --> Windows 10 Enterprise LTSC
Still have not figured out the meaning of "<mum2:EnableSelectabilityForEdition name="Microsoft-Windows-IoTEnterpriseSEdition" />"? After this, what should be the next step? Spoiler
Dism++ recongnizes IoTEnterpriseS as EnterpriseS. (Off-Topic) In Microsoft-Windows-Common-RegulatedPackages-Package Media Feature is gone from Feature menu and system (but files are still in WinSxS) Code: <selectable disposition="staged"> <detectNone default="false" /> Media Feature is re-installed and appeared Code: <selectable disposition="staged"> <detectNone default="true" /> Of course, this is not the way of IoTEnterpriseS. [Inspiration from "Media Feature is gone from Feature menu and system (but files are still in WinSxS)"] This can be used as new "Lite" solution, because the system structure has not been changed, alike Features.
What's that? It works ONLINE? It doen not make sense... Missing Code: <source location="Microsoft-Windows-EnterpriseSEdition~31bf3856ad364e35~amd64~~10.0.22000.1.mum" />
Because there is no feature enablement package, you need to manually install "Microsoft-Windows-EnterpriseSEdition" again.