If thats true, then theres something seriously wrong with my PC. So just to make sure, did you actually rename the iso yourself then?. Last question then, did you try to extract an x64 iso from MCT?, without the errors i got?, (7z/MSMG) Because im somewhat sure that its because of the extraction errors it wont work with the MCT ISO.
That worked: Code: =============================================================================== MSMG ToolKit - Extract Source from DVD ISO Image to <DVD> Folder =============================================================================== ------------------------------------------------------------------------------- ####Starting Extracting Source from DVD ISO Image to <DVD> Folder############## ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- ####Getting DVD ISO Image Options############################################## ------------------------------------------------------------------------------- Enter the ISO Image file Name : Windows15063.MCT.x86.en-US ------------------------------------------------------------------------------- ####Extracting Source from DVD ISO Image to <DVD> Folder####################### ------------------------------------------------------------------------------- Extracting DVD ISO Image Contents to Source <DVD> folder... Extraction May Take Some Time, So Please Wait... Extraction Failed... ------------------------------------------------------------------------------- ####Finished Extracting Source from DVD ISO Image to <DVD> Folder############## ------------------------------------------------------------------------------- =============================================================================== Press any key to continue . . . Only converting the install.esd to install.wim doesn't.
If you get the errors in extracting the MCT Image using 7z then definitely the image is corrupted and can't be read in any tool. The Windows MCT created Image is a ESD Compressed Image with an .WIM extension and the ToolKit converts it without any issues unless the image is not corrupted while downloading or when it's created. Just to test I have used a dummy esd image with an .wim extension and the conversion works Code: =============================================================================== MSMG ToolKit - Convert Windows Media Creation Tool Image to WIM Image =============================================================================== ------------------------------------------------------------------------------- ####Starting Converting Windows Media Creation Tool Image to WIM Image######### ------------------------------------------------------------------------------- Deployment Image Servicing and Management tool Version: 10.0.16190.1000 Exporting image [==========================100.0%==========================] The operation completed successfully. ------------------------------------------------------------------------------- ####Finished Converting Windows Media Creation Tool Image to WIM Image######### ------------------------------------------------------------------------------- =============================================================================== Press any key to continue . . .
Microsoft is spamming me with corrupted images then, that seems to install windows fine too. This is just weird, it mounts fine as an ISO as well, but it throws that error every time, no matter how many times i re-download it
I haven't checked with the latest MCT images But At first when the MCT was introduced it was .wim right, I had checked with few images and had coded it.
Long, long time ago In the past the single architecture created iso's contained install.wim but the multi-architecture iso's already contained install.esd's. And lately all created iso's contain install.esd's.
If the present RS2 MCT Images are .ESD then I need to make changes for the ToolKit. Edit: Then there will no use of the Menu to Convert MCT Images as Convert Windows ESD Image to WIM Image will do the job.
I believe i was the one how knew how to achieve all, not you. You fully depend/rely on a tool, which always is under development because of changes in almost every new build msft releases. I've shown you how to save the MCT iso with different filename, how to manually extract the MCT iso and how to manually convert the install.esd .
"Knew how to achieve all", Yes, surely it works on your PC, doing the exact same as i did, except yours didnt throw errors like no tomorrow, where as mine did Thats the difference, which is why i asked specifically if you renamed it, or got it from the MCT - in which you take some weird round-about way of posting pictures on how to use it, instead of answering "yes" Yes, yes you truly do achieve all. Thanks for the help however, glad that in the end the dev got something out of it, by knowing its in .esd now from the mct, so thats something
If you had just removed the store app then you can integrate the store app from Integrate Default Metro and you will need the store appx file and it was posted few days back just check back the post you will find the link for default apps appx files.
And again, the clue is totally missed. Learn the basics, don't always rely on tools. Tools like MSMG toolkit are the best, all can be done manually, only MSMG puts it in one big easy to use script to make things easier. The install.esd part was mentioned for quite some time
The next version of ToolKit will be released today with .Net Framework 4.7 Pack (Windows 7) and I request people to check with the new Pack for any Bug related to Folder Permission or Viewing Office Protected Documents and then deploy the image.
Yeah, id love to see you try and do a thing if your ISO is corrupt. Even when you re-downloaded it, still corrupt. It sure helps doing it manually then, i hope you use the console for extracting the ISO too, and not rely on a tool such as 7z, winrar, or any script made by others :^)