1.Mounted install.wim with ToolKit-v7.3. 2.Removed all. 4 - 1 - 2 4 - 1 - 3 4 - 2 4 - 3 - 1 4 - 3 - 2 - 1 4 - 3 - 2 - 2 4 - 3 - 2 - 3 4 - 3 - 2 - 4 4 - 3 - 2 - 5 4 - 3 - 2 - 6 4 - 3 - 2 - 7 4 - 3 - 2 - 8 4 - 3 - 2 - 9 3.Saved image. 6 - 1 4.Installed modded install.wim - Updated - then cleaned up with these commands. sfc /scannow Dism /Online /Cleanup-Image /StartComponentCleanup /ResetBase 5.Used Sysprep - then capture image. NOTES: I updated modded install.wim this way, because after integrating cumulative update and NET Framework 3.5, the modded install.wim would not install OR would be broken in some other way. MSMG ToolKit is the best tool i have used for modding install.wim, i just need to learn how to integrate updates and packages properly.
Removing at least one of those will result in un-usable image once the installation completes - you will be assigned defaultuser0 account, Explorer.exe will give out major errors and Start UI won't work... Looks like it is best to leave those alone and not remove them from AppRepository SQL database, not set them as Inbox=0 or NON-inbox Apps because removing every trace of those exact packages in registry alone causes issues. My point is - be careful with custom package removal. I think MSMG Toolkit developer was very much correct when he said that just about everything that could be removed without causing issues has already been put on the existing list. Yet, I still wonder about that 2GB Windows 10 LTSB custom image. This is what was removed from that custom image that resulted in 2GB install size and I am translating this from Russian: These are the things that are disabled by default in their release: Even without Swap file and Hibernation, the best install size I ever got was about 10GB, nowhere close to 2GB! Could someone point to me which of the removed features take up THAT much space? I guess I need to install it and run WIM Tweak to get the list of remaining packages and then compare to the default package. Some other questions: - What is the difference between On-Demand NetFX35 (that does not require NetFX35 folder in Packs directory) and the downloadable NetFX35 package? FYI, integrating On-Demand package barely increased image size. - How and when should NET Framework 4.7 be integrated into the image? LTSB doesn't come with 4.7 like CU and the 1GB update released/dated 5/9/2017 does not deliver it either. - What is the difference between Store and Store Client? I assume none are required for Edge browser integration. - Should Edge browser integration take place before or after applying cumulative updates onto LTSB?
Just an empty C:\Program Files\Windows Defender folder, and a C:\Program Files (x86)\Windows Defender folder with these folders and file. en-US EppManifest.dll.mui MpAsDesc.dll.mui MpEvMsg.dll.mui Offline (empty folder) Files: EppManifest.dll MpAsDesc.dll MpClient.dll MpOAV.dll MsMpLics.dll shellext.dll Second time i ran sfc /scannow, there was no errors.
1) Yes, removing some of this packages offline will make the OS unusable and but when it's removed online it will work, the best you can do is to add the removal code for this packages to be executed on first boot. 2) About the 2GB Windows 10 LTSB custom image you were referring to, I think the one who did it might have removed the components on live system and then did a sysprep image to get that size. 3) On-Demand NetFX35 CAB present in sxs folder or Packs folder or downloaded from WU are same package files. 4) NETFX 4.7 can be Integrated like any other feature pack there's no order. 5) Store is the Metro App and Store Client is a back-end client for the Store App and it's not related to Edge. 6) Edge Integration should be done before the CU Integration.
About that 1st one - how can I make it happen? Should I edit the registry to make those AppX's NON-Inbox ones and create a .bat file or PowerShell file and place it in StartUp?
Remove package without mum: I delete all files in "C:\Program Files (x86)\Windows Defender" and delete key and value in registry related to these packages, delete files in WinSxS related to these packages, and sfc scannow is ok.
Open the game bar does slow Windows, there is no solution against this if it is disable the game bar ?
It appears that even LTSB versions gets the wrong registry entries for items it is not supposed to have - Zune, Xbox, and MSMG Toolkit does not get rid of all registry keys related to the items removed - ParentalControls package are still found in registry - update or not. SFC goes through with repairs, but DISM keeps failing with Remote Procedure Call Failed (error 1726) even if its the first thing I run when PC boots cleanly installed OS for the first time. The RPC Service is running just fine... Remote Procedure Call Failed (error 1726) - what usually causes this?
Keep waiting. I'm not the only one complaining and you didn't say that to every user who complained. If you'll not even enternaint my supposed stupidity why did you wrote that testament? So, it's my way when I did the right thing, even in a PC in which I didn't even use CCleaner? Of course you have nothing to say about this second situation but only about the first one! I've changed my mind but that wouldn't be the correct way...
You have really a big problem. In every thread of you there's just one thing: gimme gimme gimme! No friendliness or something. No "thank you" just give me all an everything. Thats disgusting+