@MSMG: Can you please release the toolkit as it is now? I really only need it working for x86 images. Cheers.
Exactly. We have no right to push MSMG for updates. If there is a rush for an update, then perhaps they could update the Toolkit themselves.
MSMG stated some time back in this thread he's working on a new version that fixes some issues including sfc errors (LTSC 2019 is covered by the latest version of the toolkit). So you have to wait with the rest of us for that.
Nobody else knows that better than me, and I've said it before. I was referring to MSMG's own comment that x86 was working without issues. Mind you that the English-only version also has been released as an "intermediate" release. You've been able to play with that, while multilang hasn't even't seen the first build. Just a request, not in any way to harass the devs. Cheers.
I look forward to a new version of MSMG ToolKit that works 100% well with Windows 10 Enterprise LTSC RDS5 1809 x64Bit, because I have to remove that annoying search and defender. MSMG ToolKit v9.1 does not seem very stable there is something wrong.
LTSC RDS5 1809 .379 after removing all coponents, dxwebsetup - gives an error message = dxerror.log & directx.log directx_Jun2010_redist.exe = works great.
Unfortunately the next version is not very promising for x64 builds as with the regular editions the setup is breaking when some apps are removed and with LTSC the setup is breaking even with the components working on regular editions. The ToolKit needs more time for testing for x64 images to fix the issues but anyhow will be releasing an update today.
That's unfortunate for me since I'm using LTSC x64. I regularly check this thread in hopes there will be a version at some point that has no ill effects on that image. For now I'm just disabling things rather than removing. When those issues get worked out I'll use the toolkit. At the minimum I want remove flash player from the installation image. There's just no way I can find to uninstall that package otherwise. In previous versions of Windows it's just a reg tweak to make the package visible and a call to dism /Remove-Package. They buried it in LTSC. Why did they do that, especially considering the damn thing will be deprecated next year. I can actually get ToolKitHelper.exe to work from a script for the most part, modified image installs without a problem. The main issue for me is it breaks the component store. Component cleanup after installation fails with a file not found error (dism /Cleanup-Image /StartComponentCleanup). Would also be good to see sfc run without flagging any files.
Do try out and see if it works for you if you are only removing few selected components and not all, It may work as my tests were with all components. Right now testing WHD update pack integration, once it's finished will upload the newer version.
I'll give it a try, let you know what happens. I'll start by removing flash player and see if any issues arise. Probably try it tomorrow or next day. Thanks for all your work on this. After looking into removing stuff with dism it seems like a bit of magic involved. They really made things convoluted with this new component store layout, at least in terms of identifying packages through the registry.
I used Toolkit 9.1 to make a new modified x64 iso. When install new windows, and after the last step, the screen becomes grey, nothing happens, but i still hear some windows sound. I press Windows + L to get out to lock screen and wait for some seconds and the desktop screen opens. I did not see any bugs on new windows installation. Everything work fine. Only Components cleanup is error and sfc/scannow recover some files. Code: C:\Windows\system32>DISM /Online /Cleanup-Image /StartComponentCleanup /ResetBase Deployment Image Servicing and Management tool Version: 10.0.17763.1 Image Version: 10.0.17763.1 [==== 7.2% ] [================ 28.7% ] Error: 2 The system cannot find the file specified. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log C:\Windows\system32> Code: 2019-03-19 05:32:31, Info CSI 00004c70 [SR] Beginning Verify and Repair transaction 2019-03-19 05:32:31, Info CSI 00004c71 [SR] Repairing corrupted file \??\C:\Windows\System32\\Windows.Data.Pdf.dll from store 2019-03-19 05:32:31, Info CSI 00004c72@2019/3/18:22:32:31.436 Primitive installers committed for repair 2019-03-19 05:32:31, Info CSI 00004c73 [SR] Repairing corrupted file \??\C:\Windows\System32\\iotstartup.exe from store 2019-03-19 05:32:31, Info CSI 00004c74@2019/3/18:22:32:31.530 Primitive installers committed for repair 2019-03-19 05:32:31, Info CSI 00004c75 [SR] Repairing corrupted file \??\C:\Windows\System32\en-US\\Windows.Data.Pdf.dll.mui from store 2019-03-19 05:32:31, Info CSI 00004c76@2019/3/18:22:32:31.639 CSIPERF - FileMapsCreated 112ms 2019-03-19 05:32:31, Info CSI 00004c77 CSIPERF - FilePI Commit 113ms 2019-03-19 05:32:31, Info CSI 00004c78@2019/3/18:22:32:31.655 Primitive installers committed for repair 2019-03-19 05:32:31, Info CSI 00004c79 [SR] Repairing corrupted file \??\C:\Windows\System32\\uwfcsp.dll from store 2019-03-19 05:32:31, Info CSI 00004c7a [SR] Repairing corrupted file \??\C:\Windows\System32\\uwfcfgmgmt.dll from store 2019-03-19 05:32:31, Info CSI 00004c7b@2019/3/18:22:32:31.733 Primitive installers committed for repair 2019-03-19 05:32:31, Info CSI 00004c7c [SR] Repairing corrupted file \??\C:\Windows\System32\\uwfservicingapi.dll from store 2019-03-19 05:32:31, Info CSI 00004c7d@2019/3/18:22:32:31.827 Primitive installers committed for repair 2019-03-19 05:32:31, Info CSI 00004c7e [SR] Repairing corrupted file \??\C:\ProgramData\Microsoft\Diagnosis\OfflineSettings\\offlineblocklist.json from store 2019-03-19 05:32:31, Info CSI 00004c7f [SR] Repairing corrupted file \??\C:\ProgramData\Microsoft\Diagnosis\WindowsAnalytics\\analyticsevents.dat from store 2019-03-19 05:32:31, Info CSI 00004c80@2019/3/18:22:32:31.842 Primitive installers committed for repair
Let me know if you get satisfactory results, I also want to remove it from the system LTSC x64, thk.-
Here's a little tidbit I received from Corsair today. I typically remove Windows error reporting, but Corsair tell me their iCue software depends on WER. So if you use Corsair AIO coolers with their iCue software WER should probably not be removed.
MDL Developer, does the new version support the removal of functions "Clipboard history" and "Timeline" ?