That's called Component Protection/Splitting to have a working system without any issues in retained components and Yes it requires some method to make SFC not to throw errors at removed components.
Yes these packages are safe but there's no room for more menus in the Current ToolKit under Remove components Section until the menus are Categorized.
I joined just now, because this brilliant piece of work caught my view; been tinkering around with this with a copy of windows 8.1 pro (when I had to reinstall my dad's OS because his hard drive Pear-Shaped, and we got a replacement), and I do have a few questions, also getting sleepy, so forgiveness if I n00b it up in this post, OS specs in attachment I can set this so I can keep components like the snip tool, and it would work if I messed with my copy of windows 10 pro, correct? If I tinker with Windows 10 Pro, can I remove cortana without breaking the search indexing function/program? I can integrate whatever updates I want, and if I remove certain windows components I deem useless, will any subsequent update(s) my copy of windows gets (windows 8.1, 10, 7, etc.....) upon installation break the customized OS installed, or reinstall the removed components, or something else happen? reading through old posts, correct me if im wrong, but there will be a game pack released that has all the windows 7/vista (and maybe windows xp, mainly the 3d space cadet pinball game, LOVED playing it as a kid) installed games like minesweeper, chess, etc..., correct? I didn't know where to get the .tpk files for any of the games I can set this so a program (lets say for example, Dropbox, or CCleaner) is integrated and after installing the custom OS, and creating the user profile and all that jazz, it will show up in the program files folder or wherever it installs itself, right? Last part to this before I get some sleep (the sandman calls, and will not be denied any-longer): when I moved the iso file of windows 8.1 pro to the iso folder and renamed the file Windows, I tried using the "extract contents to source folder" option, but it just went back to the menu each time I tried using it, and on top of that, it deleted the DVD\Sources folder, making me re-create the folder(s) manually and extracting the boot.wim and intstall.wim (converted the .esd to .wim) files; is there something I'm doing wrong here, or is it my Operating System; also, do I need EVERY file from the Win8.1 iso in the sources folder, or just the files in the sources directory, or JUST the boot.wim and the install.wim
If I want to remove ALL Store Apps INCLUDING Store, do I select option 3 or 4? The description does not match... 3 is supposed to Remove All, but Y/N message states "All, except Store". I think it was already mentioned, but which one is wrong - the selection menu or the Y/N confirmation message? Is anyone having issues updating to the recently released Servicing Stack and Cumulative Update? Something, some component is missing and update fails, but which log should I use to find out what is actually missing? I made the image using several tools and would like to know which component is missing. DISM only reports that needed default files are missing (not which ones exactly) and SFC ScanNow does not find any violations, so which log should I check? Windows/SoftwareDistribution folder logs are encrypted...
Maybe not so safe - the new update will not apply and the only things I removed with NTLite was the reaming Xbox Game mode components and Game Explorer. SFC and DISM were passing, yet needed files or components were missing and I need to find out whether it was NTLite or those extra packages I deemed safe to remove that prevent the OS from updating. I do not know which log to look into - DISM does not specify files or components, just that they are missing and SFC ScanNow passes with flying colors...
One more question for now - now that the first Servicing Stack it out for Creator's Update - does MSMG Toolkit update with respect to Servicing Stack's instructions? I updated the image with Servicing Stack only, then performed Apply + ResetBase, and only then remounted the image and applied Cumulative Update, followed by Flash update. Do I need to redo all that using the WHDownloader (WHD folder) method to make sure Servicing Stack is utilized properly for Cumulative Update application?
No, it's about not knowing what you're doing but placing the blame at a tool that is misused. My example of phoenix still stating his iso is so big because of the method of rebuilding by MSMG Toolkit but clearly it wasn't even performed, as i showed. Rebuilding is just exporting the indexes to a new install.wim, a simple dism command, that cleans up the 2GB of deleted stuff in the existing install.wim. Just read the comments he makes at notebook review and MajorGeek.
I specifically did not call out specific people to try to avoid a response where someone felt I was explicitly writing about them. My comment was not about you. I have been reading this thread the past 10+ pages to catch up on some things and some users' bitching have zero credibility. And I think everyone can agree that unless you know precisely what you're doing and have done it yourself, then you need not tell others what they should do nor how they should go about doing it. Again, not directed towards you.
I think I understand, but since I have also had trouble integrating CU I would like for it to be extra clear. MSMG seems to agree with MonarchX, but then says the opposite?? So ... which is it? Remove and CU or CU and remove?