WIM vs ESD and boot.wim compression
Posted: Mon Sep 04, 2023 8:42 pm
Hello all,
Thanks for the work on this project.
I'm creating a debloat and hardening deployment method for Windows 11 and have been using wimlib as a final touch.
It's my understanding that .ESD files are just solid .WIMs? Are there any other differences?
And why doesn't wimlib rename it to ESD so it's clearly identifiable as a solid archive?
Further, I noticed when I tried the same solid high compression switches with boot.wim it became a non-bootable setup with critical errors. I didn't do any sort of testing to see if this was the issue, but it was the only other change I made to boot.wim
Does boot.wim need to be non-solid and editable for setup? What are the highest compression settings for this WIM?
Thanks in advance
Thanks for the work on this project.
I'm creating a debloat and hardening deployment method for Windows 11 and have been using wimlib as a final touch.
It's my understanding that .ESD files are just solid .WIMs? Are there any other differences?
And why doesn't wimlib rename it to ESD so it's clearly identifiable as a solid archive?
Further, I noticed when I tried the same solid high compression switches with boot.wim it became a non-bootable setup with critical errors. I didn't do any sort of testing to see if this was the issue, but it was the only other change I made to boot.wim
Does boot.wim need to be non-solid and editable for setup? What are the highest compression settings for this WIM?
Thanks in advance