I installed the wrong one, didn't know if I had to delete that one before I installed the correct slic one, and could not find it in any search :|
If the system has a valid slic, the loader would have worked on uefi, how are you now using the cert? it needs the slic and oem:slp, doesn't it?
Q. The loaders status says "Unsupported partition table", why is this? A. You're either using GPT on a UEFI motherboard or you've got a locked OEM partition. Both problems can be fixed by fully formatting your entire hard drive. but that wasn't an option so I did it manually
The loader does 2 things: When it finds a valid slic (UEFI/GPT or Legacy BIOS/MBR), it only applies the certificate and oem:slp key When it doesn't find a valid slic, it installs the boot loader and next it applies the certificate and oem:slp key The boot loader only installs when needed, but only on MBR partitioned systems.
Tokens.dat can hold more than one certificate. Analyzed some containing 2 different ones... Long time ago.... https://forums.mydigitallife.net/threads/how-do-i-extract-my-oem-cert.144/#post-2179
Yes correct Yen, I remember way back some scripts would add all certificates that were in $OEM$\$$\SYSTEM32\OEM folder.
The Loader checks manufacturer info from motherboard and adds appropriate certificate. Edit: from what I can make out he added certificate manually example slmgr.vbs ilc c:\your_certificate.xrm-ms
The loader status doesn't 'say' this if you are on GPT and the UEFI has a valid SLIC integrated. The loader then does not install, but applies the needed slmgr commands to establish the right certificate and corresponding OA key.