![]() 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. 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. Īs a example all *.evtx files on C:\Windows\System32\winevt\Logs are not captured. When you re-apply (in any mode) from a Wimboot mode captured WIM. 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. ![]() ![]() This topic was created with the idea to share your test made, and the results of them (good or bad), but please it is required: I will update latter this topic with a compilation of info, spread on several topics on the forum. Possible issues (if any) and how to fix them.ĮDIT: During the tests ran for this topic we have achieved a 1.57 GB used size on a 2.3 GB VHD, by means of cutting several non critical parts on the 10 OS. Install and run Office 2003, info on Post No.Win_Reduce_Trusted v4.0 (valid for 10, 8.1 and 7) links are on post No.Our fellow wimb making use of his skills on AutoIt3, was able to put together all the info we have gotten on this topic, about cuttings and related to some programs, and also about some free portables, and made a program capable to do all this automatically in less than a minute. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |