How does that answer the question about activating Cloud aka S? Cloud is pre-installed on specific devices, it will only be activated by MSDM, because no cmd's or exe's can run, KMS activations also don't work. Maybe connecting to an external KMS server will work?
Yes, I was about to delete my post after but MDL forums don't allow post deletion. Thanks for explanation.
No Volume:GVLK range is defined for Cloud SKU as of now, so you can't even generate GVLK for it. Regarding connecting to external KMS server, you still need to set the KMS server address (provided this SKU has KMS capabilities and the emulator can't broadcast its address in the network) which needs to be done externally by loading the registry hive as slmgr (or the underlying WMI shell) should be inaccessible in it. @Saurav You can report the concerned post so that mods can do it for you.
@Aty Good finding; Cloud is nothing but a stripped down Pro. Even the edition infos are same for both.
You can also see it when converting UUP>ISO for cloud, Cloud can be offline upgraded to most editions too. Wasn't there a post somewhere which shows there is a switch somewhere which locks Pro down to store apps only?
I am also testing atm, just installed S on my testsystem with HWID's for pro and home + both N versions. After clean install it shows Pro, activated by Digital License but it has the S restrictions, now updating. Addition: After updating it now shows Windows 10 S, activated with a Digital License. Addition 2: After inserting the generic Pro key it switched to Pro and still the S restrictions.