Microsoft VAMT: The specified product key is invalid or is unsupported

von

I recently set up a KMS server and installed the Volume Activation Management Tool (VAMT) to activate product keys. Everything worked as expected for Windows Server 2016 and Windows Server 2022, but Windows Server 2019 keys caused a problem every time I tried to add them.

VAMT consistently returned this error:

The specified product key is invalid or is unsuppressed by this version of VAMT.
An update to support additional products may be available online.

At first, this looked like a key issue or a missing VAMT update. However, after some research, it became clear that the problem was not the key itself, but the way VAMT identifies and classifies it.

What caused the issue

VAMT uses pkconfig files to identify supported product keys. These files are located in the VAMT installation folder and contain the information VAMT needs to recognize different key types.

On the VAMT server, the relevant location is:

C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\VAMT3\pkconfig

In my case, the Server 2019 key was not being recognized correctly, even though the tool worked fine for other Windows Server versions. The issue appeared to be related to the pkeyconfig-csvlk.xrm-ms file used by VAMT for key identification.

The solution

The workaround was simple, but a little unusual.

The same type of file also exists on the target operating system under:

C:\Windows\System32\spp\tokens\pkeyconfig

The file that mattered in my case was:

pkeyconfig-csvlk.xrm-ms

To make VAMT accept the Server 2019 key, I did the following:

  1. Renamed the existing pkeyconfig-csvlk.xrm-ms file on the VAMT server.
  2. Copied the pkeyconfig-csvlk.xrm-ms file from a Windows Server 2019 system into the VAMT pkconfig directory.
  3. Started VAMT and entered the product key again.
  4. Closed VAMT.
  5. Renamed the original pkeyconfig-csvlk.xrm-ms file back to its previous name.

After that, VAMT accepted the Server 2019 key without any further issues.

Why this works

The problem seems to be that VAMT does not always correctly identify certain product keys based on the files it already has available. Replacing the pkeyconfig-csvlk.xrm-ms file with the version from the target operating system gives VAMT the information it needs to recognize the key properly.

This is not a new issue. Similar behavior has already been reported for older Windows versions, including Server 2012 R2. The workaround is therefore consistent with known VAMT limitations and is not limited to Server 2019.

Important note

This solution is best understood as a temporary workaround rather than a permanent replacement for proper VAMT support. It works because VAMT reads the key configuration files during validation, but the original file should be restored afterward to avoid unintended side effects.

That is why I only replaced the file long enough to add the key, then put the original file back once the entry was complete.

Conclusion

If VAMT refuses to accept a Windows Server 2019 key while other versions work without problems, the issue may be related to the pkeyconfig-csvlk.xrm-ms file rather than the key itself. Replacing the file temporarily with the version from the target operating system can resolve the identification problem and allow the key to be added successfully.

This workaround is not obvious at first, but it can save a lot of time when VAMT seems to reject a valid key for no clear reason.

Source: VAMT known issues | Microsoft Learn

Schreibe einen Kommentar