Is it normal for Component Store to become corrupt as using MSMG Toolkit? I didn't integrate anything, but removed a ton of stuff. I assumed MSMG Toolkit could preseve Component Store and file integrity. If aditional cleaing from Toolkit Helper is what causes corruption, then can we get an option to not use it and get limited feature removal that preserves Component Store and file integrity? Also, can MSMG Toolkit remove dependence of Windows PE (Index 2) in boot.wim? I remove Windows PE from boot.wim and that results in MSMG Toolkit displaying an error that it can't find Index 2.
Removing too much can always cause errors. MSMG isnt perfect and with MS updating stuff "constantly" its more difficult to maintain a proper working tool I guess.
i think none of the .NET Core / .NET versions are backwards compatible fully, there is always some sort of binary or source incompatibility resulting in various degrees of breakage, which is why they are all co-installable you can target multiple .NET versions in your app, but its safe to assume that it will always require manual changes. for the MSVC case, yes they are (mostly) binary compatible, which is why 2022 shares the major version with 2015, although there are still some restrictions: - an Application built with 2022 must use a 2022 runtime, an app built with 2015 can use a 2015; or anything up to (currently) a 2022 runtime - there are some compiler flags which break this for Static libraries or object files ( namely /GL and /LTCG ), but this is only relevant for building an app, not running iit.
If using the source image with right CU specified in the latest changelog.txt then removing components won't corrupt the component store, do specify the source image used? Using Cleanup Image (DISM /Cleanup-Image /StartComponentCleanup /ResetBase) will give a ghost SFC error. Adding support for skipping Boot.wim (Index 2) needs modification for all Toolkit features related to boot.wim image, will see what can be done.
Code: echo.------------------------------------------------------------------------------- echo.####Integrating Firefox ############################### echo.------------------------------------------------------------------------------- for /l %%i in (1, 1, %ImageCount%) do ( if exist "%InstallMount%\%%i" ( echo. if not %%i gtr 9 echo.===========================[Install.wim, Index : %%i]============================ if %%i gtr 9 echo.==========================[Install.wim, Index : %%i]============================ echo. :: Getting Image Index Information call :GetImageIndexInfo "%InstallWim%", %%i >nul echo.------------------------------------------------------------------------------- echo.Integrating Firefox Browser ... echo.------------------------------------------------------------------------------- call :ApplyImage "%Firefox%\Firefox_%SelectedSourceOS%.tpk", %PackageIndex%, "%InstallMount%\%%i" echo.------------------------------------------------------------------------------- echo.Importing Firefox Browser Registry Settings... echo.------------------------------------------------------------------------------- echo. echo.Mounting Image Registry... call :MountImageRegistry "%InstallMount%\%%i" echo.Importing Registry Settings to Image Registry... call :ImportRegistry2Image "%Firefox%\Firefox_%SelectedSourceOS%_%ImageArchitecture%.reg" echo.Un-Mounting Image Registry... call :UnMountImageRegistry echo. ) ) echo.------------------------------------------------------------------------------- echo.####Finished Integrating Firefox Browser###################### echo.------------------------------------------------------------------------------- :Stop echo. echo.=============================================================================== echo. pause
there is 12.9 there, wait for the MSMG to update or put it in some block using the paths and variables, the one I gave you was just an example of how you can install it every time it updates the .tpk and the reg, it will only change the variables, but it's the same thing everything applied the .tpk and import the .reg
False alarm. What causes Component Store corruption in Windows 10 is disabling (not removing) Optional Features and then rebasing the image.I am not sure which features are the issue, but its not related to MSMG Toolkit. Can you add option for Home editions to have GPEDIT.MSC and Local Sucurity Policy package? Or is it part of RSAT pack? GPEDIT can be added via DISM to any edition of Windows 10/11 like this: Code: @echo off pushd "%~dp0" dir /b %SystemRoot%\servicing\Packages\Microsoft-Windows-GroupPolicy-ClientExtensions-Package~3*.mum >List.txt dir /b %SystemRoot%\servicing\Packages\Microsoft-Windows-GroupPolicy-ClientTools-Package~3*.mum >>List.txt for /f %%i in ('findstr /i . List.txt 2^>nul') do dism /online /norestart /add-package:"%SystemRoot%\servicing\Packages\%%i" pause Is it possible to add BitLocker support via DISM to Home editions? The pack for MP3/Multimedia codecs is missing.