with 19042 enablement package the Edge Chromium triggers the pending.xml flag and so you can't perform the cleanup.
Tested v10.2 can't remove Cortana 19041/2.421 source uupdump 10 iot ent remove windows components > all systems + windows apps Cleanup > Apply changes to image > Rebuild
I've got another question related to the driver integration. Is it generally a good practice to be adding lots of drivers to an image? More specifically, does the integration add all the drivers into some sort of repository within the system only to be active if a relevant piece of hardware is detected, or will it bloat up the system if you add too many drivers?
@MSMG, Error 87 when we select a specific range, in this case from 3 to 4 (3-4). I hadn't used that function yet. Only used "*". Dism Log attached. Spoiler: Source Image Info Image : Install.wim Image Indexes No : 1-5 Image Architecture : x86 Image Version : 10.0.18362 Image Service Pack Build : 959 Spoiler: Error 87 when selecting the range 3 to 4 (3-4) =============================================================================== MSMG ToolKit - Select Source from <DVD> folder =============================================================================== ------------------------------------------------------------------------------- ####Selecting Source Images#################################################### ------------------------------------------------------------------------------- Reading Image Information... =============================================================================== | Index | Arch | Name =============================================================================== | 1 | x86 | Windows 10 Home | 2 | x86 | Windows 10 Education | 3 | x86 | Windows 10 Pro | 4 | x86 | Windows 10 Pro Education | 5 | x86 | Windows 10 Pro for Workstations =============================================================================== Enter the Image Index's # [Range : 1-5, * - All] : 3-4 Do you want to mount Windows Setup Boot Image ? ['Y'es/'N'o] : N Do you want to mount Windows Recovery Image ? ['Y'es/'N'o] : N ------------------------------------------------------------------------------- ####Source Image Information################################################### ------------------------------------------------------------------------------- Image : Install.wim Image Index No : 3-4 Image Name : ~1 Image Description : ~1 Image Architecture : Image Version : 10.0.20175.1000 Image Service Pack Build : ~1 Image Service Pack Level : ~1 Image Build : .201 Image Edition : Image Flag : Image Installation Type : ~1 Image Default Language : ~1,-10 ------------------------------------------------------------------------------- ####Mounting Source Images##################################################### ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- Mounting [Install.wim, Index : 3-4] Image at <\Mount\Install>... ------------------------------------------------------------------------------- Deployment Image Servicing and Management tool Version: 10.0.20175.1000 Error: 87 An error occurred while processing the command. Ensure that the command-line arguments are valid. For more information, review the log file. The DISM log file can be found at C:\ToolKit\Logs\Dism.txt ------------------------------------------------------------------------------- ####Finished Selecting & Mounting Source Images################################ ------------------------------------------------------------------------------- =============================================================================== Spoiler =============================================================================== MSMG ToolKit - Discard Changes & Unmount Source Images =============================================================================== ------------------------------------------------------------------------------- ####Starting Discarding Changes & Un-Mounting Source Images#################### ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- Un-Mounting Source [Install.wim, Index : 3-4] Image... ------------------------------------------------------------------------------- Deployment Image Servicing and Management tool Version: 10.0.20175.1000 Error: 50 DISM failed. No operation was performed. For more information, review the log file. The DISM log file can be found at C:\ToolKit\Logs\Dism.txt ------------------------------------------------------------------------------- ####Finished Discarding Changes & Un-Mounting Source Images#################### ------------------------------------------------------------------------------- ===============================================================================
The Toolkit uses the standard DISM tool to perform image operations and for driver integration also it uses the same tool, Adding too many drivers can increase the image size.
Actually The Toolkit only works with single or All Indexes, function for selective range is not added yet.
Hi MSMG I think pending.xml is not caused by enablement package and Edge browser for 19041/19042 I used clean 19041.1 , integrated all updates except enablement package and removed all components using package list and I chose "Cleanup Source Images" from MSMG toolkit Menu (6) It gave me "Pending.xml" error again Thanks
All the answers you need are in the readme file provided with the ToolKit. It is worth the small amount of time needed to become familiar with the basics. If you look at my past posts, you can find examples of methods that you can customise to suit your needs. These (hopefully) follow the instructions given by the readme file.
https://forums.mydigitallife.net/threads/msmg-toolkit.50572/page-793#post-1606110 Sent an 2020-07-31 updated file in the post above. Spoiler: CHANGELOG 2020-07-31 Merged with new Toolkit 10.2 Some improvments: When you selected any option to remove all components and decided to return by answering "no" for some reason. You would always return to the Main Menu. In the Custom Toolkit when you answer "no" you are returned to the menu you were in. In previous Custom Toolkits I couldn't see a way to maintain the Original "Apply Tweaks Menu" without increasing the code size. But thanks to the changes that @MSMG made in the new version, it opened my eyes and I managed to put both menus. The original "Apply Tweaks Menu" back and the "Custom Apply Tweaks Menu". The problem was that when deciding to apply a tweak individually, fall into the system of applying all tweaks by answering questions. But now this is fixed. Edit: new updated file 2020-08-25 Thnks!
I know, but in my case I have not enabled it, I always do it on the first boot with SetupComplete.cmd, so I asked if I was doing something wrong
Hello friends & Master of toolkit on Windows 8.1 x64 integration: Although before the Net 3.5 integration, Cleanup op still getting ``Cannot Perform Image Component Cleanup when Pending.xml is present``...error BTW one quick question: what about if we skip the cleanup op then directly pick "apply" option? is "cleanup" op in mandatory? or just related wıth image size? thanks in advance..
Readme details about updates integration. I can't see your previous posts. I looked at ntlite forums and they suggest integrating updates and using the iso to update windows 10 keeping your files. I think their host refresh method does something similar. I read somewhere that updating with DISM is better since it doesn't add removed components, I'm not sure though.
With 1809 support ending November this year looks like those still on it (if not already been forced on to 2004), will have to upgrade or face the risks. I've avoided the upgrade because everything but Windows apps gets restored by a CU. I've spent some time working with Linux, but it doesn't run everything I need and Wine is not that great from my limited experience. I think it's fairly safe to say now (it's been almost 18 months since 1903 came out), there will never be a solution to "keep removed components removed", so it's going to be a process of disabling stuff, which in many cases doesn't actually completely disable stuff. With that in mind does anyone know any of the following; 1. Registry and group policy changes between 1809 and 1909. Microsoft used to publish a spreadsheet for this but from what I can tell, 1809 was the last time. There are some sites that talk about specific group policy additions, but I've not been able to find anything comprehensive. I'm particularly interested in registry settings. I have over 500 registry tweaks I do now. Don't want to make a change that breaks Windows. 2. I vaguely recall seeing something about end of life registry settings or some such for keeping components off the system. I don't recall where I saw it and I'm damned if I can find it again. Anyone heard of anything like that? 3. Can everything I want to disable, which is pretty much everything, be disabled via the toolkit? Looking through the release notes and readme.txt it looks as if a couple of components can be disabled but most cannot be disabled via the toolkit. Am I reading that correctly? I don't know how many things the toolkit removes, but if there are 100, I'm keeping around 5%. 4. Cortana, store and Defender seem to be three of the most resilient components and I don't want any of them anywhere near my systems. Perhaps I can remove them with the toolkit, and script something that I run after installing a CU to re-re-remove those components? But from memory, I think MSMG has said some things can't be accomplished with DISM? @MSMG can you confirm that. Or is it that DISM just doesn't remove all of a component? Sorry for the long post. No disrespect intended to anyone.
Yes in your case it was the enablement package (Edge Chromium) I was referring to the case of tefor that used clean 19041.1 and did not integrate the enablement package.
In Windows 7/8.1 several updates cause pending operations. Cleanup/resetbase is not mandatory and serves to reduce the size of the image by removing superseded files and updates. There is no side effect of not doing so and you can ignore it although the image size will be significantly larger. The ideal is to boot the image in audit mode and do the cleanup/resetbase then do sysprep and capture the image again to an install.wim file.
At least System Apps can be made completely inactive so you will have the same effect as removing them with the difference that they are still present in the SystemApps folder and the updates will not "restore" them. As for the other components I don't know if it is possible to disable them entirely since I continue to use versions 1809 and 1607. So in your case I think it's worth testing this: https://forums.mydigitallife.net/th...1803-1903-19h2-1909-20h1-and-ltsc-2019.80038/ Although I am not a fan of this script because in addition to its use having become very complex it adds several reg tweaks by default so things like autorun for example are disabled without asking the user. So if you are going to use this you will have to edit the script for your need and even this has become super complex.