I have just finished coding half the components, few more components are left and then need to test the ToolKit for any errors, it may take few more days may be by Sunday it will be ready.
My previous tests were done when the first CU was released for RS4 and removing Unified Telemetry Client under Telemetry components was causing failure of downloading Drivers through Windows Update. But the CU was downloaded and got updated properly through Windows Update, you can see it here https://forums.mydigitallife.net/threads/msmg-toolkit.50572/page-339#post-1436527 Will test with the new CU after updating the ToolKitHelper.exe and report back.
I have added code protection for ToolKitHelper.exe which also compresses the exe and this causes the AV to raise a false alarm, don't worry about it.
Yes, Microsoft-Windows-WinPE-AppxPackaging-Package is only for Winre.wim. Only the Microsoft-Windows-WinPE-OpcServices-Package is not available anywhere to complete the pack. Boot.wim, Index:1 Code: Microsoft-Windows-WinPE-LanguagePack-Package~31bf3856ad364e35~amd64~en-GB~10.0.17133.1 WinPE-ATBroker-Package~31bf3856ad364e35~amd64~en-GB~10.0.17133.1 WinPE-AudioCore-Package~31bf3856ad364e35~amd64~en-GB~10.0.17133.1 WinPE-AudioDrivers-Package~31bf3856ad364e35~amd64~en-GB~10.0.17133.1 WinPE-EnhancedStorage-Package~31bf3856ad364e35~amd64~en-GB~10.0.17133.1 WinPE-Narrator-Package~31bf3856ad364e35~amd64~en-GB~10.0.17133.1 WinPE-Scripting-Package~31bf3856ad364e35~amd64~en-GB~10.0.17133.1 WinPE-SecureStartup-Package~31bf3856ad364e35~amd64~en-GB~10.0.17133.1 WinPE-Speech-TTS-en-GB-Package~31bf3856ad364e35~amd64~~10.0.17133.1 WinPE-Speech-TTS-Package~31bf3856ad364e35~amd64~en-GB~10.0.17133.1 WinPE-SRH-Package~31bf3856ad364e35~amd64~en-GB~10.0.17133.1 WinPE-SRT-Package~31bf3856ad364e35~amd64~en-GB~10.0.17133.1 WinPE-WDS-Tools-Package~31bf3856ad364e35~amd64~en-GB~10.0.17133.1 WinPE-WMI-Package~31bf3856ad364e35~amd64~en-GB~10.0.17133.1 Boot.wim, Index:2 Code: Microsoft-Windows-WinPE-LanguagePack-Package~31bf3856ad364e35~amd64~en-GB~10.0.17133.1 WinPE-ATBroker-Package~31bf3856ad364e35~amd64~en-GB~10.0.17133.1 WinPE-AudioCore-Package~31bf3856ad364e35~amd64~en-GB~10.0.17133.1 WinPE-AudioDrivers-Package~31bf3856ad364e35~amd64~en-GB~10.0.17133.1 WinPE-EnhancedStorage-Package~31bf3856ad364e35~amd64~en-GB~10.0.17133.1 WinPE-Narrator-Package~31bf3856ad364e35~amd64~en-GB~10.0.17133.1 WinPE-Scripting-Package~31bf3856ad364e35~amd64~en-GB~10.0.17133.1 WinPE-SecureStartup-Package~31bf3856ad364e35~amd64~en-GB~10.0.17133.1 WinPE-Setup-Client-Package~31bf3856ad364e35~amd64~en-GB~10.0.17133.1 WinPE-Setup-Package~31bf3856ad364e35~amd64~en-GB~10.0.17133.1 WinPE-Speech-TTS-en-GB-Package~31bf3856ad364e35~amd64~~10.0.17133.1 WinPE-Speech-TTS-Package~31bf3856ad364e35~amd64~en-GB~10.0.17133.1 WinPE-SRH-Package~31bf3856ad364e35~amd64~en-GB~10.0.17133.1 WinPE-SRT-Package~31bf3856ad364e35~amd64~en-GB~10.0.17133.1 WinPE-WDS-Tools-Package~31bf3856ad364e35~amd64~en-GB~10.0.17133.1 WinPE-WMI-Package~31bf3856ad364e35~amd64~en-GB~10.0.17133.1 Winre.wim, Index:1 Code: Microsoft-Windows-WinPE-AppxPackaging-Package~31bf3856ad364e35~amd64~en-GB~10.0.17133.1 Microsoft-Windows-WinPE-LanguagePack-Package~31bf3856ad364e35~amd64~en-GB~10.0.17133.1 Microsoft-Windows-WinPE-OpcServices-Package~31bf3856ad364e35~amd64~en-GB~10.0.17133.1 WinPE-AppxPackaging-Package~31bf3856ad364e35~amd64~en-GB~10.0.17133.1 WinPE-ATBroker-Package~31bf3856ad364e35~amd64~en-GB~10.0.17133.1 WinPE-AudioCore-Package~31bf3856ad364e35~amd64~en-GB~10.0.17133.1 WinPE-AudioDrivers-Package~31bf3856ad364e35~amd64~en-GB~10.0.17133.1 WinPE-EnhancedStorage-Package~31bf3856ad364e35~amd64~en-GB~10.0.17133.1 WinPE-HTA-Package~31bf3856ad364e35~amd64~en-GB~10.0.17133.1 WinPE-Narrator-Package~31bf3856ad364e35~amd64~en-GB~10.0.17133.1 WinPE-OpcServices-Package~31bf3856ad364e35~amd64~en-GB~10.0.17133.1 WinPE-Rejuv-Package~31bf3856ad364e35~amd64~en-GB~10.0.17133.1 WinPE-Scripting-Package~31bf3856ad364e35~amd64~en-GB~10.0.17133.1 WinPE-SecureStartup-Package~31bf3856ad364e35~amd64~en-GB~10.0.17133.1 WinPE-Speech-TTS-en-GB-Package~31bf3856ad364e35~amd64~~10.0.17133.1 WinPE-Speech-TTS-Package~31bf3856ad364e35~amd64~en-GB~10.0.17133.1 WinPE-SRH-Package~31bf3856ad364e35~amd64~en-GB~10.0.17133.1 WinPE-SRT-Package~31bf3856ad364e35~amd64~en-GB~10.0.17133.1 WinPE-StorageWMI-Package~31bf3856ad364e35~amd64~en-GB~10.0.17133.1 WinPE-WDS-Tools-Package~31bf3856ad364e35~amd64~en-GB~10.0.17133.1 WinPE-WiFi-Package~31bf3856ad364e35~amd64~en-GB~10.0.17133.1 WinPE-WMI-Package~31bf3856ad364e35~amd64~en-GB~10.0.17133.1
The windows gaming overlay that pops up whenever you run anything remotely close to "gaming"? Is there a way to remove that as well? I removed the store, but now is there a way to completely get rid of the overlay? If not, thats ok too. Basically looks like the included capture. Never have that come up?
I live in Turkey and Cortana in my country is not being used. When we delete Cortana we also delete the search option from the start menu. Do we have a chance to separate these two and just delete cortana?
The DISM method of component removal doesn't fully remove the component related files/registry entries and that's why the ToolKitHelper.exe was introduced which uses the manual method to remove a component. At present the ToolKitHelper.exe can remove Xbox and Store for only RS3, for RS4 you will need to wait for the next release.
At present no you can't separate them, the best is you can disable Cortana and keep the search functionality.
hmm, people wait Dev works this is one difficult operations to make, wait, wait when our master Dev. Chief and 1@ dev on MDL anyone can run only patience please this is one big WORK remember , here is not NTLITE , here is MDL think
Hey there, one quick question: Are all the packs except dotnet35_rs4 optional using win 1803? Or are they all "required" for msmg (latest 8.6.7) to work properly? Thanks!
All packs are optional, including Net3.5. The toolkit wil work properly without. It just depends on WHAT you want to integrate, according to your preferences you need the packs. BTW, I use the net3.5 from the source folder, not the MSMG pack. Cheers.
laziness often kill the user's success by not knowing READ text (or better to read the text correctly before any modification is absurd it will never work of course oh my good GOD nor at least you can solve !!I'm wrong ....
Yeah I know, I just don't want to be an ass on the forums. And when I see @Enthousiast being so patient with other members, I admire that. Really. Cheers.