Right now there's no such option to remove all components (DISM+ToolKitHelper) at once. But from next version, as I said earlier the Toolkit will be fully using the manual method to remove the components for W10 RS3/RS4, so the option Remove Windows Components using the Package List can be modified to remove components using the manual method too, will implement it once I do finsh the manual method.
Dear Author Please Check Toolkit 8.8 Windows 10.1803 Remove Hyper-V Access Denied Error! Thanks! 1709 and 1607 Works OK!
I have just used this method with KB4343669 SSU and KB4343909 CU to see if this fixes the 0x800f081f I receive when Windows Update tries to install KB4457128 CU. However the error still persists. I have built another ISO with the current KB4456655 SSU and KB4457128 CU, so perhaps I will not got the error once the next CU is released on Windows Update. But this is making me much more weary about installing SSU's.
If you had integrated .NET FX35 before the Hyper-V removal, the DISM will not allow removing the Hyper-V. Do check whether you have integrated .NET FX35.
Do one thing when you use the ToolKit to integrate the updates, do not use the Apply->Apply & Save Changes to Source Images, instead manually save the image outside ToolKit, using the DISM inside a command prompt. Now test the image install and let me know if it works.
How do I do this? This is something I do not really understand, one of the reasons I use your Toolkit as it makes the task easy for me.
When the ToolKit's Apply->Apply & Save Changes to Source Images option is selected, the ToolKit will clean up the WinSxS's Backup and Temp folder and then proceeds to Saving the Image. So just wanted to make sure whether this cleanup thing is not breaking the WU. After the Integration of Updates, close the ToolKit and follow the below steps to manually save the image outside the ToolKit : - Open a Command Prompt (Admin) - Run the below command to save changes to the image. Code: DISM /UnMount-Image /MountDir:"<Path-To-ToolKit>\Mount\Boot\1>" /Commit DISM /UnMount-Image /MountDir:"<Path-To-ToolKit>\Mount\Boot\2>" /Commit DISM /UnMount-Image /MountDir:"<Path-To-ToolKit>\Mount\WinRE>" /Commit DISM /Unmount-Image /MountDir:"<Path-To-ToolKit>\Mount\Install>" /Commit - Now Again open the ToolKit and choose Apply->Re-Build Source Images
This is currently how I work my ISO image: Code: Integrate Win32 calculator (3 > 3 > B) Apply updates (3 > 4 > 2 > 1 > 3) Remove all metro apps and associations (4 > 1 > 5; 5 > 3) Remove connect, Onedrive, Skype (4 > 3 > A/B/C) Remove Store and People (4 > 3 > 2 > J/N) Windows Photo Viewer (5 > 5 > 6) Cleanup (6 > 1) Apply changes to image (6 > 2) Convert WIM to ESD (2 > 4) So I should not perform cleanup or apply changes, and do as you say?
Amazing tool, feature request though - Could we select multiple options with commas like - 1, 3, 4, 5 etc or remove all EXCEPT 1, 2, 3 for instance. Would bring down the time needed when we want one thing like calc.
For the test, skip both the cleanup and apply changes through the ToolKit, use the commands given earlier to save the image and then do the test. If it works, then perform the cleanup operation and skip the apply changes through the ToolKit, use the commands given earlier to save the image and then do the test. if it works then the post-cleanup operation under the apply changes might be breaking the WU.
I have ran the test slipping both cleanup and apply changes as you said. I still get the the 0x800f081f error in Windows Update when it tries to install "2018-09 Cumulative Update for Windows 10 Version 1803 for x86-based Systems (KB4457128)". This is on x86 en-gb Enterprise. If you want to check the machine with TeamViewer, this can be arranged. If you can arrange somewhere to upload large ISO images, I can upload what I have worked with.
I have the same problem like Feartamixg, I used to do the same routine in every ISO using your scripts and it always worked great. The first time I encountered this error was with a 1803 ISO. At first I thought it had to do with the fact I chose "Upgrade and Shutdown" because I read some references that there was a problem with hybrid shutdown and upgrade process with old hardware but I had the same issue even with new laptops. I also use abbodi1406's updater to update the ISO but I always used his scripts (part of the routine). By the way I was the one who proposed you to include that post-cleanup operation to your script.
Yes, I posted exactly how what I do here: https://forums.mydigitallife.net/threads/msmg-toolkit.50572/page-390#post-1461883 The only things missing are selecting source (1 > 3 then 1 > 1) at beginning, then saving as an ISO (7 > 1) at the end.
