I really hate to ask anything more as I don't want to slow you down, but would it be possible for you to create a 9.0 "unlocked/test version" of ToolKitHelper.exe with WinSxS clean up switched on for testing instead? I'm positive I'll mess things up otherwise, I'm not familiar enough yet. I can test one advanced component at a time and let you know my results. I think I know how to see SFC and SxS repair results as well so I can at least give you some real detail. I have a 4790k overclocked to match a 7700k stock so I can process builds quickly at least.
UnifiedTelemetryClient removal needs to be refined for each Windows 10 versions, will see what I can do to fix mail and calendar Apps.
You can replace the ToolKitHelper.exe from v8.9 to v9.0 since both are same only the WinSxS component cleanup is disabled in v9.0
So Copy/Extract the Toolkit archive to C:\Toolkit and do the following steps - Mount the source image using the ToolKit - In C:\Toolkit\Bin\x64 folder ther's a NSudo.exe, double click on it. - Choose "Enable All Privileges" in the NSudo Dialog Box. - Type "cmd" in the NSudo Dialog Box's TextBox. - Choose Run from NSudo Dialog Box and it will open a cmd window. - Now in the command window type C:\Toolkit - Now Run the below commands to see if it works Bin\ToolKitHelper.exe mount\install /?
Yes that's the way to run the ToolKitHelper.exe manually, In future version I will remove the need of NSudo for ToolKitHelper.exe so that it works with normal command prompt. - Mount the source image using the ToolKit - In C:\Toolkit\Bin\x64 folder ther's a NSudo.exe, double click on it. - Choose "Enable All Privileges" in the NSudo Dialog Box. - Type "cmd" in the NSudo Dialog Box's TextBox. - Choose Run from NSudo Dialog Box and it will open a cmd window. - Now in the command window type cd C:\Toolkit Bin\ToolKitHelper.exe mount\install /? will get the list of components available for removal for the given image. Bin\ToolKitHelper.exe mount\install <ComponentName> removes the specified component name.
Please forgive me if this is a tad off topic. I created an 1809 ISO from the original esd (not the refresh) using MSMG v9.0 and installed on my Test PC. I have written a script which tweaks many of the settings which essentially tuns several hours of configuration and application installation into a few minutes work. One of the things this script does is to Deny/Disable/Turn off App Privacy settings. There are some registry entries that end with _cw5n1h2txyewy in the consentstore branch. On my 1709 PC the consentstore branch is empty, but when I was looking for info on contentdelivery I noticed in C:\Users\Tanya\AppData\Local\Packages that the package names have the same value of _cw5n1h2txyewy Can anyone confirm if this _cw5n1h2txyewy is consistent across Windows versions and safe for me to code in my script to set the values to Deny?
Sorry for the trivial question. I ask if there is a way to avoid all requests during the installation of ISO, or you can set them via tools. Thanks
@Yanta: I have packages with that same string in my folder on 1809. But not all the packages carry the same string. @MIMMO61: Yes you can make an "unattend.xml" file to achieve that. Cheers.
Yes, I noticed a couple of different strings. As long as they are consistent across all 1809 installations I'm good to go. thanks for your help.
True but there's no posts available for it. Would be cool if we had our own subforum like WHD and a few others
Am I missing something. I'm getting everything removed and burning it to an ISO. After I install, everything is still there. I got it working on my desktop, but can't remember exactly how I did it.