If you have copied the source image files directly from the DVD ISO image and the <Toolkit\DVD\sources\sxs> folder is present then you don't need the .NetFX35 pack, just go to Integrate->Windows Feature->Microsoft .NET Framework 3.5 menu. If the <Toolkit\DVD\sources\sxs> doesn't contain in your source, then copy the v1809 .net framework pack provided by Toolkit, to <Packs\NetFX35\w10\10.0.17763> folder. The .NET Framework 4.8 packs files should be copied to <Packs\NetFX48\w10> folder and the menu to integrate is present in Integrate->Windows Feature menu. Which source edition are you using?
Actually the version that i want to integrate the Net framework is 1903, in Windows 10 1903 as host system. Sorry for the mistake, and the error persists.
Actually, i confuse me, the folder (ISO) that i want to integrate is the Windows 10 1903, in a Windows 10 1903 as host. I copied the NET35 pack with 3 .cab files provided by toolkit into the folder "MSMG/Packs/NetFX35/w10", and the mentioned error appears. And the NET48 is already included in 1903 version, thats why. My bad. I'm new in this.
copy the v1809 .net 3.5 framework pack files provided by Toolkit to <Packs\NetFX35\w10\10.0.18362> folder.
Oh, just before I reinstalled Windows 10, seems 19H2 has come Anyone knows if it will be called 1909 ( therefore MSMG will support ) or an 18362.XXXX version? If 1909, will keep waiting.
We have 18363.32x+ since august 30. 2019 available and it's 1909: https://forums.mydigitallife.net/th...pc-19h1-2-release.79259/page-282#post-1551877
Hey, Few months ago I tried v1903 but it wasn't fully supported yet (Windows update and some features were reinstalled) so I want to make sure : Should I try again with v1903, or stick with v1809 this time ? Thanks again for your amazing work
Is the "RemoveAppsList_W10_10.0.18362_Template" The complete list for apps? Not for features but the Apps.
@MSMG Hi please I would love to know when the latest version of the Toolkit 9.4.2 now can be used to work with Windows 8.1 ISO's so right now I am very grateful
both v1903 and v1909 are supported but the removed components do get returned as soon as you use the Windows Update or integrate/install updates, yet a fix is to be worked out.
Yes the list is complete for using it with Remove Windows Apps using Apps List which uses the DISM to remove the components.
If it's about using the latest version of Toolkit to intergate/enable/disable/customize then it's already working. If it's about using the latest version of Toolkit to remove components then it will take time as I haven't decided yet to whether to use a Windows 7/8.1 base image or with updates for component removal. Let me fix this v1903/v1909 component returning issue, then will think about it.
I am trying to follow your list but when i am trying to remove components i got message that build is not supported ? i have integrated following updates: windows10.0-kb4517389-x64_6292f6cb3cdf039f01410b509f8addcec8a89450.msu windows10.0-kb4462930-x86_ee44cbbd86b3271990ccc472760f0228094131e5.msu windows10.0-kb4486553-x64_0c3111b07c3e2a33d66fed4a66c67dec989950a0.msu windows10.0-kb4521863-x64_a26672b0d37671b49d9306874bfab9db47007ddb.msu
https://forums.mydigitallife.net/threads/msmg-toolkit.50572/page-642#post-1553761 Note: you need to modify the Toolkit.cmd to remove the condition put in Remove Components Menu to check for v1903 ServicePackBuild.