https://forums.mydigitallife.net/threads/msmg-toolkit.50572/page-793#post-1606110 Sent an 2020-10-03 updated file in the link above. Spoiler: CHANGELOG 2020-10-03 I myself thought that, with 4 files to start the 4 toolkits, it was a little confusing... So, I decided to remove "Start.cmd", "Start_Beta.cmd", "CustomStart.cmd" and "CustomStart_Beta.cmd". So, in today's package, I put the file "GenericStart_LauncherMenu.cmd". I think that way, it gets better. Spoiler: CHANGELOG 2020-10-02 Merged with new MSMG Toolkit 10.6 and 10.7 Beta The files "CustomStart.cmd" to launch "CustomToolkit.cmd" and "Star.cmd" to launch MSMG Official "Toolkit.cmd" have always been made available in the CustomToolkit package. So that you can simply extract and start using. Now I renamed the Toolkit 10.7 Beta file to "Toolkit_Beta.cmd" and included a launcher for it. Included "CustomStart_Beta.cmd" to launch "CustomToolkit_Beta.cmd" and "Star_Beta.cmd" to launch MSMG Official "Toolkit_Beta.cmd". Simple and intuitive. Thnks!
19042.546.200926-1809.20H2_RELEASE_SVC_PROD3_CLIENTMULTI_X64FRE_RU-RU Used the Pro edition No matter how I tried, I can't do the cleaning ... Actions: 1) 8>1>C (Delete) 2) 1>([1] Select Source from <DVD> Folder) 3) Remove Windows Components Using Package List Spoiler: RemovePkgsList EdgeChromium SecurityCenter StepsRecorder EdgeDevToolsClient Edge OneDrive SmartScreen WindowsDefender WindowsReaderPDF 3DViewer AdvertisingXaml Alarms BingWeather Camera CommunicationsApps Cortana FeedbackHub GetHelp Getstarted Maps MixedRealityPortal OfficeHub OfficeOneNote Paint3D People ScreenSketch SkypeApp SoundRecorder StickyNotes WalletService XboxApp XboxIdentityProvider YourPhone 4) Cleanup Source Images ... -------------------------------------------------------------------------------------------- If you do this: 1) 8>1>C (Delete) 2) 1>([1] Select Source from <DVD> Folder) 3) Integrate [H] Extensions - HEIF, HEVC, MPEG2, VP9, Web, Webp Extensions 4) Integrate Microsoft Games 5) Remove Windows Components Using Package List Spoiler: RemovePkgsList EdgeChromium SecurityCenter StepsRecorder EdgeDevToolsClient Edge OneDrive SmartScreen WindowsDefender WindowsReaderPDF 3DViewer AdvertisingXaml Alarms BingWeather Camera CommunicationsApps Cortana FeedbackHub GetHelp Getstarted Maps MixedRealityPortal OfficeHub OfficeOneNote Paint3D People ScreenSketch SkypeApp SoundRecorder StickyNotes WalletService XboxApp XboxIdentityProvider YourPhone 6) Disable Windows Features Using Features List Spoiler: DisableFeaturesList WindowsMediaPlayer Internet-Explorer-Optional-amd64 WorkFolders-Client 7) Cleanup Source Images It turns out this error... SFC violations do not seem to cause
In v19042 you can't perform Cleanup due to Edge Chromium, The ToolKitHelper can remove Edge Chromium and it just removes the entries from pending.xml and not the pending.xml itself. Having a pending.xml present the Cleanup won't happen.
Adding W10 v19042 Enablement package adds Edge Chromium installer as a first run task and creates the pending.xml file which makes the cleanup not possible. I will add a workaround in the next release for people using Toolkit to integrate updates to 19041 image to skip integrating Edge Chromium while adding the W10 v19042 Enablement package.
Performed without clearing and no SFC violations detected. And if cleaning is done on the installed system, there are violations (Dism /Online /Cleanup-Image /StartComponentCleanup /ResetBase) Thanks. I'll wait for a fix ...
Can I remove media feature pack with this instead of just disabling it on LTSC? Don't want to use LTSC N due to no hwid activation.
He's probably about Windows Media Player. At LTSC edition "N" Windows Media Player is missing. If so, you can uninstall Windows Media Player.
I never removed "Desktop App Installer", even in the most min. config I tried ever. At least, last time I tried on STOCK Windows, without any modifications (original image). I'm also can't imagine what happens. Did you tried WT on you own W10? Which build you are using? Even on modified ISO it should install successfully using PowerShell. But interesting whether you have issues with launching *.exe, same as me or not.
Recently I am using 1909 18363.1082. It is very stable for the work PC. It started to increase the movement at work and, I'm kind of out of time to be a tester. On the gamer PCs of some friends and family that installed the 20H1 and 20H2 versions, we had problems, including untouched isos. For now, we decided to stay at 19H2. Microsoft is making very aggressive changes and, in my view, this proves to be an unstable stage. I rate it from the point of view of a linux beta and alpha tester user. Similarly considering the update cycles, status update protocols (alpha (unstable = SID) to beta (testing) and beta to stable) and currently, I see how Microsoft is similar in this regard. With reassurance ... Because the version considered unstable I have it as testing. And, Insider Preview as ultra-unstable as it is. So I ask myself: If the 19H2 version is stable, where's the testing version that should have been released instead of 2004 as stable? 2004 when it was released was unstable. Currently that 2004 is evolving to testing and then it could be quoted to become 20H2. And this 20H2, when more mature, quoted to 21H1. But who am I to determine something, right? hehehehe I'm not going to go deeper ... Just check out some new functionality and watch when it comes out in a version considered stable. In the current protocol, it can be said that a stage is burned transcending the unstable to stable. From my point of view, Microsoft has to improve the stage identification protocols. They are running over everything in favor of Marketing. The advertisements for the new features are very top, make the eyes shine, but major changes have to be implemented in shorter steps. Remembering, it's just my opinion. It is a speculation based on what I have been observing empirically over time, from Vista to 10.