Okay, I found mymistake. I only had $$ Folder in my sources folder. I should have $oem$ folder, the $$ in the $oem$ folder. You answered my answer about the UserTweeks.cmd file. That is what I was missing. I'll let you know how I made out for the third time. Thank You..
The $OEM$ within the MRP archive is in the correct format. UserTweaks.cmd (and the folder named UserTweaks), Wintel.cmd are what MRP will look for in the Scripts folder only. If they are present it will use them, if not present it just ignores them. Wintel.cmd contains basic Telemetry removal and blocking. It does have advanced services removal etc but are bypassed by default. You need to know what you are doing as once a service is deleted its gone and only a full reinstall is the way to revert that. Unless you are a master at recreating services! So those are not in use to prevent messing up a OS. UserTweaks.cmd contain barebones which do not do anything. It is for advanced users that know how to write batch scripting etc to add their own personal tweaks etc. The correct structure of the $OEM$ folder is: $OEM$ -> $$ -->Setup --->Scripts - this folder contains the MRP files. or $OEM$\$$\Setup\Scripts $$ = Windows folder When windows setup copies the files over it will do so to: C:\Windows\Setup\Scripts C: being the system drive usually. It is late here and i am about to get some sleep. So i wont be able to reply until sometime tomorrow if needed.
QT 64 - RC4 This *should* detect HyperV... (famous last words ) Link Removed. Passed Tests and is out of RC. To be uploaded later... Those with the Microsoft Surface may have the Windows Default theme shown if the DMI does not have the word Surface within it. Can't do much about that. - Use the CustomTheme Luke! sorry a bit of Star Wars there. Been up since just after 5am after about 3 or 4 hrs sleep - well broken sleep due to the heat - so used my time to battle with this QT code. If this one not sort it then i am out of ideas. But it has allowed me to upgrade the DMI checking code base to be a bit more efficient so not all time was wasted. If it does work then MRP will have the same DMI checking upgrade.
Fingers crossed. But signs look promising at least. Takes me a few attempts, rare i totally give up. May leave something a while then come back to the problem head on and batter it into submission - usually that works.
It's nice to see that the conflict part is working on HP/Compaq as that was the hardest one to master, it may not be 100% perfect but it close. Toshiba is another one i added a while back that seems to be working nicely too. I am adding the new DMI checking routine into MRP which is tricky as i have to be very careful it not upset the code block. One thing i noticed is that if the computer is a EMachines the conflict part kicks in and says Emachines resolved as Emachines. But that immaterial.
Added the new DMI check routines to MRP96 code.... Now at RC4 test stage... (strange that the QT64 is at that 4 stage too ) Technically it should not affect non HyperV VM's but i have to fully check to make sure i not upset the main routine... If this passes and i manage to install HyperV and retest then it passes my scrutiny -- i will be happy and MRP 96 will soon be ready.
The QT 64 RC4 looks like that VM/DMI area been sorted. But will wait until later to see if any other glitches have sneaked in. Link removed. QT 64 passed tests. If all is golden then will change it from RC4 to QTv64.0
Why is setting up HyperV such a pain in the rear? Gez. error cannot be started as Hypervisor is not running! Err what is HyperV then? stupid bloody thing, no wonder i stopped using it lol. VT is enabled in bios. CPU is a C2Duo quite capable. Enough RAM and HDD space. Edit: Almost an hour later... 2nd Test PC (Haswell Celeron Gxxxx , 4gb ram, 250gb drive) HyperV stuff installed. Two reboots later it looks all ok... (Default settings - as too many to mess about with) Created Test VM... Installing W10 Home x86 via Gen1 HyperVisor - think that means MBR not UEFI. At least it 'started up' and attempting to install. Seems faster than VMWare At Getting Ready screen, soon be oobe stage.....
HyperV used. HyperV theme installed Cant get project.log as the VM being a pain now says cant create checkpoint or something when i tried to install the guest stuff to allow copying. Plus trying to mount the avhd file i think corrupted it grr. But you can see the theme in place and bit of the log. So it was a success. I must say that the HyperV theme might need some new logos