Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

Can you explain what happened during my Windows 10 Enterprise MAK key activation experience?

Delicieuxz
 Share

I have a Windows 10 Enterprise MAK key good for 20 installs that I purchased off of eBay a couple of years ago. I've contacted Microsoft support, and they've verified the authenticity of my Windows 10 Enterprise MAK key for me.

 

The seller I bought the key from provided an ISO download for Windows 10 1607, which I installed from and used the bought key with.

 

When Windows 10 1703 came out, I downloaded an Enterprise 1703 MSDN image from somewhere and tried to activate it with my key, but the installation didn't accept my key. After that, I contacted the seller I got my key from and they gave me link to their Enterprise 1703 image, which I made another installation from, and my MAK key worked with it.

 

So, my Win 10 Enterprise MAK key worked with the ISOs I got from the seller, but didn't work with an MSDN image I downloaded from somewhere else.

 

 

Now, what I've been told by multiple people is that all MSDN and VLSC KMS and MAK keys work with the same images, and that any Enterprise or LTSB / LTSC KMS or MAK key from any MSDN or VLSC account will work with any Enterprise or LTSB / LTSC KMS or MAK key from any MSDN or VLSC account. But, my personal experience suggested something different.

 

 

What likely was the cause of this?

Link to comment
Share on other sites

Link to post
Share on other sites

Possibly the key was an EnterpriseN or EnterpriseKN key, which only work with Enterprise N or KN ISOs.

 

Download the VAMT 3.1 tool and verify the key. 

If I helped, hit the thumbs up icon below my post and pick it as 'Best Answer'

Resident living meme - I swear a lot; if you don't like it fuck off :^)

  My specs and shit down below.

Spoiler

Apollo: i5 4670K @ 4.6Ghz, Corsair H100i, MSI Z87I, EVGA GTX 1070 SC ACX3, Corsair 250D, 840 EVO 120GB, 1TB Seagate Barracuda, SeaSonic 520W PSU. Planned upgrades: 16GB RAM, 480/512GB SSD, new HDD

Sputnik: HP EliteBook 2570p, i5-3360M, 16GB DDR3, 256GB 840 EVO - Running Win10/Sierra dual-boot.  Future upgrades: i7-quad

Comet (home server): Atom D2500, 4GB 1066Mhz RAM, 2 x 320GB HDDs, 350W PSU, HAF-Stacker ITX, dual GbE. Cost me $80. back from the dead (mobo failure) bois

Spoiler

Main peripherals

- Corsair Strafe RGB MX Reds

- SteelSeries Siberia 650

- SteelSeries QcK+ CS:GO Camo 

- SteelSeries QcK+ Na'Vi Splash (Secondary pad, used for second rig)

- SteelSeries Rival 700

- SteelSeries Rival 300 (Secondary mouse, used for second rig)

 

 

 

Link to comment
Share on other sites

Link to post
Share on other sites

I contacted Microsoft support about it and was told that they no longer do product verification via support.

 

VAMT 3.1 looks like a bigger download than I want to do for the info, but here the information about my Windows 10 key from ShowKeyPlus:

 

158587908_Win10keyinfo.png.e22e59a00fedc9b3d87ef7a4dfbaf1c1.png

 

 

Does this tell anybody anything about the type of ISO I should be installing from?

 

Also, I think that the seller of the key is from Italy.

Link to comment
Share on other sites

Link to post
Share on other sites

Weird. No, it doesn't. If it was an N or KN key, it would show like this

image.png.d7dae6eabd1113f5ce8c97607fd5e4b4.png

If I helped, hit the thumbs up icon below my post and pick it as 'Best Answer'

Resident living meme - I swear a lot; if you don't like it fuck off :^)

  My specs and shit down below.

Spoiler

Apollo: i5 4670K @ 4.6Ghz, Corsair H100i, MSI Z87I, EVGA GTX 1070 SC ACX3, Corsair 250D, 840 EVO 120GB, 1TB Seagate Barracuda, SeaSonic 520W PSU. Planned upgrades: 16GB RAM, 480/512GB SSD, new HDD

Sputnik: HP EliteBook 2570p, i5-3360M, 16GB DDR3, 256GB 840 EVO - Running Win10/Sierra dual-boot.  Future upgrades: i7-quad

Comet (home server): Atom D2500, 4GB 1066Mhz RAM, 2 x 320GB HDDs, 350W PSU, HAF-Stacker ITX, dual GbE. Cost me $80. back from the dead (mobo failure) bois

Spoiler

Main peripherals

- Corsair Strafe RGB MX Reds

- SteelSeries Siberia 650

- SteelSeries QcK+ CS:GO Camo 

- SteelSeries QcK+ Na'Vi Splash (Secondary pad, used for second rig)

- SteelSeries Rival 700

- SteelSeries Rival 300 (Secondary mouse, used for second rig)

 

 

 

Link to comment
Share on other sites

Link to post
Share on other sites

Maybe the most-likely explanation is that the MSDN ISO I downloaded from another source was an incompatible version, like maybe the N version. I'll find out when 1809 Enterprise is re-released and I give a fresh installation another try.

Link to comment
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share


×