Pl i am not a mediator to provide any expert or any team to a mdl user asking for help online. its also against the rules of MDL community that if somebody found providing a help for self benefits will be hardly taken under action by staff . you can visit my profile n go to the thread i have created on MDL there download latest updated AIO debloater script n edit it to see the function i used in my script for onedrive removal.
please go through my profile information n click on thread by me on MDL . there u will find a single thread n click on it . you will be directed to my win10 tweaking thread.
sorry i got it . my profile is restricted . please wait let me open it . Edit : Opened It now . pl cross check.
Pl cross check now as restriction is removed . or direct link : Win10 Tweaking Scripts i know this comment will be reported again by MSMG fans to staff. But my POV is to help anybody with good intention & sharing is caring .
I believe he meant that he would like to wait for more help from the team to better understand how to do it. But he's already getting your help. Alright then!
Wimlib not required, you can literally rename the esd to wim and windows setup and dism will still recognise it
Did you try that? DISM can't handle an install.esd renamed to install.wim Code: Error: 11 An attempt was made to load a program with an incorrect format.
Yes. In my homemade ISO homebrew experiments The compression algorithm used (LZX, LZMS etc.) is read from the file header. Esd is used to ease identification of solid archives
Does renaming a ext from .wim to .esd works then what for dism commands are used to convert wim to esd & why abbodi has made a esd to wim or vise versa wim to esd convertor why compression methods are different in both scenarios ie for esd is recovery & for wim is normal or max
Yes it should work but it won't change the compression algorithm so non-solid archive will remain large and non-solid (contents won't be changed) Wim to esd converter converts it into a solid archive and reduces file size. Esd (solid archive) renamed to wim will remain non-editable, needs to be properly decompressed to make non-solid and editable
Or by design to prohibit novices who used the MCT to create an ISO to corrupt it? ps, imagex (not wimlib-imagex) can handle install.esd to some level, mounting but not saving, deleting indexes.
why will somebody just change the ext from wim to esd if it wont do any change. main criteria of converting wim to esd is to solid compress it so as to save space on iso & as well as faster installation.