r/sysadmin•
aberugg

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

517
theNAGY1•

First of all, it is an OEM key, not a MAK. They have different EULAs.

11
aberuggOPJack of All Trades•

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.

0
networkwiresonfire•

if we are talking about the OEM key, the troubleshooter should detect that just fine (I do that for Lenovos all the time)

here's a little powershell that should do what you need (if it doesn't, maybe it helps you debugging)

#activate windows using internal (OEM) license key
$Productkey = (Get-WmiObject -Class SoftwareLicensingService).OA3xOriginalProductkey
iex "cscript /b C:\Windows\System32\slmgr.vbs -ipk $Productkey"
iex "cscript /b C:\Windows\System32\slmgr.vbs -ato"

no third-party tools needed

2
aberuggOPJack of All Trades•

if we are talking about the OEM key, the troubleshooter should detect that just fine (I do that for Lenovos all the time)

It doesn't for Dells then apparently. Yeah, the OEM key which I understand to basically be their equivalent of a MAK (probably functionally different in some specific ways as far as their licensing and they might have self-hosted activation servers maybe, I haven't looked into it).

Thanks for the powershell script, that's a great idea!

1
networkwiresonfire•

thinking back when we ordered downgraded (Win10 to win7) PCs from Dell, I do remember that they were using their own keys for doing so (Volume? MAK?). I thought for Win10 they are now proper OEM at least

1
aberuggOPJack of All Trades•

This would have been a system where it had the option of windows 10 pro for workstations when that version was relatively new, as an optional, so this makes a lot of sense in the reverse... The key was embedded btw, it activated fine, the problem is... why doesn't Windows 10 Activation Troubleshooter do that for me? lol

1
[deleted]•

Also there is the automated phone system where you can call and it’ll text you a link and instructions on activating. Works well if you know a computer is activated but the troubleshooter says: this computer is currently using a digital license. You must use a digital license.... etc. just a little tedious

1
aberuggOPJack of All Trades•

That's not exactly what I'm talking about. I'm well aware of that system. I'm talking about a system that for whatever reason was on Windows 10 Pro, but it's OEM Embedded key from Dell was for Windows 10 Pro for Workstations, it wasn't activating, and the activation troubleshooter didn't detect the OEM Embedded Key from Dell. It just gives you an error as if it's trying to contact a different server, come to think of it, than it should.

1
starmizzleS-1-5-420-512•

Yes, I'm a caveman. From a command prompt:

wmic path SoftwareLicensingService get OA3xOriginalProductKey
1
starmizzleS-1-5-420-512•

Installation from proper media will pick up that embedded OEM key btw.

1
aberuggOPJack of All Trades•

Reinstalling on these specific users' devices can result in enough downtime for our tooling machines to cost us thousands of dollars, generally we have a spare they can use, but they don't like it, and it doesn't come with all their customizations. I fixed it, but was more wondering why the troubleshooter doesn't do this, seems like it just should work.

1
[deleted]•

[removed]

0
aberuggOPJack of All Trades•

It's kind of a half rant and a half "why would the Windows Activation Troubleshooter, technically speaking, not do this?". As other people said, it did for their Lenovo setups, but not for our Dell ones, so not sure where the issue is.

1
[deleted]•

[removed]

-2
aberuggOPJack of All Trades•

Yup, looked through it. Didn't see anything that would cause this to happen from what I can tell. We don't go all out on security settings as much as some people have to around here, so I kinda ruled out that possibility. We do super basic BIOS settings, basically just Dell Defaults.

1
[deleted]•

[removed]

-2