I would say because you stubbornly refuse to acknowledge that the code is buggy. It works only if you place Toolkit folder in a root dir (C:\ or D:\). I've moved Toolkit folder to D:\ and everything was ok. Ten years and 1225 pages to find out. Never had similar problem using DISM.
You could have saved a lot of time energy by just following the instructions included with the ToolKit.
Updated the Toolkit to v13.2 Spoiler: Change-log v13.2 + Updated Toolkit's Bin folder with Windows 11 v22H2 Insider Preview WADK (v10.0.25281.1000) Tools. + Updated the Microsoft .NET 6 Desktop Runtime Pack (Windows 7/Windows 8.1/Windows 10/Windows 11) with Microsoft .NET Desktop Runtime 6.0.13 Runtime. + Updated the Microsoft .NET 7 Desktop Runtime Pack (Windows 7/Windows 8.1/Windows 10/Windows 11) with Microsoft .NET Desktop Runtime 7.0.2 Runtime. + Updated the Microsoft Edge Chromium Browser Pack (Windows 7/Windows 8.1) with Microsoft Edge Chromium v109.0.1518.61 setup files. + Updated the Microsoft Edge Chromium Browser Pack for MSMG Toolkit with updated Microsoft Edge Chromium Group Policy Definitions files. + Updated the Microsoft Edge WebView 2 Runtime Pack (Windows 7/8.1/Windows 10) with Microsoft Edge WebView 2 Runtime 1.3.171.39 setup files. + Updated the Mozilla Firefox Browser Pack (Windows 7/Windows 8.1/Windows 10/Windows 11) with Firefox 109.0 setup files. + Updated the Feature "Integrate Microsoft DaRT Tools" with Windows 11 v22H2 (v10.0.22621.755) Debug Tools. + Added a Feature "Integrate Microsoft Classic Paint". + Added the Microsoft Classic Paint Pack (Windows 11) with Microsoft Classic Paint binary files. + Updated the Feature "Integrate Microsoft Default Inbox Apps" to support new dependency packages. + Updated the Feature "Remove Windows Component" to support Windows 10 Client v1809/LTSC2019 (v10.0.17763.1/v10.0.17763.3887 [KB5022286]) Source OS. + Updated the Feature "Remove Windows Component" to support Windows 10 Client v1903 (v10.0.18362.1) & v1903/v1909 (v10.0.1836x.2274 [KB5013945]) Source OS. + Updated the Feature "Remove Windows Component" to support Windows 10 Client v2004 (v10.0.19041.1) & v2004/v20H2/v21H1/v21H2 (v10.0.1904x.2486 [KB5022282]), LTSC2021 (v10.0.19044.1288/v10.0.19044.2486 [KB5022282]) Source OS. + Updated the Feature "Remove Windows Component" to support Windows 11 Client v21H2 (v10.0.22000.1/v10.0.22000.1455 [KB5022287]) Source OS. + Updated the Feature "Remove Windows Component" to support Windows 11 Client v22H2 (v10.0.22621.1/v10.0.2262x.1105 [KB5022303]) Source OS. + Optimized the Toolkit code (Thanks to MDL Members : inTerActionVRI). Also have uploaded Google Chrome Browser, StartIsBack, StartAllBack Pack for testing.
MSMG thanks for all the hard work on this much apricated. Also I believe that the VCRUNTIME pack is corrupted it took me several hours to figure out that pack is what was causing my SFC errors. Please have a look at the pack. Thanks, Dean
When using MSMG on Windows 11 Professional Workstation N, does anybody know what components I need to preserve the ability of Windows Explorer to navigate my mobile phone files and to be able to view Windows *.xps files? Everything else was working fine.
Are you using the refreshed images provided by MS or do you use the [1] Cleanup Source Images using DISM Cleanup-Image menu in Apply menu? If yes then it creates ghost SFC errors, If not then will check the pack and fix the errors.
refreshed image I made with the updates and I am not using the [1] Cleanup Source Images using DISM Cleanup-Image menu in Apply menu? If I do not use the VCRUNTIME pack I get no errors and the build it perfect. I have spent hours trying to figure it out I started by building the image one step at a time and installing in a Virtualbox VM. I never though to check the packs as I never had a problem with then on my WIN10 build. I will try it with the original MS WIN11_22H2 release and see if I still get the errors. I will report back in a few. Thanks
Hey! How to integrate the StartIsBack package in Windows 10 Pro 19045? In MSMG Toolkit V.13.2 there is no string StartIsAllBack to integrate this package.
Already answered (never had the "path issue" with DISM). Does anyone know why it's not possibile to sign in Microsoft Office? What packages should you keep? All the ones related to Microsoft account?
what happens if i delete windows defender and then update windows through windows update? does it install windows defender again?
Hi, is there a way to edit/create tpk files on my own? For example with StartIsBack, I'd like to integrate additional start orbs into the tpk or with PowerShell7, I'd like to integrate the x64 binaries only (already edited the reg file to remove all x86 entries & relatives and then I manually delete the x86 files from the mount dir using nsudo to elevate a script that deletes them). I tried mounting one of those separately but I got an error doing so because no "architecture is defined in the wim file".