Yes, i stand corrected. I was focused on component removal. As i said I still find MSMG is useful for lots of things, but for me using an autounattend.xml file is faster and more reliable for component removal and tweak adjustments. There are lots of tools to mount install.wim but MSMG & autounattend.xml works best for me. Not throwing shade at all and never said any approach was "best".
Dear @inTerActionVRI do you know if there are new VCRuntime VC.tpk files to integrate in windows 10 iso with MSMG ToolKit ? The last one are from june 2023 ... Thanks in advance!!!
Thanks , my SetupComplete looks like this : @echo off %SystemDrive% label %SystemDrive% SISTEM Compact /CompactOS:always compact /c /s /i /a /exe:XPRESS8K "%SystemDrive%\*" powercfg /hibernate off net accounts /maxpwage:unlimited netsh advfirewall set allprofiles state off >nul call "%WINDIR%\Setup\Scripts\Tweaks.bat" shutdown /r /t 6 del /q /f "%0" where i have in folder Scripts the 2 files : SetupComplete Tweaks can i add in the folder : DirectX_Redist_Repack_x86_x64.exe VisualCppRedist_AIO_x86_x64.exe ??? and what command should i add ? Thanks for any advice !!!
Yes, you can add almost any executable app that has a silent install switch, just precede the file name with Code: START /WAIT %~dp0\ to let Windows setup know to expand to current directory path of the running batch file to locate your setup file. VisualCppRedist_AIO_x86_x64.exe is shown in my code example, above. I don't know the silent install command for DirectX. Hope that helps.
If you disable hibernation you will disable hiberboot. This will slow down you windows boot speed. Enabling hibernation again will not be enough to reactivate the hiberboot function. Regarding the TPKs, only MSMG updates these files; literally the most current TPKs are those available in the MSMG repositories. I also use something similar to SetupComplete. And I integrate the abbodi packages.
Thanks for this tip , but i build my lite Windows and on boot i have only 60 services running and it starts in 5 to 8 seconds since i press the start button. I do not find hibernation necessary for my day to day usage. I consider it uses a lot of unnecessary services running in the sleep mode and this uses a lot of memory .
Greetings! Something I don't understand... Microsoft began to selectively remove applications installed through the Msmg Toolkit... This has never happened before... I tried it in different ways... for example, I use the Windows 10 Pro 20H1_19041.1 image, I integrate it through the Toolkit ("C:\Toolkit\Packs\Apps "), for example: Microsoft.AV1VideoExtension_1.2.2331.0_neutral_~_8wekyb3d8bbwe Microsoft.HEVCVideoExtension_2.1.2191.0_neutral_~_8wekyb3d8bbwe Microsoft.MPEG2VideoExtension_1.0.61931.0_neutral_~_8wekyb3d8bbwe I check through Dism++: everything is installed. Integrating updates to Windows 10 Pro 22H2_19045.4842 Checking through Dism++ : extensions are in place. I install Windows, there are no extensions that I integrated ... I go to the folder along the path: "C:\Program Files\WindowsApps" and I see that a new folder "DeletedAllUserPackages" has been created ("C:\Program Files\WindowsApps\DeletedAllUserPackages") and my extensions integrated through the Toolkit in it. It turns out that during the installation of Windows... selective applications and extensions are removed ... I tried to integrate after updating Windows immediately on Windows 10 Pro 22H2_19045.4842... the same "trouble"( Maybe there is a workaround so that integrated applications and extensions are not deleted during the Windows installation process?
Download 22H2_19045.4842 from uup dump go to config file remove and add whatever you like install windows and see if it works. That's what I would probably do.
Check if these versions are still compatible with Windows 10. Check min supported build version in "*Manifest.xml". Just examples... Pay attention on MaxVersionTested. This is not means that is not compatible with newer builds. Another thing: You should integrate Inbox Apps after integrating Updates. That's why the Inbox Apps Menu was moved to after the Update Integration Menu. If it's nothing like that, it seems like MS is taking preparatory steps for when Windows 10 is discontinued. I think a lot of features will be cut.