#ISO IS NOT SMALLER AFTER USING MSMG TOOLKIT UPDATE#
I will update latter this topic with a compilation of info, spread on several topics on the forum. The OS will be installed without all old logs and it will create new logs as on a first brand new installation.ĮDIT: I think it is not a bad idea to start a new topic to share our test made chopping the OS by means of WimBootCompress.ini or any other tool.
When you re-apply (in any mode) from a Wimboot mode captured WIM. Īs a example all *.evtx files on C:\Windows\System32\winevt\Logs are not captured. In fact it is as a chopping by brute force.ĭuring Wimboot mode capture almost if not all log files created by the OS itself, are also excluded always, by means of wimlib-imagex and WimBootCompress.ini. Then any files/folders added by the user to section will not be included on the new WIM file (no matter the consequences), edit it wisely to avoid future troubles after apply the new WIM on a new installation. Wimboot mode capture or re-capture makes also a reduction which can be controled by the user by means of editing the WimBootCompress.ini.
That's why WinSxS_Reduce_Trusted is a sepate tool, you can decide when and where use it, the reduction process can be applied on any installation you want, of course it is good to apply it before the Wimboot mode re-capture to reduce the WIM file size, especially if you latter will make a Wimboot mode installation, but on Normal or Compact installed systems can be used after the installation for testing pourposes or if the user wants to keep his WIM not reduced (just in case).
0 kommentar(er)
