Has anyone figured out why adding NET Framework 3.5 and 700MB worth of drivers + removing everything Metro-related from the ISO with this tool results in a WIM file larger than the original and an out-of-proportion increase in desired free space during installation yet??? All instructions followed and yet during clean OS install from an ISO with many Metro Apps removed results in a request to have 40-55GB worth of free space, while official Creator's Update ISO installs just fine on my 30GB partition...
If you are using the the stable Windows 10 LTSB and follow the LTSB build instructions in my signature, then don't apply the 'remove Cortana' step: "[4] Remove -> [2] Remove Windows Components -> [H] Windows Cortana & Search App" You can safely leave Cortana in the LTSB ISO since the LTSB version of Windows 10 only allows the start menu search features of Cortana and doesn't install any of the bloat... Personally, I remove Cortana and use Classic Shell because my old laptop and netbook have very little RAM and the 'memory budget' for just the "Cortana Start Menu Search" feature (searchUI.exe) is like 30MB+ while all of Classic Shell, including an excellent "Start Menu Search" feature, consumes maybe 2MB ...
As dhjohns pointed out already ... If you look at the "== Basic Set-up ==" section for the Windows 10 build instructions in my signature, you'll see the statement that ... "if you name or locate the ToolKit folder differently, edit the provided code" Personally, I name my folder with the version number and binary (ToolKit-6.9x86) and then modify the code to reflect that name. I believe MSMG recommends putting the toolkit folder on the root of your hard drive so it should be on C:\ToolKit-xxx or D:\ToolKit-xxx or whatever. I really tried to make the build instructions as simple and generic as possible. I may have 'polluted' my instructions with too much information and complex details. If that is so, I am sorry! Just for fun and because it might solve someones issues, here is an alternative PowerShell code that does the exact same compression as the 'imagex' code shown in my signature's MSMG ISO build instructions. You're still going to rename and then delete 'big_install.wim' Follow the build instructions until you get to the the "Compress the WIM..." point. Instead of opening a second command prompt, open a PowerShell terminal Use the following PowerShell code instead of the 'imagex' code. Make the Code Specific to your toolkit directory: Replace "ToolKit-xxx" two times Code: Export-WindowsImage -CompressionType maximum -SourceImagePath C:\ToolKit-xxx\DVD\sources\big_install.wim -SourceIndex 1 -DestinationImagePath C:\ToolKit-xxx\DVD\sources\install.wim As before ... after you run this code, don't forget to delete 'big_install.wim'!!! Good luck!
Feedback well this night I start my new project using Windows 10 Build 16179.1000, so after extracting source from DVD ISO image script warn this so on doubt I temporary stop my job until someone help if this warning can broke my job or don't make nothing thanks in advance EDIT:[SOLVED] corrupted files
Hi mb_force! tpk (means toolkit pack) file is a custom file type used by MSMG for Toolkit. The real and "usable" type file is .ESD.
If you guys wonder how long it takes to convert a 4.2 Gb .wim file to a 2.83 Gb .esd ,on an ancient amd athlon x2 250 dual core cpu with 4 Gb of ram the answer is...3 full hours.My cpu stayed at 99% and 1.6 Gb of RAM used all the time.
Hi, While removing Windows Defender from an W10 x64 RS2 (15063.0.170317-1834) Enterprise image an error pops up: Only happens with the WOW64 package. The "Windows Defender Client" before (non WOW64) removes correctly. Any ideas? The log isn't there. Maybe MSMG deleted it after finishing? I removed almost all Windows components and that was the only error. I'm trying the ISO in a virtual machine now.
MSMG, please if you can include removing "mixed reality" app and the start menu shortcut, and security center. thanks so much!!!
yay the best news for today, I haven't haste for a while v6.9 works fine same on Build 15063.0 no issues still new version seem awesome very good job
Cool. Upon installing, the settings for Defender say "The app has been uninstalled from the server" so everything looks good so far. I'm trying a completely stripped version of RS2 in a VM (Hyper V and a few others thing were left untouched) and I don't see any problems. Will install in the main machine in a few days.