ISSUE - VAMT from Windows 11 22H2 ADK does not accept WS 2019 GVLK

[Deleted]

I am seeing this at different customers now, that VAMT 3.1 included in Windows 11 ADK 22H2 does no longer accept GVLK product keys for Windows Server 2019 Std. / Datacenter. VAMT does not accept the GVLK keys.

Windows Server 2022 and 2012, 2016 can be added without issues.

The issue was introed with the 22H2 ADK, and does not affect VAMT in 21H1 ADK.

ADK W11 22H2 is still preferable as it fixes DB incompatibility. 

Thanks for looking into this.

Repro:

Install W11 22H2 ADK > VAMT 

Open VAMT > go to product keys > try to add WS 2019 GVLK into a blank database.

(if these exist from an older VAMT DB, they will still exist / work).

sidenote: Windows Server 2022 keys (GVLK / CSVLK etc) will still appear as Windows Server 2021 in VAMT or Volume Activation Wizard (ADBA).

[#2]

@Deleted 

Karl, were you able to find a resolution to this?  We can't import 2019 standard keys, but all other keys imported just fine.

[#3]

@Bill_Watts oh yes, found a way. Meanwhile the Windows Server Insider team have raised an internal ticket to address this issue.

Here's my new guide how to solve it (workaround):

HOW-TO : Use VAMT 3.1 for Windows Server activation 2016 through 2022 and license management - Micro...

[#4]

Thanks Karl. I'll attempt the workaround this week.

[#5]

@Bill_Watts keep us posted!