Windows 10 retail usb image.

Just add ignore option to this forum for some users and nerds like him will disappear real quick. If you call some1 a theif,liar without proof you should be punished thats as simple as that. I have nothing to hide and posted everything i know. The only thing i want is for my stick that i bought to get updated. I contacted microsoft directly they said they dont have this image and if i want them to make it public i should submit ticket. Right now all i can do is either pay again which i wont cuz i already bought it once or ask people around forums to help which is what im doing.

In case of install.swm files i suspect that the msft compression is different. Because when i used tools here on forum i could not get the same install.esd i would get after converting it ESD file with mct thats just an example. Its hit or miss based on images unless some1 with the stick will upload those files so we can compare sha-1 and dism getwiminfo. When there is no compression involved then like in case of my 1607 install.wim stick i had exact same sha-1 as msdn iso's.

 

Once media creation tool creates usb it downloads ESD file to C:\ESD and after its done and verified its called installx64.esd. When i check it with dism getwiminfo i get it has winpe enviroment as well as images that are present in normal install.esd later on the disk. I tried to copy that installx64.esd to separate folder and i used the tool that is here on forum with options 1. include all editions 2. create install.esd later it was automated. In the end what media creation tool creates is different than what this forum tool creates when comparing sha-1 files. I dont know what the difference comes from but as its connected with comperssion that i know nothing about i bet on that.

 

Is the install.wim size the same as both install.swm files summarized?

 

You need to login to view this posts content.