I feel like there is something here I'm doing wrong? I went through the whole readme for 1909 and removed all the items I wanted and then did the following: [J] - Cleanup the Source Image using [Apply->Cleanup Source Images] menu. [K] - Integrate Microsoft .NET Framework 3.5 Feature using [Integrate->Windows Features->Microsoft .NET Framework 3.5) menu. [L] - Apply & Save Changes to Source Images using [Apply->Apply & Save Changes to Source Images] menu. [M] - Re-Build Source Images using [Apply->Re-Build Source Images] menu. After this I then did [7] TARGET >> [1] Make a DVD ISO Image Named my ISO and after it was done creating it, it was 300MB LARGER than the original ISO. Should it be a solid 1-2GB smaller if I removed a ton of the windows features? Any assistance would be greatly appreciated.
I successfully completed the process once and am tinkering with it on Vbox. I am now in the process of my 2nd go at this to ultimately have a system that is satisfactory. I have a few questions for those who know what's going on with this. I am at the integrate updates part of the process. I am using WHD as my updates source. I put the update files in their respective folders. Please tell me what goes in the SetupMedia folder and the WinPe folder. Does this affect being able to create the boot and winpe parts of the process? ( I answered yes at the start of the process when asked if I wanted to include that). Do I need to extract (or just copy) something else to put in these folders? There was not an update included in the WHdownloader files that were downloaded for SetupMedia or WinPe. Using 1809. Thanks.
What's wrong with WIM's size ? Spoiler: My source =============================================================================== MSMG ToolKit - Select Source from <DVD> folder =============================================================================== ------------------------------------------------------------------------------- ####Selecting Source Images#################################################### ------------------------------------------------------------------------------- Reading Image Information... =============================================================================== | Index | Arch | Name =============================================================================== | 1 | x64 | Windows 10 Education | 2 | x64 | Windows 10 Education N | 3 | x64 | Windows 10 Enterprise | 4 | x64 | Windows 10 Enterprise N | 5 | x64 | Windows 10 Pro | 6 | x64 | Windows 10 Pro N | 7 | x64 | Windows 10 Pro Education | 8 | x64 | Windows 10 Pro Education N | 9 | x64 | Windows 10 Pro for Workstations | 10 | x64 | Windows 10 Pro N for Workstations | 11 | x64 | Windows 10 Enterprise for Virtual Desktops =============================================================================== Enter the Image Index's # [Range : 1-11, * - All] : ------------------------------------------------------------------------------- ####Source Image Information################################################### ------------------------------------------------------------------------------- Image : Install.wim Image Index No : 3 Image Name : Windows 10 Enterprise Image Description : Windows 10 Enterprise Image Architecture : x64 Image Version : 10.0.17763 Image Service Pack Build : 1 Image Service Pack Level : 0 Image Build : 17763 Image Edition : Enterprise Image Flag : Enterprise Image Installation Type : Client Image Default Language : en-US 1. I did ntegrate NOTHING and I did remove allmost everything : full folder WindowsApps(1.3GB) and 20 folders in SystemApps(176MB) boot.wim 323MB -> 336MB (+13MB) install.wim 3917MB -> 3955MB (+38MB) 2. Then in addition I did integrate win32calc only boot.wim 336MB -> 347MB (+11MB) install.wim 3955MB -> 3985MB (+30MB) 3. Then in addition I did ntegrate & remove NOTHING - only mount, cleanup and apply & save changes boot.wim 347MB -> 358MB (+11MB) install.wim 3985MB -> 4015MB (+30MB) The trend is observed...
Hi friend, well I remember once about this situation after having extracted the iso into the script and the sequence using (8) Tools and check what was inside of it I forgot to delete ALL indices so unnecessary as consequence my iso got about 5.7GB lol so I undid everything and started again and my iso was much smaller ...
No. For some reason I thought that this refers to rebuild ISO file, not WIM file. Thanks. Code: boot.wim : 338,871,678 -> 336,942,294 install.wim (exported index 3): 3,748,451,380 -> 2,646,505,681
@MSMG I want to report 2 bugs in the latest version 9.5 servicing Windows 8.1 1. Toolkit won't copy the Uxtheme files. Keeps giving error that DLL files should be in specified location even though files are already there. This also happened with 9.4 but not with 8.8 2. WHD Baseline update KB4504418 has been superseded by KB4524445 but toolkit won't integrate newer update bceause it keeps looking for the older one KB4504418. I had to rename the newer one to older one to get it integrated. A request. It's a big hassle to work with two different versions. We the 7/8 users only need the latest version to integrate the .NET 4.8, if we can somehow do this with 8.8 then it would really be very easy and hassle free. Please consider this. Thanks for this awesome toolkit. Highly appreciated.
Never mind, I found the answer. I hadn’t read far enough. On Jan 15, 2019, MSMG posted: “Go to WHD Downloader thread and get the Tool and download the updates and copy them to the corresponding folder. SetupMedia and WinPE updates needed only if there are updates available for them.”
is converting WIM to ESD using MSMG Toolkit in windows 7 same as using it in windows 10 ?? (wim of windows 10 iso)
It should be the same, it's done by wimlib-imagex, afaik. it's done by dism, provided by the toolkit.
IMHO, Since MSMG hasn't been around, does that mean he isn't well? Maybe he took a vacation. I don't know anything about MSMG, like his/her age, any illness, etc. I, myself do miss him.