There is something wrong with "M128.0BL_Compiled_12th_Aug_2020". At 71%, it aborts the installation and returns to the beginning. With "M127.0BL_Compiled_10th_July_2020" the installation goes normally.
im at work on my break so cannot test at present. Weird it is crashing setup as MRP is not run at all during that time of setup, MRP only starts to run during the oobe stages ie when you get to set up the username etc.
All works fine for all test installs i did for my releases (78 indexes 19041.450 + 78 x 19042.450 dutch + 8 19041.450 and 19042.450 dutch +10 x 19042.450 and 42 x 19042.450 en-US), the stage you got the error at 67% is at the applying of the wim to the systemdrive.
MRP v128.5 beta 4 is under testing with 3 new W10 (w10-tab1) options: Remove Disk 'Quota' tab from a Drive's 'Properties' menu - experimental as unsure if it can be removed during first oobe stage... Remove 'Previous Versions' tab from a file's 'Properties' menu - this may be affected if 'System Restore' is operational. Remove 'Retail Demo' files. Fairly obvious what this one does.
The new QT is code complete, it just that i not had time to get the change-log sorted and it all uploaded as been very busy with work, i will try my best to get it all done very soon.
Query Tool v108.0 has finally been uploaded, 2nd post download link, password and hashes updated. Spoiler: QT 108 Summary + Adjusted the memory unit display suffix to show KiB, MiB, GiB etc. + Updated the OEM Consumer/Server versions line with commas to look clearer. + Updated the AntiVirus name detection, it still may display a wrong name but that is a failure of the WMIC's api. + Updated the Graphics VRam value routine to hopefully be more 'accurate' however the api used has some limitations and so it does not split the physical and shared data amounts, the value could be shown with, or without, either amounts. + Various internal code optimizations. There may be other little bits done but the main parts are listed within the change log/summary. I re-compiled with today's date to keep things in a relative order for references.
no graphics card information... I know that section works, maybe something triggered the routine's error checking and ignored that part? If it continues to skip that i will take another look in that routine, as no AV is present such as Defender that cannot be the cause of the routine being missed...