https://forums.mydigitallife.net/th...view-build-15031-pc.73093/page-8#post-1317758 It's the same, only use enterprise N or pro N as source (and the correct key for GN). Don't forget to set the sku flag to "EnterpriseGN" when you're done. Code: imagex /flags "enterpriseGN" /info "x:\install.wim" 1 "Name" "Description" "Name" = desired index name "Description" = desired index description ps, on win 10 you have to install ADK to be able to use imagex commands and use the dism tool from the ADK.
I get this. Deployment Image Servicing and Management tool Version: 10.0.15063.0 Error: 2 Unable to access the image. Make sure that the image path and the Windows directory for the image exist and you have Read permissions on the folder. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
You'll need to mount the WIM first, then set the edition, unmount and set flags in the WIM directly (needs no mount).
You mean this: https://forums.mydigitallife.net/th...-insider-preview-build-14901-pc-mobile.70772/ ? It's the first rs2 pre_release.
I found an old Pro 14901 en-us x64 iso of mine, if you're interested, convo me It has dotnetfx3 enabled, DaRT10 and dx9c onboard plus murphy78's diskpart image and apply script 1.2.8 in boot.wim
Actually I wanted the original IP of Creator's Update. I wanted to see if I could convert Enterprise to EnterpriseG w/o the BSOD which occurs with the March Update. EnterpriseN to EnterpriseGN works fine, but not the regular Enterprise.
That one is promoted at the OP of this thread. https://forums.mydigitallife.net/th...date-final-15063-pc.73650/page-2#post-1328969
I couldn't get it to download and it's not an official iso. You can do it easily by yourself, take the 15063 enterprise or pro zh-cn iso and set-edition it offline to enterpriseG like i showed here: https://forums.mydigitallife.net/th...view-build-15031-pc.73093/page-8#post-1317758 (and i didn't show how to mount the wim (first step)).
The BSOD is a result of the enforced language restriction (zh-CN only), which is a part of kernel licensing policy. It happens with CoreCountrySpecific SKU too - nothing new.