This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(96, 79%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENK%3C/text%3E%3C/svg%3E)
Hi Team,
I’m seeking clarity on Windows Server core-based licensing, particularly around how to handle license compliance and cost after upgrading CPU cores.
Scenario: I initially purchased and applied a Windows Server 8-core license.
The server was activated successfully using the product key.
Later, I upgraded the server hardware to 16 cores.
To stay compliant, I purchased another 8-core license pack.
My Questions:
How do I apply or register the new 8-core license pack?
There doesn’t seem to be any place in the OS to enter a second product key.
The server is already showing as activated — does anything need to be done in the OS?
Is there a way to verify or reflect licensed core count in Windows Server itself, or is the second license pack tracked only via external documentation?
Do I need to pay for the extra cores even if I don’t “activate” them in the OS?
In other words, is it mandatory to license for the full number of physical/logical cores even if there's no change in functionality or activation status?
What is Microsoft’s official expectation for audit/compliance purposes in such cases?
If I’m ever audited, how do I prove the second license pack was applied if there is no input in the OS?
I am using a volume license (or CSP) — do I need to register this second 8-core pack anywhere, like in the VLSC portal?
Additional Info:
OS: Windows Server 2022 Standard
Licensing: Core-based, purchased in 8-core increments
Activation: Done via product key (MAK or Retail)
Upgrade: Physical/VM cores increased from 8 to 16
New license pack (8-core) has been purchased but not entered into the OS since there's no mechanism to do so
Would appreciate your insights on what exactly needs to be done (if anything) and how to remain compliant both from a technical and licensing cost perspective.
Thanks in advance for your support!
To apply the second 8-core license pack, you don’t need to enter it in the OS. Windows Server doesn’t track core count directly. The license is tracked externally, so keep documentation of the second pack. Yes, you must license all cores, even if not actively used. For audit compliance, keep proof of purchase. If using a volume license or CSP, register the new license in the VLSC portal.
Hi @Tasadduq Burney ,
Thank you for the clarification regarding how additional core license packs are tracked and that there's no need to enter a second key in the OS.
I had a follow-up regarding the cost implications after upgrading the server hardware from 8 to 16 cores:
Since Windows Server licensing is based on physical core count and not usage or activation status, I understand that I’m required to license all physical cores present on the server, even if the second 8-core pack is not directly activated within the OS.
Can you please confirm the following regarding cost and compliance?
Microsoft does not reduce the licensing cost if only a portion of the total cores is actively used.
Pricing is determined purely by hardware configuration, and not dynamically adjusted by usage metrics or whether additional keys are entered.
For Volume Licensing or CSP purchases, as long as the second 8-core license pack is recorded in the VLSC portal or CSP billing system, I remain compliant and covered for audit purposes — even though the OS shows no change in activation status or licensed core count.
Essentially, the key takeaway for me is:
Licensing is a legal/contractual obligation based on hardware, not a technical limitation enforced by the OS.
Please let me know if this understanding is accurate or if there's any flexibility from Microsoft in such scenarios.
Thanks again for your guidance!