Your right its in esd. My bad, hence the small wim file size! The ability to compress to esd after compressing wim i almost forgot about it.
@daveo76, @kronflux and @MSMG: Thank all you for your reply. Also, thank for your shared informations about D3DCompiler_47.dll file. PotPlayer and Cent Browser (which it a Chromium-based web browser) included this file. Therefore, So I thought this file should be in system32 and SysWOW64. I now understand the state. It's good to know that Deleted folders can be trimming via Rebuilding. Thank you. I will use it. I discovered Dism++ yesterday that I would recommend. Already it's mentioned. I'm hoping to get a GUI that we can use the MSMG toolkit... Thank you for all your efforts. Sorry my bad English. Kind regards...
You have to know this: The MCT downloads esd files to create the iso locally on your system, so it will always have a different hash, each time you create it. But the install.wim/esd is of the same build as the corresponding MSDN/Techbench iso. Many iso's that are created by the MCT have an install.esd instead of an install.wim. Again: conclusion, convert install.esd to install.wim before servicing!
Could someone with Windows 10 RS2 (Creator's Update) 15063.296, who skinned their Windows Photo Viewer with Metro skin using MSMG Toolkit, upload the 2 PhotoViewer.dll files - one from "Program Files" and the other from "Program Files x86" directories? I think preserving the size of the DLL files will prevent SFC from failing, like it does when files are replaced with the ones from a different version of the OS.
Then my PC is fubar, because even when i DO convert the install.esd to install.wim, it still cant find it in DVD/Sources, because, i assume, the script fails somewhere along the line As i dont even have a sources folder in DVD Have you, personally, used the MCT ISO and converted it after extracting? If so, did you also get a million access denied while converting and extracting? Can you extract the ISO with 7z?, because when i do i get this error too. "Warnings: There are some data after the end of the payload data" This is done a freshly installed, untouched, fully updated Windows 10 x64 Pro For reference, even though i get the error the install.esd does extract with this hash --------------------------- Checksum information --------------------------- Name: install.esd Size: 3061350362 bytes (2919 MB) SHA256: 2BA5128C1928BE3F33EAB8F414C06082F293A4A91CA1BB94E25BBC7572DC569B --------------------------- OK --------------------------- The ISO that i got from the program you linked does -NOT- have install.esd, it has the regular install.wim extracted, and throws -no- errors when extracting. This is why i asked about the MCT ISO, because something about it just messes with the program, or my entire PC.
I have used MCT, manually downloaded esd files, converted to iso by abbodi1406's ESD>ISO decrypter and standard MSDN/Techbench iso's. What build do you want me to test?
MSMG only can't convert install.esd to install.wim, at least it gives this error: Code: =============================================================================== MSMG ToolKit - Convert Windows Media Creation Tool Image to WIM Image =============================================================================== Cannot Find Windows Setup "Install.wim" Image in <DVD\Sources> folder... Please Copy Windows Setup "Install.wim" Image to <DVD\Sources> folder... =============================================================================== Press any key to continue . . . or Code: =============================================================================== MSMG ToolKit - Convert Windows ESD Image to WIM Image =============================================================================== Cannot Find Windows Setup "Install.esd" Image in <DVD\Sources> folder... Please Copy Windows Setup "Install.esd" Image to <DVD\Sources> folder... =============================================================================== Press any key to continue . . . But this has been mentioned a few times before. Also this: 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.iso Cannot Find the Specified DVD ISO Image in <ISO> folder... Please Enter the Correct DVD ISO Image Filename... =============================================================================== Press any key to continue . . . But all can be done manually.
Hi all, It's possible to reinstall the Windows Store where is disabled by MSMG? I didn't find on this thread. Thanks
I saw the post, i also saw that your ISO file was x86, and not even named Windows.iso, so either you renamed it, or you didnt use MCT to get it. If it cant convert install.esd to install.wim - then i have to question the sanity of there being both an "Convert ESD to WIM" and a "Convert Store ESD to WIM" option in the convertion options in MSMG Either i missed something, or someone else did Or im just not making any real sense and am failing in conveying what issue im having, i suppose
I think the update is again offered through WU might be for the .NetFX35, you just try integrating the windows10.0-kb4016871-x64.cab again after the .NetFX35 and it will update only the .NetFX35 components and then check with WU it will not offer the update.
The MCT names the iso windows.iso by default, you simply can use another name..... The options not working is up to MSMG to fix, but those options can easily be done manually, as shown by me. x64 or x86 is no difference.