question

KEN-6786 avatar image
0 Votes"
KEN-6786 asked Dgorter commented

VAMT Error when import Windows 10 Enterprise LTSC MAK key

Hi Guys,

It get error "The specified product key is invalid or is unsupported by this version of VAMT" when import Windows 10 Enterprise LTSC 2019 MAK key.

Below URL can't fix.

https://docs.microsoft.com/en-us/windows/deployment/volume-activation/vamt-known-issues#workarounds-for-adding-csvlks-for-windows-10-activation-to-vamt-31

Can't find the file 485392_intl_x64_zip file from the URL, just copy the csvlk.xrm-ms to C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\VAMT3\pkconfig can't fix the error.

My platform below:

Windows Server 2016

VMAT 3.1

Windows Assessment and Deployment Kit - Windows 10 (10.1.14393.0)

How to solve this problem? should I need to upgrade the Windows ADK Win10 to version 10.1.9041.1?



Regards

Thanks...KEN

windows-10-setup
· 4
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hello,
You need to update the version of VAMT that you have. It doesn't have the latest version of the PKCONFIG_*.xrm-ms which contains the updated keys for the newer version of Windows.
The latest version of Windows ADK is available here
https://docs.microsoft.com/en-us/windows-hardware/get-started/adk-install

The PKCONFIG files for VAMT are located in this folder , mine are dated 4\18\2019
C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\VAMT3\pkconfig

You could try copying the correct *.xrm-ms file for the key being deployed from the version of Windows that you are wanting to activate.
the license file folders are located under C:\Windows\System32\spp\tokens\skus\ : You would need the correct folder of Windows edition and the correct license file for the key being used to be located in the above listed pkconfig file. It would likely be easier to download the latest ADK.


0 Votes 0 ·

Hello,
The VAMT version should be Version: 10.1.19041.0
You list 3.1 above as the version but I think that is the version of MMC being used not the VAMT version, in VAMT under help about there are two entries for about, one listed the MMC version and one lists the version of VAMT.

0 Votes 0 ·

Hi,


The link you referenced is relate with adding KMS host key into VAMT, however I noticed you said you are using MAK, so I am a little confuse about your product key type. Where did you buy the product key? Through Volume Licensing Service Center or others? Please check your product key type again.

Did you used the key to activated Windows 10 yet?

Bests,


0 Votes 0 ·

Hello,
The product key doesn't matter, this is simply an issue where the Product key being used is not recognized by VAMT, this is almost always because an older version of VAMT Is being used. With each release of Windows, there are new key ranges being identified, this key ranges have to be updated in VAMT or the product key will not be recognized. So with each release a new version of VAMT is made available that contains the updated key ranges. the updated ranges are for all key types, including but not limited to MAK and KMS keys.

0 Votes 0 ·

1 Answer

LeonLaude avatar image
0 Votes"
LeonLaude answered

Hi,

Since you're running the Volume Activation Management Tool (VAMT) on a Windows Server 2016, you can also ask in the dedicated forum below where they are actively answering questions:

Windows Server 2016
https://social.technet.microsoft.com/Forums/en-US/home?forum=ws2016


Best regards,
Leon

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.