I wonder if there is a specific reason that this step seems unable to leverage multiple cores. DISM, as I am sure you have seen in testing, usually grabs every single available thread and splits up the workload. What is the specific command being executed here if that is something you can share? -> [L] - Cleanup the Source Image using [Apply->Cleanup Source Images] menu. Conversely what is the effect of skipping this step? Aside from this one single step my workstation (and much more so the one I am building) tears through the build process, this one step takes longer than all the others combined.
Maybe I'm an idiot or something, but for the life of me I can't get the latest cumulative uppdate integrated properly in RS3 1709. Every time I install and check for updates, it wants to install the update. My step by step is: -Integrate updates (I only have the cumulative update[non delta] in there) -apply and save changes -remount -integrate .net framework 3.5 and directx -apply and save changes probably forgetting a step or something, so if anyone can point out what point I'm being dumb at, much appreciated
@MSMG Since RS3, e.g. x64. Hyper-V: [Hyper-V] Microsoft-Windows-HyperV-Guest-Package~31bf3856ad364e35~amd64~~10.0.16299.15 Microsoft-Windows-HyperV-Guest-WOW64-Package~31bf3856ad364e35~amd64~~10.0.16299.15 Microsoft-Hyper-V-ClientEdition-Package~31bf3856ad364e35~amd64~~10.0.16299.15 [Windows Defender Application Guard] Microsoft-Windows-HVSI-Package~31bf3856ad364e35~amd64~~10.0.16299.15 [Protected Host] Microsoft-Windows-PAW-Feature-Package~31bf3856ad364e35~amd64~~10.0.16299.15 [Containers] Microsoft-Windows-OneCore-Containers-Opt-Package~31bf3856ad364e35~amd64~~10.0.16299.15 Connect: [Primary package] Microsoft-Windows-Non-LTSB-RegulatedPackages-Package~31bf3856ad364e35~amd64~~10.0.16299.15 [Secondary package] Microsoft-PPIProjection-Package~31bf3856ad364e35~amd64~~10.0.16299.15
I don't know if this is the wrong place to ask for this, but I'd like to request some additional things to be removable: - Windows\Web (vanilla wallpapers) - Windows\Media (Annoying OS sounds that I turn off anyways and such) - Windows\Resources\Themes\theme1.theme + theme2.theme (The extra aero themes) - Windows\Resources\Ease of Access Themes - Windows Ease of Access (Overall I'd like to have this gone as I've never used it once) - Windows Mail (Program Files\Windows Mail & Program Files (x86)\Windows Mail) - Parental Controls? I know that none of these items aren't removable after installation (Perhaps EoA is difficult to get rid of after installation), but I'd like to have them removed from the installation media aswell. I'm a perfectionist and love a clean OS. Thanks for your awesome work!
Here's what I will do. 1 wimtweak to remove some packages offline 2 remove metro apps using msmgm tool offline 3 create iso msmg tool 4 make it bootable wintobotic 5 install Windows 6 use wimtweak to remove remaining crap online 7 use dism++ to clean up online image plus remove some more unwanted crap 8 create install.wim of installed os 9 replace install.wim with the one i have created earlier on bootable USB stick That's what i did with 1511 year ago
@MSMG: Welcome back and it's good to hear that you're doing well. Can version 8.0 be used on LTSB without issues? Or is it still recommended to use the old 7.7 version? Cheers.
I have a quick question about your post here. Are you saying that there is currently an issue with Hyper-V removal through the toolkit or mentioning something else unrelated to removal issues. I am asking because I just removed Hyper-V from an image I want to test and will hold of if there are known issues. Thanks.
Can you specify the folder structure from where you are running the ToolKit? Did you removed any files changelog.txt or modified any foldernames/filenames inside the ToolKit?
Did you followed the instructions given in the First Post? Did you use the Start.cmd to run the ToolKit?
Follow the Instructions given in the First POST, I have specified separate Set of Instructions for All OS. Don't forget to run the ToolKit using Start.cmd Yes Integrating Cumulative Updates before .NET Framework 3.5 will again offer a 50mb of update to update .NET Framework 3.5.