@Enthousiast ok but this is my doubt dude when using Toolkit v 6.4! related to Resetbase one thing I'm sure myself NO integrate dotnetfx3 more after system is installed is easy install using dism so I avoid issues correct
When you enable dotnetfx3 after install with dism command there is the change WU will offer the CU again and download the parts for updating dotnetfx3. It's better to enable dotnetfx3 by going to "programs and features" and next go to "turn windows features on and off" and enable dotnetfx3 from there, then an updated dotnetfx3 will be downloaded and installed.
That's why you do cleanup resetbase after the CU, enable net 3.5 as a last step, and apply the CU again to update the net 3.5 stuff. No issue at all, but I'm repeating previous posts (again). Cheers.
I have made a striped LTSB ISO (1607) fresh using MSMG v6.4 yesterday. My surprise was to end up with a 4,9566 GB iso file after integration servicing stack, latest CU and Flash. Just removing "all Windows apps" after integration. The latest I made in December with 6.2 version was 3,6235 GB only . Same component removed. Why a so big difference ? Do I make something wrong ? I integrated updates in *mui format as before. What I do : Copy iso files > DVD > Launch MSMG and after mounting first thing is integrate updates, then apply to wim > go to remove section > remove > apply and cleanup /resetbase , unmount then target create iso ?
Integrate latest CU first, then remove original component? Original is original, and CU is CU. What's gonna be? Lately, Microsot does not want you to easily remove a package. OneDrive is a good example - The 14393.726 CU divides the OneDrive package into 4 sub packages... And most badly, in different main packages! To sum it up: It will be reinstalled anyway - unless those 4 sub packages were removed afterwards.
1) May be when executing the Integrate Apps function the Apps path variable is not getting reset that's why it's concatenating the path with the previous one, this happens when you enter the integrate apps menu more than once. ok will check out the script and fix it. 2) You can use the full package name in the RemovePkgs.txt list file but in order to reuse the list I had put a warning to truncate the package name so that there's no need to change the build number/language each time. - The list should contain only the main/parent package name - The list should not contain the MUI language package names since removing the parent package will remove the associated MUI language package too. - The list should not contain the sub packages name since the removing the parent package will remove its associated sub packages too. But for some packages it may required to manually to remove the sub packages/MUI language packages separately. For E.g. The below packages will remove the Defender from Windows 10 RS1 64-bit OS Windows-Defender-Client-Package Windows-Defender-Client-WOW64-Package Microsoft-Windows-SenseClient-Package Windows-Defender-Group-Policy-Package For RS2 it requires some more packages to removed like Windows-Shield-Provider-Core-Package Windows-Defender-ApplicationGuard-Inbox-Package If you don't follow the above method and just add all the package names the TooKit will check for each package name and if it's found then it will remove or else it will give not found message but it will take lot of time. 3) Resetbase is included and it works only if there is not pending flags set in the image, if you had integrate .NET FX 3.5 or any update/package that sets the pending flag then the ToolKit will skip the Resetbase for install.wim
For what it worth, I just made an iso file using MSMG v6.3 with same updates same procedure. I ended with an integrated servicing stack, CU from Jan 10 + Flash player and same removed components = 3,6431 GB. I think v6.4 has issues. (I use iso date august 2016 - LTSB 2016).
Hmm may be...but this one (10240.16393.150909-1450.th1_refresh_clientpro_ret_x64fre_en-us.esd) didn't cause any error. Cheers.
Yes, but with the latest refresh (14393.0.161119-1705.rs1_refresh_clientcombinedsl_ret_x64fre_en-us.esd) people already reported errors when attempting to remove metro apps. The 10240 refresh didn't cause any error, but that doesn't mean the 14393 will be the same. Cheers.
So I just did an x64 image. But it takes an awful lot of time, with the latest CU released today it was 2 hours and 30 minutes. The CU is being released twice a month it seems, so this is not really efficient. Is there any way to speed up the process? Ramdisk and mount the wims there? I'm really getting bored to do the whole process over and over again. Cheers.
I've actually never tried that because I lack the necessary amount of excess RAM. What I've had done, however, is edit the toolkit so that it uses my SSD instead of HDD. That produced a noticeable speedup. So it makes sense that a RAMDisk would also produce a speedup, at least, in theory. However, you will need lots of excess RAM to test this. An untouched MSDN Windows 7 Professional SP1 x64 index with the 17.1.15 Simplix pack integrated plus the other wim files that the toolkit mounts makes the toolkit's mount folder 18.2 GB. Replace the aforementioned Windows 7 index with an untouched MSDN Windows 10 2016 Enterprise LTSB x64 index and the folder size drops to 16.2 GB. I personally wouldn't try this with anything less than 32 GB of RAM. Probably not even then because I'd have to re-initialize the RAMDisk every time I want to use to the toolkit because I'm not fond of cutting my RAM in more than half for the whole time my PC is on.
I don't get why you're doing things redundant, where does the need to do a resetbase after one sstack and CU integration come from? resetbase cleans up winsxs components and resets the base. You're integrating the CU first only to be able to do a resetbase and afterward you're enabling dotnetfx3 and reintegrating the CU again.....what did you actually cleanup?
Integration of features components and WHD Updates with Convenience Rullup on WIN7SP1 Following the recomendation of @abbodi1406 I post here the same message I've posted on the WHD support thread (with some corrections). Hi I'm very new user of this tool, maybe my question could be a little stupid for other people but my english is very bad and I don't found a answer to this (its my fault... I know it...): ¿What's the correct order of integrating the updates into the Windows 7 Ultimate SP1 ISO with Convenience Rollup Update? I'm using MSGM Toolkit v6.4. The order I think is: 1.- Windows Features: NetFX4.6.2 IE11 RDP8.0/8.1 WMF5.1 DaRT7 DX9C 2.- Windows Updates from WHD with SP2 (aka Convenience Rollup option) WHD WAT update from Addictional updates WHD General updates (Convenience Rollup Update) WHD Security updates WHD Hotfix updates 3.- Update Windows Setup Media 4.- Windows Custom Features: Terminal Server Patch Fraunhofer MP3 Tweak UxTheme Patch Custom WinRE Custom Default User Account Pictures Custom System Files 5.- Remove Components: Windows Home Group Windows Parental Controls 6.- Apply Changes to Source WIM Images and create de new ISO. Is this order correct and safe? or Do I need to apply the Covenience Rollup again (WHD General Option) or something else? I will use this post to give thanks to the developers of this tools @abbodi1406 (mantainer of update list and creator of Updates Installer), @burfadel (maintainer of Office2013 lists), @Alphawaves (for the WHDownlaoder) and the MSGM Team of course. With this tools I think could make my life easy.THANKS FOR YOUR EFFORTS AND TIME.
Short answer: Because it saves more than 1GB of space. The .net 3.5 integration does not allow for a resetbase. So I do that after having integrated updates, apps and removed all that I want. After the .net 3.5 integration as a last step, those components need updating also. That's why I repeat the CU, obviously it finishes quickly because only the .net 3.5 stuff is being updated. Resetbase removes all superseded stuff from the image. And it saves a lot of space. People here have reported image sizes of 4.5GB or more after running MSMG toolkit. But show me the error of my method and I'll gladly try any method you propose. Cheers.
Feedback: Removing all Windows components does not remove dmwappushsvc service (related to telemetry). Integrating the DirectX9c pack through the Toolkit continues to cause the bug with protected Office files. But if you extract the files with the 7-zip and copy directly to the folder where the image is mounted and import the .reg file the bug does not happen. With Windows 10 Enterprise Redstone 1 as Source the following packages are not present: Code: ------------------------------------------------------------------------------- Removing Windows Retail Demo Offline Content Package from WIM Image... ------------------------------------------------------------------------------- The Package Might Have Been Removed Already Or It Doesn't Exists... ------------------------------------------------------------------------------- Removing Windows Retail Demo Offline Content [en-US] Package from WIM Image... ------------------------------------------------------------------------------- The Package Might Have Been Removed Already Or It Doesn't Exists...
1) Will fix the dmwappushsvc service removal. 2) Due to lack of time, still I haven't worked on that bug causing protected Office files, if it works by extracting the files directly but not with applying the files as an image then the problem might in the way the Image is created or with the DISM applying the image But the other images aren't having any issues in applying the pack image. 3) Due to too many Build and Edition combinations I might have missed the Retail Demo Offline Content, will check out fix it.