but in vmware same iso (no ei.cfg) MRP works, my vmare is MBR partition styles, my main PC is in UEFI with secureboot, so i knew it MRP oobe.cmd skipped or bypassed, any ways to fix?
MRP (if run) will detect the PID text file and will mention it in the log as its checks the key if it is valid or not and if it is then it will insert that key in the OS.
Im sure i remember working with someone with a similar issue months ago (may be a year or two, cant remember), not sure if it was in this thread or in a convo but i think PID.txt sorted the issue or a combination of ei.cfg set as the Edition and pid.txt set as the Edition's key. Those are the only two ways i know that should force setup to ignore a MSDM table's Edition value or a dummy one that confuses setup and install that Edition the user has chosen via those files. Unless m$ are changing the way setup is working aka like copilot and making setup run as they want and we the users have no choice. Not put it past them!
Secure boot is a bit over rated now as it was broken a while ago as the master 'key' was leaked, not sure if m$ fixed that loop hole now. But you can install the os in UEFI mode with that turned off and once the OS installed turn it back on. As far as i know secure boot is only used during boot via bios side so the OS not use it within itself.
I will be out for a few hours today as car has decided to put up the engine management symbol on the dashboard so need to go to a mechanic, (more expense i can do without), but need the car for hospital appointments. *sigh*
The MPRconfig is setting my Win to use black theme solid color instead of wallpaper and can't find witch setting is the cause ?
Will look into it later.. Does the MRP log show anything about OEM's.7z such as an error of some kind? Or was the file deleted so that MRP uses the default windows logos etc.
Will look into it when i get home later on as just about to leave to take , or limp the car to the garage to find how much it going to cost to find the fault. I know on w11 insider i had a weird issue like that but it cleared itself on the next insider build update.
Which oem theme should of been used so i can attempt to recreate the scenario. Or a mrp log so i can recreate the DMI entries to see if there is a parsing error for that brand. Thanks
Uploaded MRP 155 RC1 for beta testers Added option for w10/11: Add 'Registration Entries' (.reg) to the New's CT Menu this should hopefully be auto translated by the OS. One note is that it will fail if Notepad.exe is missing from the OS which may happen with a later Win11 OS update, but for Win10 it should work ok , there is a check for the file and if missing then the option will be auto disabled and be mentioned in the project's log. Updated the Creator too with this new option - found on [Win1x 2] tab - almost forgot to add that in Should all be well a early February release.
I was going to ask if any other tool/script was used that may of changed the theme in some way. The Slimdown script i believe strips most theme stuff out or sets things to a default type.
i was worried that i may of got the wrong translation string location for the registry (.reg) new item, but it looks all ok.
I was more like converting the original TranscodedWallpaper with solid color! on Win8.1. a glitch in script coupled with the MPR config. nothing todo with this wonderful project.