How to permanently add SLIC in (newer) ASUS UEFI

How did you mod the bios?

If you wrote something on the SPI ROM, the only way to remove it is to erase the bits that you wrote because that's not updated when you flash a newer bios.

 

https://forums.mydigitallife.net/threads/how-to-permanently-add-slic-in-newer-asus-efi.31404/ :

 

Stuck here - might be missing something?
HWID matches on v1809 x64, SLIC reports correct 2.1 matched cert installed by slmgr -ilc . Not activating, though. Ideas? Just using wrong product keys maybe?

 

Windows 10 cannot be activated by SLIC. HWID is something completely different, you use the default RETAIL key for your Edition and activate online.

 

Thanks. So, let me check if I understand that
1. no BIOS SLIC works in Win10 so even OEM don't use that anymore? Or do they use a higher version like 4.0 that can't be replicated?
2. HWID - what is this id, then? What does online activation do? Are retail keys unique for OEM?
3. Only chance is then VL versions right?

Any explanatory material is very welcome here, I failed to locate it, it seems

 

1. OEMs use OA3.0 (OEMM) for consumer OS since Windows 8, where every machine has an individual product key embedded into its firmware (MSDM table in BIOS or UEFI). Loader worked because the OEM:SLP keys were generic and thus could be shared. Well, not anymore. For that reason. there will never be a Loader for any OS beyond Windows 7... with one exception. The Server OS still use OEM:SLP, Server 2019 would be using SLIC 2.5, most probably. Loader has limited support for Servers.

2. HWID is simply a hash of your machine's hardware. A fingerprint, if you want to call it like that. The HWID is stored on MS' servers and allows activating the machine without any individual key, as long as the hardware doesn't change significantly. Contrary to OEM:SLP, it is an online activation mechanism.
OEMs do not use Retail keys. The default Retail key just tells the OS to search for a HWID and activate using that. Nearly all OEM systems are MSDM, now.

3. KMS Client keys (gVLKs) are about the only keys now that are both generic and activate fully offline against a local KMS server. It's either HWID or KMS, now.


Reading:

Explanation on how to create a HWID that activates the machine without needing a key: https://forums.mydigitallife.net/th...g-through-the-complete-upgrade-process.64770/
As the free upgrade from 7/8 still works, you can establish a HWID by follwing the topic instructions.

OA2.2 and OA3.0 explanation: https://forums.mydigitallife.net/threads/windows-8-preinstalled-licenses-aka-oa2-2-and-oa3-0.34580/

KMS tools: https://forums.mydigitallife.net/forums/kms-tools.51/

 

You need to login to view this posts content.

 

(Dummy) MSOA: See @Tito answer below.

 

thank you very much for this explanation.
can you tell me now how can we know if bios has MSOA/DummyMSOA module ?

 

You need to login to view this posts content.

 

Maybe you shouldn't openly post your OEM꞉DM key here?

I removed my wrong information.

 

okay and after that ?
is there any information that shows that the specific bios contains MSOA/DummyMSOA after you open it with MMTool ?