@ Inge001 I've removed that part of my post as I don't want to encourage people to create the fake keys. The KeyInfo app causes us problems when it comes to key sharing as we can't easily tell the difference between a real key and a fake key, but the author decided to publish it here and the information is very useful. As is the provided source. So from keeping it around maybe one day someone will figure out how the "secret" is generated, which would cause a media frenzy no doubt
Until MS starts banning bad keys we will never know for sure. Information can be used for good or for bad, always. If someone decides to poison the key reps with fake keys finding a legit one is like needle in a haystack. Crap.
I have dumped the SLIC from a Dell server - it is v2.3 - has this been leaked already? I know Fujitsu 2.3 is in the wild. Unfortunately the server is 2012 and not R2.
As the server is Windows 2012 and not 2012 R2, I think he won't be able to give us the key... Maybe I'm wrong.... I hope so !!
Would love to test this, but unfortunately I'm running Svr2012R2 on a HP Microserver which doesn't support uefi Now, if there was only a simple way to inject the MSDM table into the HP BIOS with my product key, or have this emulated via the DAZ loader
Loader support will come when theres a real OEM SLP key leaked. If I'll also have the loader inject an MSDM I'm still not sure on though as it's a lot of work with almost zero gain. The current version of the loader is limited to Intel chipsets or systems with an existing SLIC (any version) for Windows Server 2012. So for the loader to also inject an MSDM for WS 2012 R2 systems it'd mean that there's less of a chance that the loader would work on your system as it's having to allocate more space and adjust more tables. EDIT: The same goes for WindSLIC. By injecting an MSDM you're reducing it's compatibility with your hardware.
It would be nice if the end user could insert their own key via your loader, and not rely on a leaked key, but I guess there are reasons you don't want to do that. I thought the benefit of injecting an MSDM with the correct key was to avoid the error reported in the first post - or have I misunderstood something?
I don't want to support generated keys at all since uploaders will just put them in the keys.ini file and then hundreds of people will think that they're safe. Not everyone appears to have the error logged to their system, but for them that do what does it matter? It doesn't visually pop up, get in the way, effect system performance or annoy you at all. What matters most to me is hardware compatibility. So if injecting an MSDM would cause the following issues then the odds of me supporting it are slim. Systems with limited memory for a SLIC could run into issues if they also need an MSDM Systems that don't have an Intel chipset but do have an existing SLIC would no longer be supported as other tables would need to be adjusted
After injecting the MSDM, did you verify that it was present and correct in the ACPI tables? (use R/W Everything to check)
Then, that would explain why you still have the issue; the MSDM is evidently not actually getting injected.
Got the same warning message on VirtualBOX. The 1058 event log is triggered on every reboot. Still trying to inject MSDM into bios440.rom. Will report later.