I will check the original reg entries in the 20348.681 wim
Very strange if it's not there because it would have been there after the packages were added and windows edition was set to EntS.
This reminds me of the problems I encountered when I made 25398 AzureStackHCICor with GUI.
I will check the original reg entries in the 20348.681 wim
Very strange if it's not there because it would have been there after the packages were added and windows edition was set to EntS.
This reminds me of the problems I encountered when I made 25398 AzureStackHCICor with GUI.
Have you got it yet? I used the ISO 20348.681 from my friend @dungltcd so I got it after following instructions from you guys. By the way, could you show me how to update to 3566?
If you want to update the 20348.681 wim offline using @2012mshs update tool - the tool might need to be modified because the msu contains a cab which has a cab1 and cab2.
Please post your results because it may not upgrade if the fix was applied to 20348.681. If that is the case then you have to upgrade the 20348.681 first to 20348.3561 and then apply the fix for the dism problem.
If you want to update the 20348.681 wim offline using @2012mshs update tool - the tool might need to be modified because the msu contains a cab which has a cab1 and cab2.
Please post your results because it may not upgrade if the fix was applied to 20348.681. If that is the case then you have to upgrade the 20348.681 first to 20348.3561 and then apply the fix for the dism problem.
Excellent.
Use HEU_KMS_Activator to get a digital license.
What would happen if we apply the dism fix to the 20348.681 build and then try to upgrade ?
This will be the ultimate proof that it will be able to upgrade in the future without problems
Excellent.
Use HEU_KMS_Activator to get a digital license.
What would happen if we apply the dism fix to the 20348.681 build and then try to upgrade ?
This will be the ultimate proof that it will be able to upgrade in the future without problems
For what I know EditionMatrix will get overriden by the new CU Update and only the registry edits will remain so you'll need to again modify the EditionMatrix to make it work since the EnterpriseS edition gets removed from EditionMatrix upon update and only the Server editions remain in it.
I did try to edit the EditionMatrix file, remove Server sku, rename EntS sku, run slmgr /rilc again, then enter key YY74H, I got IoTS edition again but not yet activate:
But I still can not activate for IoT-S, it shows like this: