I have uploaded the ToolKitHelper.exe with fixes for post-updates integration and also have added removal of new components like Ease Of Access Themes Multi Point Connector Windows Mixed Reality Windows Search Do test and report for any errors related to updates integration, other existing bugs related to IE, SmartScreen/Defender needs to be fixed yet. Windows Mixed Reality and Windows Search needs to be tested properly and so don't use it for production systems, these components need to be removed using the ToolKitHelper.exe in the NSudo command prompt. The ToolKitHelper.exe is uploaded at mega link, do download the file and copy it to ToolKit's bin folder and then use the ToolKit to remove the components. Name: ToolKitHelper.exe SHA1: A8ACE7C54922FBBB648495CB82272C9EBC7AF3BA
Still getting System.Reflection.TargetInvocationException... notification when removing apps (with start.cmd, .194, 4-1-1-8)
I used the version that was current in December of 2017, which looks like it might have been v8.0. I also recall recreating the image in March, which would have used v8.2. I'm going to recreate the 1709 image with v8.8 as you suggest, and I will again remove everything that the toolkit allows to be removed and see what happens. Thanks for your reply.
- Refreshed Images are not supproted - Use Start.cmd to run the ToolKit and make sure .NETFX472 is installed, If still error is happening then do specify the HOST OS.
Then need to figure out which component is breaking the Sysprep. Can yo do few tests by removing just the apps and then test the Sysprep?
Anyone tested the updates integration after removing the components using the newer version of ToolKitHelper.exe?
Yes, I have done this using en-US LTSC 1809 17763.1. I put *.msu files into WHD folder in right place up to 17763.195. No errors in logs, but when trying to install on formatted Hard Disk, setup copy then before "preparing" action I got the error "Windows cannot continue due to hardware.. blah blah. Integrate updates before removal does not provide any errors (tested).
I've found a solution to the UAC issue reported earlier. It was said that it is related to the removal of "SmartScreen" but I could not confirm this. Anyway, I'll document the issue and solution just in case someone runs into this. Issue: Some programs either complain that UAC is disabled, or they ask for admin rights while the user is already admin. Examples: Flash Updater, Shark007 codec pack, GPU-Z etc. Solution: After checking the "HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System" key, it was found that the UAC values were correct and at their defaults. Further checking revealed that the problematic programs were all 32 bit. Windows uses "registry reflection" for 32 bit apps. So I figured there would be another policy setting for UAC in the "HKLM\Software\WOW6432Node\Microsoft\Windows\CurrentVersion\Policies" key. After checking that key in the registry, it was found that there was no "system" key - Hence UAC error on 32 bit apps. I made a new key "System" and under that key two new dword values: ConsentPromptBehaviorAdmin and set it to "5" EnableLUA and set it to "1" After closing the registry editor the affected programs worked fine, reboot was not even needed. At this point I do not know whether those values exist in the original 1809 WIM (maybe someone can check). I also don't know if the key and values have been removed by running the toolkit script. Cheers.
Nice find! This fixed things for me as well. I did not remove any components with MSMG btw (just integrating updates), but instead thought the issue was related to applying Optimize Offline script by GodHand. But now I'm thinking/guessing the original WIM also has this issue.
Well, I also used GodHand's script and got the same issue. So obviously, I blamed it on his script. But then @metr metr reported it in this topic while removing smartscreen with the toolkit. So the next thing I did was going to GitHub and sift through the recent commits GodHand made to his script - I went back as far as the start of october 2018, but what do you know? Those keys are not modified by his script. So it is either some side effect from component removal, or it is a plain windows bug, as you say you did not remove anything. Let's see if we can pinpoint the cause. Cheers. Edit: After reading up on the UAC related keys in the registry, namely HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System and HKLM\Software\WOW6432Node\Microsoft\Windows\CurrentVersion\Policies\System You can even delete both keys and Windows -should- recreate them on restart. This is obviously not happening on the WOW6432Node part, so I'm inclined to believe that we have a Windows bug here.
Could anyone please help me, how can i include Windows defender updates? They all come as .exe files.