No, but if the install takes updates it's either a license switch install or manually tampered with the registry cbs info.
Is there any way to check the created ISO after the wim switch to verify it is 100% correct? I tried to use the wim switcher but it doesn't show anything, assuming that is due to the iso being mounted?
WES shows exactly what the result is, as shown here: https://forums.mydigitallife.net/th...o-for-workstations.74909/page-65#post-1413458 Code: Details for image : H:\Test\wes.v0.01.24\install.ProWork.wim Index : 1 Name : Windows 10 Pro-Work Description : Windows 10 Pro-Work Size : 10,628,200,010 bytes WIM Bootable : No Architecture : x86 Hal : <undefined> Version : 10.0.17107 ServicePack Build : 1000 ServicePack Level : 0 Edition : ProfessionalWorkstation Installation : Client ProductType : WinNT ProductSuite : Terminal Server System Root : WINDOWS Directories : 14961 Files : 77565 Created : 2/21/2018 - 8:38:24 AM Modified : 2/24/2018 - 2:05:32 PM Languages : en-US (Default) The operation completed successfully. Yours should show 16299.15 instead of 17107.1000
yes, use gimagex tool, run it then go to "info" tab, it will tell you if the conversion was successfull.
now since you use existing sku from install.wim, entering the key during the installation should work but not sure.
He already has a (linked) HWID why 16278 again? He just needs to create a pro-ws from 16299.15 home and install, enter the non gVLK from the product.ini and it will have the HWID again (or in his case sign in with the MSA).
no i wasn't talking about that, in one of your previous posts you said "Yours should show 16299.15 instead of 17107.1000" , i just said that it shoud show 16278.1000 not 16299 since he downloaded home 16278 version.
I just can't think of anything to say about this all. He has a HWID and installed 16299.248 and did the license switch. Why on earth would he create and install 16278 again? He wants 16299 Pro-WS, doesn't he?