ok RC2 .... Only way to theme a HyperV as HyperV will be via the CustomTheme option. QT cannot determine HyperV - link removed.
well sadly i cant fix it No matter what i try it refuses to accept that it not Emachines but HyperV. Grr i hate m$ at times i really do! The odd thing is : Query Tool has detected a possible HyperV Virtual Machine. Yet it still refuses to budge from bloody EMachines!
The routine that detects the VM's can't really be used to theme because if you change the DMI data then it would ignore those entries and just theme as HyperV or VMWare, VBox etc which is not what is required. Say for instance you have a VM with edited DMI entries for Asus or another brand, if i force the VM name then VM's would be themed as the VM name and not the DMI entry 'Asus' in this example. Plus as the area for theme detection is very sensitive it is so easy to crash the QT (or MRP) so i try to avoid messing with it. Its a fine balancing act. Sadly for now this HyperV stuff is on hold, or i won't have time to finish MRP 96 before the end of the week!
I may have a way to force it.... Just working on the code..... If this not work then i will have to leave it for now....
FYI: Nice tip to speed up powershell calls by using -noprofile switch. Source: https://forums.mydigitallife.net/threads/discussion-download-uup-dump.75052/page-100#post-1451854
RC3... See if this one works! Not holding my breath as this was a 'easy' code test... Just VOID the dmi "Virtual Machine" DMI entry so it cant see EMachines ... Closer! Link removed. Another Test will return tomorrow.
I try to avoid powershell because it not as easy to pass vars back to a calling batch script, well i not been able to do... Unless it by a text file to then be parsed but that adds another layer of extra code.
There is only one line of powershell in MRP and if that fails it has two other methods to fall back on. Your the master of those FOR loops! Im still struggling to get the swines to do as i want lol.
LOL well it on the right track i guess! Surface is M$ although not quite the Surface model. Well as it getting late here i will refrain from another QT test today. I will add another void for Microsoft Corporation, but this may upset the real Surface DMI entry. But at least it on the path.
all that is needed in the scripts folder is: Decompile.exe oems.7z oobe.cmd MRPConfig.ini The rest is not needed as the other scripts will *not* be ran as MRP does not use them. As all options used are self contained within the decompile and called upon via the options that have been used internally. They are for reverting or using AFTER MRP/Setup has completed. As you not got the script called UserTweaks.cmd the folder UserTweaks will not be used either. IFSSD.exe , SetACL and the QT files are not used at all in this context. All reg entries/files needed for MRP to work are contained within the decompile.exe they are extracted as required on a per system basis.
I see you have the ei.cfg in the Sources folder this is needed as you installed Pro and the MSDM is for Home/Core you will be presented with the edition list to choose Pro (if that what you wish to install). The MSDM for Core/Home will be ignored to allow you install Pro.