How does it show the content like the other servicing tools do? Or do you mean the xml file inside the wim/esd?
You can test it yourself by downloading the MCT or the upgrade tool, check the products.xml file for the ESD download links.
Thank you From what I understand, the MCT Tool has not been updated yet, so I just need to have more patience. The Microsoft ISO gives AIO. With ESD. I can get Pro only, which is all I need.
Download MVS consumer ISO, extract install.wim, export pro to a new install.wim or directly to an install.esd, replace original install.wim with install.esd and you have a Pro only iso with install.esd
I'm patiently waiting for the 2018 Windows 10 LTSC (latest LTSB) so I can upgrade to it. Running 1803 as 2016 LTSB kernel doesn't fully support my 8700k though, in reality, I doubt it really affects it much.
@KedarWolf there is no kernel modification in both version ,only Pro workstation has a little optimization
Updated the OP with @LostED's 17134.228 SHA-1 post and my 17134.228 SVF Repo: https://forums.mydigitallife.net/threads/windows-10-svf-repository.63324/page-123#post-1458478 All will soon be available at @s1ave77's download tool
I have this ISO but can't find products.xml for Pro ,esd en_windows_10_consumer_edition_version_1803_updated_aug_2018_x64_dvd_f2764cf8.ISO 5,080,262 kb
There is no products.xml on MVS iso's, if on any iso at all. It gets downloaded by the upgrade tool or MCT. It also exists in a .cab file. When it comes available (or IF), we'll see it published soon enough.
@whitestar_999 Regarding this: https://forums.mydigitallife.net/th...te-upgrade-process.64770/page-96#post-1458621 You are going thru a very specific scenario, involving 3rd party software and user intervention. What is the HWID based on, the MSDM (hardware bound) or manually generated for another sku then the original pre-installed oem one? Because i can figure that when the HWID is based on the MSDM the new hardware could be considered not original OEM anymore.
This laptop doesn't have any msdm info in uefi as it never came with any windows oem os.My guess is that either mak key activation of win 8.1 done via call is very strict or these "os migration to ssd" tools are not that perfect(which in my opinion is unlikely as it is nothing but C partition cloning with a few extras).
I never used MAK with call to msft. So you generated the HWID by MAK used outside it's terms of use? I don't have a laptop with a hdd bay to test but i do get a laptop to replace the hdd with a ssd and i am going to test the samsung clone software and watch the results. It has a MSDM for Home but i established a HWID for Pro and some other sku's. Lets see what happens (it should be brought to me this week).
Thanks for testing & let me know the result.One thing I would like you to test if possible is using a caddy to replace optical drive with ssd but I think it would be too much to ask.What you can test though is trying some free OS migration software(as long as it is mbr,for uefi I think only macrium reflect free works for os migration) & transfer/copy os to ssd connected via usb enclosure(aka test of both hdd & ssd being connected while using os migration software). MAK activation was allowed over phone call by MS earlier but now it is only allowed via online chat with a support agent & after successfully answering support person queries.Still the fact remains that original MAK activated install in hdd still remains activated irrespective of whether ssd is present or not(aka behaving like hwid).
To be clear, the MAK activation was on the 8.1 install? How did you generate the HWID for 10 (for 8 hwid doesn't work)?.