How can I enable the switch to apply it compressed? So are you saying that compressed (fast, max, recovery, etc) would actually increase performance of the final install on an SSD?
I use wimlib not dism for that, something like X:\wimlib-1.13.3-windows-x86_64-bin\wimlib-imagex.exe apply Y:\ltsc-19045.wim Z:\ --compact=lzx Exactly. A 486 was already powerful enough to manage the on the fly compression w/o sweating (everything became slow at the time because the FS fragmentation on mechanical disks, not because the CPU overhead), And now the CPUs are thousand of times faster. While mass storage is still relatively slow. Even the fastest Optane drive is orders of magnitude slower than RAM (which in turn is slower than CPU cache). So yes compression means very little more work for the CPU while having one half or even one third of data to send/receive to/from the "slow" mass storage.
hmm... nvm I think who want to enable 22622 new feature then can -> make a 22621 ISO via UUP dump -> use MSMG toolkithelper debloat、edit wim file -> when done then increase KB5015669 patch, that finally should be 22622 full functions enabled install.wim It's a good idea :目
Just started experimenting. Have a few questions regarding customizating Windows 11 ISO. Is it possible to remove start menu app advertisements? I applied custom start menu layout however, it didn't seem to work. Is it possible to get rid of Edge browser first run prompts?
Lol, given it's been near on 4 years since the release of 1809 I'd say it's darned impossible, not difficult. I think if no-one's figured out by now they are never going to find a way to stop restoration of all the garbage. Given everything released since 1809 is nothing more than bugs, more telemetry, bloat and malware, there really is no compelling reason to go past 1809.
The same thing occurs on Android. WebView ends up becoming a framework for various apps and becomes a prerequisite like: VC ++ Runtime and .NET Framework. It is very interesting to put as separate components.
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.