Forum Discussion

Karl-WE's avatar
Karl-WE
MVP
Jun 05, 2026
Solved

Windows Server vNext cannot be activated

Error Code 0xC004F012 when trying to activate WS vNext Datacenter with Key 2KNJJ-33Y9H-2GXGX-KMQWH-G6H67. vbscript is removed, implying the future removal of this component from the OS.  It appea...
general
management
  • Artem Pronichkin's avatar
    Artem Pronichkin
    Jun 22, 2026

    Hi Karl, thanks for reporting this.

    Can you please try running the following in elevated PowerShell? Let me know if you encounter the same (or a different) error.

     

    $key = '2KNJJ-33Y9H-2GXGX-KMQWH-G6H67'

$sls = Get-CimInstance -ClassName 'SoftwareLicensingService'
$arg = @{ 'ProductKey' = $key }
Invoke-CimMethod -InputObject $sls -MethodName 'InstallProductKey' -Arguments $arg

$slp = Get-CimInstance -ClassName 'SoftwareLicensingProduct' -Filter 'PartialProductKey <> null and ApplicationId = ''55c92734-d682-4d71-983e-d6ec3f16059f'''
Invoke-CimMethod -InputObject $slp -MethodName 'Activate'

$sls = Get-CimInstance -ClassName 'SoftwareLicensingService'
Invoke-CimMethod -InputObject $sls -MethodName 'RefreshLicenseStatus'

     

henry_collins's avatar
henry_collins
Copper Contributor
Jun 23, 2026

The activation error is likely a licensing store or activation component issue rather than the removal of VBScript itself. While slmgr.vbs has traditionally been the main management tool, the underlying activation service is separate from the script wrapper.

I agree that a native PowerShell module would be a welcome modernization, especially as VBScript is being phased out. It would be helpful if Microsoft could clarify whether PowerShell-based activation management is planned for future Windows Server releases.