Forum Discussion

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

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'

Artem Pronichkin

Microsoft

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'

Karl-WE
MVP
Jun 22, 2026
Hi Artem Pronichkin I have tested b29595 and b29602. This time in a Hyper-V VM for easier repro.
Behaviour is different to what I earlier reported here based on a bare-metal HW installation.

Testing Settings app once again
Interestingly enough both VMs activated trought Settings app as expected, while VBscript FOD has been removed and VM restarted beforehand.

results:
b29595 - works
b29602 - works

executing slmgr returns this as expected.

--------------------------- Windows Script Host --------------------------- Can't find script engine "VBScript" for script "C:\WINDOWS\system32\slmgr.vbs". --------------------------- OK ---------------------------

Testing your PowerShell approach:
PS 5.1 b29595 - works
PS 5.1 b29602 - works
PS 7.6.2 b29595 - works
PS 7.6.2 b29602 - works

I did not expect that VMs would activate using settings app. The mentioned key, is not an AVMA key here, I assume.

Thank you for your guidance!