In short: Open Command Prompt as administrator and run
slmgr /dli. Look at the Description line:RETAIL channelmeans Retail,OEM_DMorOEM_COAmeans OEM (came with the PC), andVOLUME_MAKorVOLUME_KMSCLIENTmeans a Volume licence (business). Retail licences can move to a new PC. OEM licences stay with the original motherboard.
Contents
- The one command check
- What each channel means
- PowerShell method (scripts and multiple PCs)
- Check the key stored in your BIOS/UEFI
- Check Office licence type too
- Red flags: when the licence type looks wrong
- FAQ
The one command check
Open Command Prompt or Terminal as administrator and run:
slmgr /dli
After a second or two, a small Windows Script Host window pops up:
Name: Windows(R), Professional edition
Description: Windows(R) Operating System, RETAIL channel
Partial Product Key: XXXXX
License Status: Licensed
The Description line tells you the licence type. That's all most people need.
Want more detail (activation ID, KMS server, expiry)? Use the verbose version:
slmgr /dlv
Tip:
slmgrshows its output in a pop-up. To print it in the console instead (handy for copying), run it throughcscript:cscript //nologo %windir%\system32\slmgr.vbs /dli
What each channel means
| Description shows | Licence type | Where it comes from | Moves to a new PC? |
|---|---|---|---|
RETAIL channel |
Retail | Bought separately (box, digital key, Microsoft Store) | Yes, one PC at a time |
OEM_DM channel |
OEM (digital marker) | Pre-installed by the PC maker, key stored in UEFI firmware | No, tied to that motherboard |
OEM_COA_NSLP / OEM_COA_SLP
|
OEM (COA sticker) | Older PCs or system builders, key on a sticker | No |
VOLUME_MAK channel |
Volume (MAK) | Business volume licensing, activated once online | Managed by the organisation |
VOLUME_KMSCLIENT channel |
Volume (KMS) | Business PCs activated by a company KMS server every 180 days | Only inside that organisation |
Retail vs OEM vs Volume in plain terms
-
Retail: you own the licence and can move it. Uninstall it from the old PC (
slmgr /upk), then activate it on the new one. If it's linked to your Microsoft account, the Activation troubleshooter can move it after a hardware change. - OEM: the licence belongs to the device. It survives reinstalls on the same PC, but a motherboard swap usually means buying a new licence.
- Volume (MAK/KMS): licensed to an organisation under a Microsoft agreement. It's normal on company laptops and not meant for home PCs (see red flags below).
PowerShell method (scripts and multiple PCs)
slmgr is fine for one machine, but PowerShell gives you clean output you can script:
Get-CimInstance SoftwareLicensingProduct -Filter `
"ApplicationID='55c92734-d682-4d71-983e-d6ec3f16059f' AND PartialProductKey IS NOT NULL" |
Select-Object Name, ProductKeyChannel, LicenseStatus, PartialProductKey
Example output:
Name : Windows(R), Professional edition
ProductKeyChannel : Retail
LicenseStatus : 1
PartialProductKey : 3V66T
-
55c92734-...is the Application ID for Windows, which filters out Office and other products. -
ProductKeyChannelgives a short value:Retail,OEM:DM,OEM:NONSLP,Volume:MAK,Volume:GVLK(GVLK = KMS client key). -
LicenseStatus:1= Licensed,0= Unlicensed,5= Notification (not activated).
Check several PCs at once
With PowerShell remoting enabled:
$pcs = 'PC-01', 'PC-02', 'PC-03'
Invoke-Command -ComputerName $pcs -ScriptBlock {
Get-CimInstance SoftwareLicensingProduct -Filter `
"ApplicationID='55c92734-d682-4d71-983e-d6ec3f16059f' AND PartialProductKey IS NOT NULL" |
Select-Object Name, ProductKeyChannel, LicenseStatus
} | Select-Object PSComputerName, Name, ProductKeyChannel, LicenseStatus |
Format-Table -AutoSize
Add | Export-Csv .\licence-audit.csv -NoTypeInformation and you have a licence audit spreadsheet.
Check the key stored in your BIOS/UEFI
Most laptops and branded desktops since Windows 8 have an OEM key embedded in the firmware. To see whether yours does, and which edition it's for:
Get-CimInstance SoftwareLicensingService |
Select-Object OA3xOriginalProductKey, OA3xOriginalProductKeyDescription
Example:
OA3xOriginalProductKey : XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
OA3xOriginalProductKeyDescription : [4.0] Core OEM:DM
-
Core= Home edition,Professional= Pro. - Empty output = no firmware key (self-built PC, or a Retail/Volume machine).
Why this matters: if the firmware key says Core (Home) but you installed Pro, Windows may refuse to activate, or quietly install the Home edition when you reinstall. Match the edition to the key, or use a Pro key.
Check Office licence type too
The same idea works for Office. For Office 2021, 2024 and LTSC (volume or retail installs), run this in an admin Command Prompt:
cscript "C:\Program Files\Microsoft Office\Office16\OSPP.VBS" /dstatus
Look for these lines:
LICENSE NAME: Office 24, Office24ProPlus2024VL_MAK_AE edition
LICENSE DESCRIPTION: Office 24, VOLUME_MAK channel
LICENSE STATUS: ---LICENSED---
(32-bit Office on 64-bit Windows lives in C:\Program Files (x86)\Microsoft Office\Office16\.)
PowerShell version, using the Office Application ID:
Get-CimInstance SoftwareLicensingProduct -Filter `
"ApplicationID='0ff1ce15-a989-479d-af46-f275c6370663' AND PartialProductKey IS NOT NULL" |
Select-Object Name, ProductKeyChannel, LicenseStatus
Microsoft 365 subscriptions don't show here. They're licensed through your account, so check them under File → Account in any Office app.
Red flags: when the licence type looks wrong
| What you see | On which PC | What it usually means |
|---|---|---|
VOLUME_KMSCLIENT |
Personal or home PC | A KMS client key was installed, often by a pre-activated image or an "activator" tool. Expect 0xC004F074 errors |
slmgr /dlv shows a KMS machine name you don't recognise |
Any PC | Activation is pointed at an unknown KMS server. Remove it with slmgr /ckms
|
VOLUME_MAK |
Personal PC bought second-hand | Likely a leftover business key that can be blocked at any time |
OEM licence |
New self-built PC with a "transferable" key | OEM keys aren't meant to move between PCs |
| Edition mismatch (Home key, Pro installed) | Any PC | Activation errors like 0xC004F210 / 0xC004F212
|
Fixing a KMS client key on a home PC: remove it and install a proper Retail or OEM key:
slmgr /upk
slmgr /cpky
slmgr /ckms
slmgr /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
slmgr /ato
If activation then throws an error, I listed every common code and its fix in Windows Activation Error Codes: Complete List With Fixes.
Prefer not to run commands? The free Noxkeys OEM vs Retail Key Checker explains what your result means and whether the licence can move to another PC.
Microsoft references:
- Slmgr.vbs options for volume activation (Microsoft Learn)
- KMS client activation keys (Microsoft Learn)
FAQ
Can I tell OEM from Retail in Windows Settings?
Not directly. Settings → System → Activation only says whether Windows is activated and whether it's a digital licence linked to your Microsoft account. Use slmgr /dli to see the channel.
Is an OEM licence worse than Retail?
No. Both are genuine and have the same features. The only difference is that OEM is tied to the original PC and support comes from the PC maker. Retail can move to a new computer.
Can I transfer a Retail licence to a new PC?
Yes, as long as it's active on only one PC at a time. Run slmgr /upk on the old PC, then enter the key on the new one. If the licence is linked to your Microsoft account, you can also use the Activation troubleshooter's "I changed hardware on this device recently" option.
What does "digital license" mean, and which type is it?
A digital licence means activation is stored on Microsoft's servers against your hardware (and optionally your Microsoft account), with no key needed on reinstall. It can come from a Retail purchase, an OEM PC or a free upgrade. slmgr /dli still shows the underlying channel.
Why does my work laptop show VOLUME_KMSCLIENT?
That's normal. Company PCs activate through the organisation's KMS server and renew every 180 days. Connect to the office network or VPN occasionally to keep it activated.
Does slmgr work on Windows 11 26H2?
Yes. slmgr and the SoftwareLicensingProduct class work the same on every current Windows 10 and Windows 11 version, including 26H2, and on Windows Server.
Which channel did your PC show? Drop it in the comments, especially if you found a surprise KMS key on a "new" laptop.
Top comments (0)