Do read the change log, the component removal is only for en-GB/en-US source images and it may or may not work with other languages. Also whatever present in the change log will be one available in the ToolKit, win32calc will be added when it's ready. DirectX 9.0c Pack integration won't show any listing in the Programs and Features, you can check it by running dxdiag.exe from run command or running any program/games that require DirectX 9.0c.
Thanks, I have successfully made an ISO from 1809 LTSC x64 , removing : "People Experience Host Skype ORTC Home Group Take Test App Microsoft Xbox HomeGroup Unified Telemetry Customer Experience Improvement Program Xbox components " Problem : When fresh install on HDD the installation of low drivers for motherboard, and Window Update seems broken. Windows does not install Low level drivers (Intel) , PCI to PCIexpress Bridge , and Windows update failed to install the two updates SSU + KB xxx30 giving you 17763.55. Maybe I have made something wrong ?
I haven't tested the x64 image + Asimov yet with WU and if the Installation of Drivers not working then it will be due removing the Unified Telemetry Client. I have tested the WU updates installation with x86 image it has worked so far, will test the x64 image and report back.
Afters removing UnifiedTelemetryClient from LSTC 1809 N file CompatTelRunner.exe still present in Windows\System32 directory. Plus getting error 0x800f0982 now when trying install Cumulative Update 2018-10 KB4464330 on fresh system. Acording NTLite forum it caused by "1809’s new PSFX update format compatibility after removals (error 0x800f0982)".
I got the very same Windows Update errors numbers when trying to update, plus the low drivers not installing. LTSC 2019. No error when removing components with Toolkit. (Log)
Unified Telemetry Client removal varies for different W10 builds and it needs further tweaking for complete removal. Cleaning up WinSXS for removed components will break WU with the new PSFX update format and leaving them alone will also gives errors with SFC /scannow. That's why I have put a switch inside the ToolKitHelper.exe for cleaning up WinSXS and currently it is set to true, So far my tests with x86 build the WU is working as you can read back few pages where I have posted my results and the WU installs the updates properly. Need to test the x64 builds yet to know whether it works or not.
This will now be my method Does it seem okay? Code: Integrate Win32 calculator (3 > 3 > B) Cleanup (6 > 1) Remove all metro apps (4 > 1 > 1) Remove Onedrive, People, Connect, Skype, Store, Xbox, Game bar, Xbox ID (K/M/N/S/U/X/Y/Z) Apply updates (3 > 4 > 2 > 1 > 3) Cleanup (6 > 1) Windows Photo Viewer (5 > 5 > 6) Apply changes to image (6 > 2) Rebuild (6 > 1) Convert WIM to ESD (2 > 4)
Windows 10 Professional en-gb tested, no problems. Just the menu error that I reported previously: https://forums.mydigitallife.net/threads/msmg-toolkit.50572/page-409#post-1480676
the things i do with your toolkit is usually repetitive. it'd be really nice if its possible to actually put together a list of tasks to automate everything. i did some of that in the past, the real bother is that after each option is selected, theres often a 'press any key' at the end of it. if only its possible to mount -> integrate -> remove -> clean -> save all at once without prompts unless a command is errorlevel neq 0... which is where it should stop
That's the difference b/w the ToolKit and the rest of the other scripts, while all other scripts give an option at the beginning and perform the task without any user interference till the end the task is complete, the ToolKit does provides the user the freedom to choose the tasks and the order of executing those tasks. While all other script are intended to do a particular tasks like integrating updates, creating an ISO, converting edition etc.. The ToolKit is a All-In-One tool and so it differs from other scripts. For people who can't remove apps/components one by one, I have given the choice to remove them all at once using the Packages list.
No buddy. The above error is because toolkithelper.exe is missing in the bin folder. Just check if the bin folder has toolkithelper.exe. I think it may have been deleted by your antivirus.
If file got flagged, disabling AV is contra-productive. Re-enable and create an exclusion for the folder you try to unpack to.