You can do whatever you want with a product policy editor, but you loose the activation. Except the obvious SKUwitch, the only option I see to use a different language, is to patch the Chinese MUIs with the resources from a different language, or patch different language MUIs making them looking as Chinese
But PAE patch is obviously better, more practical With SKUswitch you can use any server SKU and you will get 4GB support (Instead of 3.x GB) not a lot but that works w/o patching anything and w/o loosing the activation.
Of course, I know these. But not everyone knows. Due to the RSA public key provided in xrm-ms, perhaps I can replace it with my own public key and sign it with the corresponding private key.
So Registry keys need to be changed ? like Code: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nls\Language English 0409 French 040c Spanish 0c0a Italian 0410 Swedish 041D Dutch 0413 Brazilian 0416 Finnish 040b Norwegian 0414 Danish 0406 Hungarian 040e Polish 0415 Russian 0419 Czech 0405 Greek 0408 Portuguese 0816 Turkish 041f Japanese 0411 Korean 0412 German 0407 Chinese (Simplified) 0804 Chinese (Traditional) 0404 Arabic 0401 Hebrew 040d Could you post other keys that need to be changed ?...
After some research and registry editing, I figured out how to get EnterpriseG on tr-TR. It can be updated but not activated. Spoiler: EnterpriseG tr-TR
The registry (unless @example12345678912345678 discovered something new) are always the same since nt4 are in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nls\Language and HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MUI The kernel policies may override/revert them like in case of enterpriseG or single language core If you change those policies either using a different SKU or the kernel policy editor those values are accepted. Changing SKU has the drawback of changing the whole set of policies (Say LTSC allows Defender, while enterpriseG does not) Changing the policies using the policy editor has the drawback that you must disable the SPP (and possibly the clip service), which means that after 6 hours or so you get the unactivated overlay. That's what I'm aware of, then is always possible that someone discovers a new brilliant way.
Code: \SYSTEM\ControlSet001\Control\ProductOptions ProductPolicy It is in binary type. If you scroll down enough, you'll see something like zh-CN;en-US. Replace it with EMPTY and you should be good to go.
acer-5100, I may ask you a stupid question, but still. The image has three SKU editions: the main one - EnterpriseG and two backup editions - Enterprise and IoTEnterprise. How or where in the install.wim image can I disable or remove some of the SKUs and leave only one, for example - IoTEnterprise ?
Use dism /export to export the image you want. You can also delete the unwanted images from the original WIM, but you don't recover the space this way, so export is the preferred option. If you're scared by the command line you can also use the wim management submenu in MSMG, but likely other DISM GUIs like dism++, dismtools and alike will do the job. Even the good old GimageX has the export option.
You misunderstand me. I know what DISM is and how to use it. I was talking about something else: the image has one edition SKU - EnterpriseG (one edition with index 1). But the image has two more backup SKUs that have nothing to do with the main edition of the image. You can use the activator to switch between these SKUs and get a completely different edition, for example, IoTEnterprise. So, I was wondering where these SKUs are located in the image, so that I could remove the SKUs I don't need from the image. Not the edition, it is in the image one index 1, but SKUs which are in the image three. upd.: I found myself in a quandary: with the Windows editions out there, it's simple and straightforward. But with these SKU's it is not clear to me at all.
Those, say one WIM image that contains LTSC and IOT LTSC, aren't images are virtual editions (practically no space wasted), the only thing that make them different are the certificates in the \system32\spp folder. Delete the SKU folder you don't want, do slmgr /rilc and your additional SKU is gone. Practically (if I got correctly your question this time) you want to do a reverse SKUwitch procedure, possible but pointless IMO.
It finally got to me, like along the long neck of a giraffe - on the seventh day. I put those SKUs into the spp myself and completely forgot about them. It turned out to be very simple, problem solved. Thank you very much for your very helpful hint, kind person!