There is no need to do this, because in any other mode of compression it will take practically the same time to save changes to the .wim files. After finishing saving you will have to go to the Tools menu and use WIMconvert to ESD. Optimization cleans some things and removes the "[DELETED]" folder which is maintained after removal operations during the image being serviced. The NTite sins in this detail. My preference: When I need to do something with NTLite (for services and settings only) first apply your NTLite settings and do all the rest of the procedures here at Toolkit.
I tend to get errors upon removing features when I use Toolkit second after NTLite. Probably because they're already removed. What should I do about that? Whenever Toolkit errors, it completely stops the component removal process.
1. notice: thie registry only "hide" the section, but the block still there Windows Registry Editor Version 5.00 HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\Explorer\ "HideRecommendedSection"=dword:00000001 2. for skipping ege first time running page Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge] "HideFirstRunExperience"=dword:00000001 "AutoImportAtFirstRun"=dword:00000004 "PromotionalTabsEnabled"=dword:00000000
So this being said, is there a way I can disable the recompress optimization step in MSMG Toolkit when Applying/Saving image?
I have no idea, in my workflow I rarely mount and dismount the wim. If I need to do things that MSMG can't do I just keep the WIM mounted where MSMG mounts it and do my things there. That said MSMG is a batch script, shouldn't be rocket science to modify a line or two to fit your needs. BTW lke my friend Jon von Tetzchner (the coinventor of Opera browser and CEO of Vivaldi technologies) is used to say about GUIs, when in doubt make it an option. Given practically any modern browser is more or less a copy of Opera, I think he is absolutely right.
Recommended section I don't mind. I am wondering about those Twitter, Spotify, Adobe Express, Disney+, Prime Video, TikTok, Instagram, Messenger apps. They don't seem to be in ProvisionedApps.
Yes, In Toolkit and Custom Toolkit, we do not use the Wimlib-Imagex command arguments to re-compress the install.wim file. We simply let it be the maximum of the compression algorithm already used in the image. Thus, speed is not affected. If you want to use re-compression without converting to ESD. You will have as a result: An image of the same size as the original, but made with the time required to convert to ESD. So it is not worth using re-compression to keep the image as Wim. As I said, there is no need to do that. The optimization process is a re-packaging, not a re-compression.
I said my recommendation is: Use NTite only for "Services" and "Settings". When I mentioned "Services", I was not clear. I meant: Enable or Disable Windows Services.
You are mixing what I said about the live filesystem with what I said about the wim. There is not RE-compression using wimlib to build a wim. Wimlib Is just a (better) replacement to dism it does exactly what dism does with some advantages (like a bit better speed, and the multi OS support) Well. Just NO. The files on mounted image aren't compressed, the files inside the wim are compressed. To move an uncompressed file in a compressed place you have to compress it. (it's not even an IT matter, is just simple logic), and compression takes time and CPU cycles, especially an asymmertical one like LZX or an higly asymmetrical one like LZMS (esd compression in dism parlance). In your dreams, maybe
For you to be happy, I correct my speech. Speed is not noticeably affected. The difference is very tiny. I was talking to him about Toolkit and Custom Toolkit. Why would I be confusing myself about what you said? If I was strictly talking about what he asked. Man, being native to another language, a little complicates the way of expressing me ... but I tried to be clear about that in Toolkit and Custom Toolkit we do not use this command: Code: "%WimlibImagex%" export "%InstallWim%" %%i "%_TMP%\install.wim" --compress=LZX --recompress we are using for ex: Code: "%WimlibImagex%" optimize "%InstallWim%" that replaces the use of: Code: "%WimlibImagex%" export "%InstallWim%" all "%_TMP%\install.wim" --compress=LZX :: Move Replace Source "install.wim" for New "install.wim" Image File if exist "%_TMP%\install.wim" move /y "%_TMP%\install.wim" "%InstallWim%" >nul And, this one: Code: "%WimlibImagex%" export "%InstallWim%" %%i "%_TMP%\install.wim" --compress=LZX --recompress like that one: Code: "%WimlibImagex%" export "%InstallWim%" all "%InstallEsd%" --compress=LZMS:100 --solid They take too much long time to have their task completed.
for services i use kedarwolf template advanced list on offline image & everything going great. pl do have a look at his post in OO For settings i use reg capture on current installed os & have a backup of it change key according to offline image loading of registry then apply that reg whenever new image is created . save lot of time.
That's the point. Just provide an option in the menu tools to export the wim as uncompressed, then mount that and work with that, all the operation would be an order of magnitude faster, then provide an option to export as compressed at the end of all operations . To be clear that's not my pet feature, is just a request of another user that IMO makes sense in some scenarios, and probably makes sense even for common uses. Likely the time spared removing and adding features and doing the normal things that MSMG does will overweight the time to export the image at the beginning and at the end of all the operations.
I've done it at Custom Toolkit. The results were very little speed difference (a few seconds). That's why I removed the option. Since it would not make noticeable difference. I did not understand right. But describing the dynamics of Toolkit and Custom Toolkit: If it is an ESD image, there is the option to export to Wim. So Toolkit Mount only the selected WIM image indexes and after completion of the user customizations are that unmount, saving changes and, following the optimization that cleans the unwanted remnants and maintains the source image compression factor. We have been far from what we have today with Toolkit. Those who had no experience with Toolkit 10.2 could take 4 hours up to finish a personalized ISO. Today, if it takes 40 min is too much. Maybe a little more if you want to convert to ESD.
Got it. But my experience tells me to never take a single test (or few tests) for granted. Maybe the mileage may vary depending on the CPU power and the speed of the storage. Whatever, like I said that's not my personal feature request and I'm too busy in other things to do benchmarks myself But on the other hand MS undermined a lot the importance of what MSMG could do, since 1809