Adding the Wimboot flag to an already existing image is as easy as you can see on previous post images, just write WIMBOOT on the last empty space under NAME and 1 on the next espace at its right under VALUE, select it to be applyed and just click on SWITCH, of course WimBootCompress.ini should be present on \Windows\System32 folder (8.1U1 and 10 already have it with Windows default presets), and also wof.sys needs to be on \Windows\System32\drivers folder (8.1U1 and 10 already have it)
In case of Win 7 and Win 8 versions before 8.1 Udpate 1, they lack this two files, but if you have the good luck to have extracted and run at least once WinNTSetup on the running OS before capture the image it downloads and installs wofadk.sys (the ADK version of wof.sys) on \Windows\System32\drivers folder (you can open the WIM file with 7-zip and verify if the file exist) and creates the required service to load it, wimlib has internally an equivalent to WimBootCompress.ini with the recomended presets, so in this case you may apply the Wimboot flag to your image.
In case you want to use a custom WimBootCompress.ini you can add or replace it easily with wimlib-clc on Update Tab, see attached picture, the procedure to update the image file is very fast. Then your updated image file can be applyed with wimlib-clc.
NOTE: Only use wimlib to apply images with custom WimBootCompress.ini, DO NOT use imagex or Dism or any tool based on Dism as WinNTSetup or DismMoutService to apply an image file when it has a modiffied WimBootCompress.ini because it will not extract all files correctly, for more info see following quote from: https://msfn.org/boa...comment=1171109
@wimb & @alacran
You know that the problem only occurs because you guys replacing the internal WimBootCompress.ini?
Stop do that and wimgapi will work correctly.
Hope this info may be usefull for some of you.