Why doesn't Windows Activation Troubleshooter check for BIOS Embedded MAK Keys from Dell?
It's really strange to me that I had to download third party software to pick whatever specific generic MAK key Dell was using for this model, and that Windows' activation Troubleshooter doesn't do that for me. A lot of wasted time troubleshooting that, personally, when it can be a click of a button.
How has Microsoft not implemented this in a years and years of Windows 10 being released?
Is there some security reason for this, or real reason at all? Maybe I'm just ignorant to why the troubleshooter doesn't actually troubleshoot. Kind of a half rant.
Posted Sep 23, 2019, 10:16 PM UTC
First of all, it is an OEM key, not a MAK. They have different EULAs.
Sure, it's still functionally a MAK. It's sorta like someone saying "I'll use putty" instead of "I'll use SSH". Maybe I'm wrong, but I figured that Dell has a set few keys that can be authenticated multiple times across mass devices, so they don't have to do individual keys for every single device. The only difference from a MAK is just what the end user can do with it, nothing regarding Dell.