Right, but to establish one one must be on one of between these builds in order to get a HWID if one never had it before, and that's what i did but i will try to clean install a non insider preview of Pro WS and see if can still get the HWID i got when i activated the insider preview with the generic key, but how do i obtain a copy of Pro WS non insider preview ?
As refrained regularly, no matter the source (UUP/ESD/ISO) all will result in exactly the same system. Equal what was used no need to re-install anything. Just wait for the next Cumulative Updates to fix some bugs.
After a machine got a HWID for any edition, it will automatically re-activate on any fresh install of that edition (no matter what build) on that machine. Only Hardware changes can trigger deactivation. The just released ISOs contain the ProWork SKU now .
Very good point, but let's just say that the ISOs that contain this ProWork SKU weren't released yet, how could i get a stable (non insider) version of ProWork knowing that i have a HWID and on insider preview ring 16281 to be exact?
Install Pro and license switch to ProWork or convert a mounted WIM file. A ProWork install can be upgraded with the Pro ISO. As said only the Techbench or the MVS ISOs will contain ProWork and ProEdu. The ESDs (which are used by MCT) do not contain it.
Hi, I downloaded latest version of W10 from post #2 of this thread, but once installed, it tells that the current system version is = Windows 10 x 1803 build 17134.1 But, the link contains, as I understand, the 1804-180410 version (17134.1.180410-1804.rs4). Details: -> Windows 10 Pro x64 (es-es) [VL] I'm wrong with something? Thanks!
The 1804 is the date or time of creation, 17134.1 = 1803 (prolly some MSFT intern/employee having fun with code )
@abbodi1406 , I did try using strings at first, but it's not working for me (no output at all). That's why I decided to publish the other method.
An ISO built from ESD has a different size as the ISO downloaded using MCT, the main difference being the size of "install.esd" from "sources" folder. Are they actually the same thing?
MCT converted iso's have install.esd, when you select "create ISO with install.esd" using @abbodi1406 ESD>ISO tool, it also will have an install.esd too, when you select "Create ISO with install.wim, it will contain a wim, official MVS/VLSC iso's will contain install.wim. Install.esd is a compressed version of install.wim, approx. 30% less in size.
The ISO built from ESD using "Create Full ISO with Compressed install.esd" and the ISO downloaded using MCT both have "install.esd". But why are they different?
wimlib has better compression ration than dism nevertheless, i think MCT only delete the first 3 indexes after extraction/creating boot.wim