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.
Okay, nothing about him being ill, as far as I can see. His last posting was November 11, 2019. Spoiler: MSMG Post
I'm fine, there was a loss of life and so I'd been to my native place to perform last rites and two week long rituals. just returned back. Will checkout the current updates and update the Toolkit soon.
You need to register the fonts in order to get the fonts listed. Here is the steps to do: 1) On a fresh system,open the registry editor and navigate to this below key and export the Fonts Key to a registry file. [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts] 2) Now copy or install all the fonts you want to be include in the install.wim to the current OS. 3) Again open the registry editor and navigate to this below key and export the Fonts Key to a registry file. [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts] 4) Now using a File compare tool, remove all lines related to fonts present in the first registry file in the second registry file and save the file. 5) Copy the registry file to <Custom\Registry\w10\x64> folder. 6) Copy all the fonts you want to be include in the install.wim to <Custom\Files\w10\x64\Windows\Fonts> folder. 7) Use the ToolKit's Integrate->Custom Windows Features->Custom Files Menu and Customize->Import Registry Settings from Reg File Menu. 8) Save & Rebuild the Image.
1) Will fix the UxTheme error. 2) Will update the WHD feature. You only need the older version 8.8 for W7-W10 RS4 component removal, rest of the things are updated in the current version to support W7-W10 RS4. Will add the removal part from v8.8 to next version so that two version aren't need anymore.
MSMG MDL Developer Please, Tell Me: Which Version of MSMG ToolKit Do I Need to Remove Components from Windows 10 Enterprise LTSC 2019 Build 10.0.17763.316?