MRP 105 may have a new option added - my tests have shown it works perfectly and i think it will be an option most used. It also allows a user edited XML file to work too... More details once more tests have been done and if the option will be a permanent 'feature'. There was a clue in the first paragraph.
It is what is obtained from the motherboard so at some time that m/board may of had more slots on another revision or in the prototype stages and then they decided to alter it for cost reasons and the bios still 'thinks' it has the other slot(s) there. I can't guarantee that is what happened but it does makes some sort of sense.
There are "reference designs" for motherboards. Some manufacturers will sell cheaper variants of premium boards by leaving out certain components. To keep effort for providing the firmware low, it is often the same for all. Thus the QT might show things the reference model has, but are removed in the specific design.
odd, there is nothing in the .ini fle that should of caused the project to abort the main script as the debug log shows it was within the setting up of the variables stage....
i am tracing back from what would be the next line in the main log back to when the .ini is parsed. Hopefully i can find what is causing the abort.
Have checked every line of code between the last log entry in the project/log and where it would then show the pre-options such as This Computer/PC on desktop etc, nothing i can see is wrong. Checked for missing quotes around variables, missing ( ) in any FOR /F loops etc. Even parsed checked the .ini for any odd character that has sneaked in such as & ^ ( ) < > etc. The line with '[URPTE] Error: Theme may not have some parts applied correctly.' - is one of the first checks done in the Addon Manager, (after the first oobe stage reboot - before the username is entered etc). I even did a test install of win7 same edition using the ini file you used while i was checking through the code, and all installation went ok. I am at a loss why it is failing. I doubt it is Unicode in use that is causing the problem, as i have tried all possible languages in testing and none aborted the project. Plus if that was the case then the QT would abort too as it uses the same routines... Have added extra bits into the debug log now so hopefully if it not aborting before that stage where the debug log is initialized, (in which i can then narrow it down further), that it is all i can do for the time being. MRP 105 will have that extra debug info at the top now. I cannot revert back to non Unicode as it will break any drive name, model name and all the Context menus. It seems to be related to Windows 7 (i hope) as Windows 10 seems to be ok. The puzzling thing is the block of code between the log entry for 'Options Pre-Check Completed.' and what should be the next line in the log - about 'This Computer/This PC' enabled/disabled is standard code which is language/OS independent! For now i am out of idea's and as it a isolated incident and with the 1000+ downloads so far and no other reports of the MRP aborting, not much i can do i am afraid. Plus the code in that area of the project has not been altered since 102 when the Unicode stuff was added.
Before 102 the Unicode part was not added in. Technically it should not affect anything it just allows any echo's to the screen or log file in this case to show characters outside the usual Latin set. I read up that there is a possibility of some errors but the variable names used do not contain any special characters that could be changed - i was very careful in the naming of them that is why some look a bit cryptic in the .ini file.
The same thing happened to me several times, and I had to stop the installation of the windows. This happens with "Administrative Tools" and therefore I do not use this option. The "Add Control Panel as a Desktop Context Menu" option is lost, deleted, no option after a while.
On MRP versions prior to 103, on OS's below 8.0 the WiFi checking routine that was added to assist in knowing if the system was online or not, seemed to fail on certain hardware and may cause the project to either abort or 'hang'. In 103 it was removed as no longer required. Clicking the X on the blue 'command' window would of gracefully exited MRP and allowed the Windows setup to complete - the only thing not completed in MRP would be the project.log as it would of stopped at the boot drive IDE/Sata part and Wintel and Usertweaks scripts (if used) would not of ran. I have a suspicion why MRP103/4 failed was in the new option variable check and creation routine. If my thought is correct i will revert back to the old creation way adds about 4 seconds to the time to process so it not too bad and you would not notice it.
give me a few mins to find the archive. 100/101 did not have unicode added. I will find out v101 as i know that was before it was added.