yeah, finally it comes! thank you for your work also want to ask, for next Win releases, like redstone 6, you will need to do same for all langpacks, or it stay the same and needs just a little corrections?
There's no order You mean to say offline installing updates after the OS installation using a cab file and then again checking with Windows Update?
I had checked with one Windows 10 v1903 x86 Host and a Windows 10 v1809 x64 HOST and on both the systems the component removal is working. Will try with a different HOST and see what's the result.
I said the current ToolKit won't work with both the x64 LTSC ISO's be it original release or the refreshed one.
What's the HOST OS you are using? I'm testing this issue will report back once I do replicate the issue. Integrating or Installing the updates after the component removal can restore empty folders like for defender the <Program Files\Windows Defender> will be re-created. I do check for the folder/file names for package existence since some packages doesn't have a proper package names.
What's the HOST and Source OS you used? Did the installation went fine? With en-US/en-GB x86 Images there are no issues for me if the component are removed in any order but with ru-RU image I got setup error when the Apps are removed and then found out the Image-Cleanup is causing the error, still need to do further tests to know whether that's the cause.
Now most of the MUI data to be removed is automated to get the data from the registry, only few lines of code are added manually which I have seen so far hasn't changed for all Windows 10 versions. If the newly added function to fetch the MUI data works properly then adding support for future builds will be easier. I do use the MUI Image for verification of ToolKitHelper.exe Log with the Component Removal Database.
Yes. But I did the test and removed CEIP_SQM , Kernel Debugging, UnifiedTelemetryClient, Windows Error Reporting - and got that when you install the update in the cab , the same update is again hanging in the update center. If you do not remove Windows Error Reporting, then everything is fine.
Wondering if anyone in this thread is familiar on what OneNote metro/UWP app dependencies are in order to have it working in Windows 10 (1809) with all the bloatware removed through MSMG toolkit? I tried to only keep OneNote metro/UWP app installed while all Windows-Apps, System-Apps, and Advanced-Components removed. No luck in doing so. Trying to migrate as OneNote Desktop is going to be EOL in the near future. Just curious if anyone has experimented on this or have a list of dependencies handy to ensure OneNote UWP/Metro is working with minimal bloatware remained in the system.
My bad ! I missed your statement https://forums.mydigitallife.net/threads/msmg-toolkit.50572/page-499#post-1510348 "I said the current ToolKit won't work with both the x64 LTSC ISO's be it original release or the refreshed one" My host OS is W10 LTSC x64, and I could produce clean lite ISO's using the 9.1 ToolKit with all updates integrated. Just some folders came back into systemapps after a WU update. Pakage Defender does not came back, but Cortana yes. but does not give errors into event viewer. Toolkit 9.2 give errors using the same strategy when removing Windows components... But It's normal... Will wait If you can solve why LTSC cannot be used. I thought the base ISO was the same as W10 1809 17763.1_Consumer with less crap. My goal is to keep my working machines clean and stable with no "New Features" every 6 months and risky updated full Windows.
The main question. Will there be support for 19H1 soon? After all, the update is soon, and you need to see how the removal of components will take place.
I have not yet deployed the image I made yesterday, but if the previous faulty image installed fine, this one will be OK also. Host OS is English LTSC x64 (1809). Source OS is Spanish LTSC x86 (1809). I did remove some system apps and advanced components. Both without any error. Workflow: - Extract ISO to DVD folder - Run start.cmd and mount all images (recovery and boot) - Integrate Edge, Dart, DX9, camera app, alarms and clock, store. - Integrate WHD updates (CU, servicing stack, flash, dotnetfx januari + dotnetfx march). - Remove some System apps - Remove some advanced components like defender and smartscreen - Manually do cleanup + resetbase from cmd - Rebuild images with toolkit - Apply changes and dismount. For x86 it was a flawless run. Important: To avoid the errors reported here, you must use "integrate WHD updates" option from the toolkit. If you use the normal updates folder you get errors. If you use Abbodi's WUI you will also get the errors. It seems that only the toolkit integrates the updates in a specific order. Once I used "Integrate WHD updates" it all finished without any issue. I do not pre-integrate .net 3.5 as I got fed up with pending flag set. I now do it from ROE as part of the application install. I probably could remove more stuff, but I prefer to wait and test exactly what components can be safely removed without causing sfc errors. It has been said before, to much chopping is no good. So far I'm happy with the build process. When I have the change I'll deploy the image and see how it behaves. Cheers.
If you are using LTSB 2016, then you need to work with an older version of the toolkit. This has been asked before and answered. Cheers.
I want to use the “remove” features make a ltsb 2016 lite-version.But when I press [4]remove，the screen will turn to tweak menu. My OS is 1809，lastest version.
If you are using LTSB 2016, then you need to work with an older version of the toolkit. This has been asked before and answered. Cheers.
If you remove Internet Explorer, Windows Media Player, then there will be no problems with programs that require these components?
