When you receive this error while trying to import your Windows 10 product keys to KMS VAMT server 3.1, the only way is to upgrade your VAMT version.
It is not possible to import Windows 10 keys in VAMT 3.1 keys.
Download the software from Microsoft:
https://msdn.microsoft.com/en-us/windows/hardware/dn913721.aspx
Direct download :
http://go.microsoft.com/fwlink/p/?LinkId=526740
Installation:
Click Next
Click Next
Click Accept
Select VAMT & Microsoft SQL Server 2012 Express if you don’t have an SQL server installed., and click Install
And Wait
Click close
Add a Database name : VAMT
Click Yes
VAMT is now installed
VAMT is now version V10.0.10240.0
Select Product Key => Add Product Key => add your product key
Add your Product key
The product key is installed.
This helped me a lot.
Thank you very much!
Oh my god, I can’t believe that solved my problem. I was running VAMT 3.1 on Windows 2008R2 SP1, and thought I already had the latest version of VAMT after running into issues with a Windows 8.1/Windows 2012 VLMS license. Trying to install the key for Windows 10/2012R2 was driving me crazy. I could get it to instal via cmd line, but not activate (at least not after the first time, which unlicensed my server, requiring telephone activation) The article I was reading was helpful-
https://blog.workinghardinit.work/2015/08/12/find-and-update-your-kms-service-host-key-to-activate-windows-10/
But didn’t resolve the issue like getting the latest version of VAMT 3.1 with that ADKSETUP link. Thanks M$, updating you software and not changing the version.
Thanks for the post!
Fought this for days, till I came across this post. Thanks for the help, it worked like a charm!
Thank you! …. I’ve been fighting this off an on now for the past 2 weeks…. Didnt think to check the File version until i had seen this.
[…] Has anyone tried the following link? I am having the same problems with Office 2016, I am trying this to see if it solves the issue. I shall let you know. [SOLVED] When Using A Volume Activation Management Tool ( VAMT ) 3.1: The Specified KMS Product Key … […]
I’m seeing the same problems with Office 2016 and none of these have fixed it. I’m also running VAMT 10 and ran the vbscript from the ISO, SW_DVD5_Office_Professional_Plus_2016_W32_English_-2_KMS_MLF_X20-96058.ISO. it looks appears that MS pulled it out of the main office ISO into it’s own.
Hey and thanks for the gread manual.
I have now the same issue when i try to import a Server 2016 Datacenter key to the VAMT
Do you have any idea how can i fix the issue.
king regards
Benjamin
For server 2016 licenses to add to the VAMT, you need at least server 2012 R2 or Server 2016 VAMT server. And off course the latest VAMT version.
Download Windows 10 ADK :
https://developer.microsoft.com/en-us/windows/hardware/windows-assessment-deployment-kit
worked perfectly