and what u just said is the cause for my wimboot capturing and applying not working and my dism capturing and applying working - i don't mean to contest u, i simply mean that there must be a reason for the earlier not working and the latter working here, don't u think?
my wimbootcompress.ini is almost bare and it works; dism does take it into account and your wimlib does not, apparently. dism here yields a slightly bigger wim image (4.1 instead of 3.99) and allows for a better compression of the related vhd and boots ok. at least here the wimboot tool yields an incomplete vhd (for example, nvidia control panel missing from taskbar) which boots erratically.
of course, if there are any technical errors in the bare character of my wimbootcompress.ini, I am in no position to say. I can only state what happens here.
But have you tried the former with the old version attempting to create a bigger vhd and a smaller wim re-applying the latter with the newer approach?
 You see , I am perfectly capable of writing incomprehensible and meaningless blurbs, but usually conversations - particularly on technical matters - require:
both completely missing in your late posts.
I understand you did a lot of experiments, but unless you detail, exactly, what you did and report, again, in detail and exactly the results, noone will be able to understand you, let alone try and assist you in finding the mistakes (if any) you did or suggest better or alternative methods/tools.