MRP 96 will have 3 new options as i mentioned a while ago. HyperV VM was causing some problems, which in turn found other inherent problems with the DMI/BIOS parsing which now seems to be sorted. This also allows faster fixes for any new brand DMI information that has similar names within. MRP code has dropped the RC5 and now just RC as this is the final stage before baseline so it will not be long before it is released. I do not want to repeat the same what happened with the QT!
Corruption caused when mounting virtual HDDs outside of their associated VM is often because of Fast Startup/Fast Shutdown feature. Modifying a HDD (virtual or physical doesn't matter) that is hibernated, even only partial like with Fast Shutdown, will corrupt it. Windows expects a Byte-identical image upon the next start.
After much testing and fine tuning yesterday, MRP 96 appears to be working as intended. There had to be lesser known/used brand 'Intelbras' theme rename to 'Idealmax' to make things work, either that or a total removal of Intelbras! MRP should detect Idealmax from the 'BIOS/SLIC ID' if it cannot detect it via the DMI entries and brand it with Intelbras logo's etc as normal. More details about this will be in the changelog. The Config Creator and OEM's.7z have been updated with the brand name change. QTv66 will be released shortly too which has the changes done. No other brands are affected.
Query Tool v66.0 has been uploaded, 2nd post's download link, password and hashes updated. Spoiler: QT v66.0 Summary Another shorter rewrite of the BIOS/DMI detection for specific brands which caused a few confused results. Intelbras - which is Idealmax, this theme will be shown as Idealmax, MRP however should theme it as Intelbras as before. Intel branded boards should now be correctly themed as Intel and not Intelbras as before. Adjustments to internal code for the work-around above and some little changes to the log output for display and saved versions.
Tests have all passed for MRP 66.0 RC If no problems with QT v66.0 with any strange theme results, (again), then the MRP will become baseline. Hopefully released by tomorrow evening.
Just changing MRP v96 to Baseline and sorting the Changelog which is quite extensive due to all the work done. Will be uploaded as soon as i can finish off the text.
Finally MRP v96.0 Baseline has been uploaded, 2nd post download link, password and hashes have been updated. Have left the v95.0 version up for the time being. Spoiler: v96 Changelog - quite long! Added some new options... General ALL OS's: + Disable BSOD auto restart. System will not just reboot when a crash happens, giving you time to see the error. Windows 10 Kernels Only: + Advanced Option - Disable EV Certificate/Sha256 Driver enforcement (experimental), hopefully allows you to install non Microsoft approved drivers. This may get reverted by a Cumulative Update so it is experimental for the time being. + Show Command Prompt instead of Powershell on the Win-X menu. + MRPConfigCreator has been updated with the new options. + Updated BIOS/DMI detection routine which will detect 'HyperV' better also allows swift fixes when any new DMI entry causes confusion within the MRP. This was the most complicated rewrite done to date, the original routine has hardly changed since the very first OEM Project way back in 2013/14 time due to the new brands added and some having very similar wording it was causing some problems, hopefully this new routine will prevent (or fix easier) any close matched names. See 'Important Notes' below. + Added CPU's Revision Number, this is slightly different to the CPU ID Code and it may come in useful at some point. + HyperV has a updated User Account picture which looks 'better' than the old one. + Reason Codes updated, also SKU's for LTSB now says LTSC. + Other code tweaks done as usual, some rewording here and there and slight changes to the log output. Important Notes : Due to the rewrite in the DMI area, there has had to be a change in one of the brands naming, it should not affect many people. Intelbras brand is now Idealmax - the branding will still be Intelbras but the brand folder and internal checking is now looking for Idealmax which is the SLIC's internal name. This change is to allow Intel's own motherboards to be branded correctly as the parsing stage was getting very confused because the name was so close, i tried everything possble to fix it but sadly it could not be done within the limitations of batch scripting, even powershell failed - i tried that method too! The MRP database has been updated with the change, also the Config Creator has Idealmax {Intelbras} in the list of custom themes. You will need the new OEM's.7z file to be fully compliant as using an older one may result in the Windows default theme being used as MRP won't be able to find the Idealmax theme folder. For those that have Intelbras computers the new routine should be able to find it and use the Idealmax's theme folder instead as it may ignore the DMI area and use the BIOS/SLIC ID. It may be wiser to use the drop down Custom Theme menu within the Config Creator to set the Idealmax (Intelbras) theme for those that wish to use that theme.
+ Disable BSOD auto restart. System will not just reboot when a crash happens, giving you time to see the error. won't that cause a lot of heat to the machine, i used to get scared when bsod appears in my old desktop pc becuz it starts to make a horrific sound like it's about to explode before it turns off, anyways i think when there is a bsod problem you will have to use a live os to check what's causing the problem from the log and then decide what to do, so i think it's not a big deal since in all cases you have to check + Show Command Prompt instead of Powershell on the Win-X menu. i love this tweak, cmd all the way; i just hate powershell i hope it doesn't exist in the first place lol + Updated BIOS/DMI detection routine which will detect 'HyperV' better also allows swift fixes when any new DMI entry causes confusion within the MRP. This was the most complicated rewrite done to date, the original routine has hardly changed since the very first OEM Project way back in 2013/14 time due to the new brands added and some having very similar wording it was causing some problems, hopefully this new routine will prevent (or fix easier) any close matched names. See 'Important Notes' below. + HyperV has a updated User Account picture which looks 'better' than the old one. sorry but i didn't catch up anything here, can you plz explain more what does HyperV has to do with bios and why it will have a problem with MRP, is this will make any issue for a windows copy with HyperV package removed completely using MSMG toolkit ? thank you
HyperV is Microsoft's version of a Virtual Machine. If you remove HyperV via MSMG or other tool then it won't affect MRP/QT -- it only affects the Project if you are using m$'s VM to install an OS using MRP in which case if it has been removed then you won't be able to create a HyperV V/Machine. The notes are to explain why the QT/MRP did not detect the HyperV properly before. If you not use HyperV then it not matter. VMware/VMBox etc should all still be detected as normal - unless the DMI has been edited or a SLIC/MSDM added that has a brand name it can use instead. -- Regarding the BSOD no restart option, the only time which may cause the CPU a lot of work is when the system is saving the memory dump to disk, this can be disabled but i left that part alone in case someone uses a 'Memory Dump' reader program.