Home
⚠️ Since version 2410, we no longer update the VLMCSD on Floppy disk. Instead, we encourage people to move to Docker container - which is more reliable, and easier to deploy and manage.
Volume License Management Service is a free, open-source software to provide a volume-activation for Windows and Office products.
It is the replacement (or the solution for Linux) of Key Management Services on Windows Server (in term of operation), by provide less infrastructure compared to the Windows Server deployment (even the minimal one), or act as a backup solution in case the main Windows KMS Host fails.
For guide and help (written by the original developers), see here
| Contributor | Description |
|---|---|
| Hotbird64 | Original developer of VLMCSD |
| Wind4 | Contributor of VLMCSD |
| kkkgo | Contributor of VLMCSD |
| HarukaMa | Contributor of VLMCSD |
| Nang | Contributor of VLMCSD database |
| shiroinekotfs | Contributor of VLMCSD and VLMCSD Database |
| anhvlt-2k6 | Contributor of VLMCSD and VLMCSD Database |
⚠️ NoteOnly available when you have installed
gcc,git,glibc, andmakein your system.On Ubuntu/Debian, you can try
apt install -y gcc git make
curl -sSL https://raw.githubusercontent.com/tfslabs/vlmcsd/refs/heads/master/.systemd/install.sh | sudo bashOn a system having too many applications running, using Docker is the better way to deploy, maintain, and retire Volume License Management Service
Containerized vlmcsd for Linux are available on Docker Hub. By default, the container will expose port 1688. Containerized images are available for supporting architectures. You can try these available architectures by using following command lines
# AMD64
docker run -p 1688:1688 theflightsims/vlmcsd:linux-amd64
# ARM64
docker run -p 1688:1688 theflightsims/vlmcsd:linux-arm64v8
# PPC64LE
docker run -p 1688:1688 theflightsims/vlmcsd:linux-ppc64le
# S390X
docker run -p 1688:1688 theflightsims/vlmcsd:linux-s390x
# RISCv64
docker run -p 1688:1688 theflightsims/vlmcsd:linux-riscv64If you want to deploy by yourself, you can try advanced arguments with vlmcsd (Volume License Management Service DAEMON)
$ ./vlmcsd -h
Volume License Management Service DAEMON (vlmcsd)
Build Date: Aug 19 2025
Usage:
./vlmcsd [Options]
Available options:
-u <user> set uid to <user>
-g <group> set gid to <group>
-a <csvlk>=<epid> Use an ePID value for a set of CSVLK. ePID is known as the ID of the activation client, while the CSVLK is the key for KMS activation
-r (0|1|2) Set randomization level of the ePIDs (default is "0")
"0" stands for no randomization, which also means VLMCSD will use the default ePID that is built-in. It is useful for emulating/replicating real KMS servers
"1" stands for randomization of each KMS request, but it also poses a risk of being detected non-genuine KMS Server, causing clients to fail to be activated
"2" is as same as the "1" option, but only for debugging
-C <LCID> Use fixed Windows Language Code Identifier in random ePIDs
See https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-lcid/a9eac961-e77d-41a6-90a5-ce1a8b0cdb9c for correct LCIDs
-H <build> Use fixed Windows build number for activation
Useful when the client requires a proper KMS Server
See all build numbers here: https://en.wikipedia.org/wiki/List_of_Microsoft_Windows_versions
-o (0|1|2|3) Set protection level against clients with public IP addresses (default 0)
"0" for no protection, allowing all IP addresses to use KMS service
"1" only allows VLMCSD service replies connection with IP addresses in the range define by RFC1918 and RFC6598
"2" does not affect the interfaces, while it only check if the client is either external (outbound) and drops its TCP packets when detected
"3" is the combination of "1" and "2", for dropping package to that public IP addresses and no reply to that IP addresses
-x (0|1) Configure how VLMCSD deal with errors while operating (default 0)
"0" will make VLMCSD stay as long as possible, only exit the interface that having problem (including VPN)
"1" will exit VLMCSD process if there are any problem with any network interface
-L <address>[:port] Listen on the specific IP Address (IPv4/IPv6) with port defined optionally
-P <port> Set the specific TCP port for subsequent "-L" statement (default 1688)
If you use "-P" alongside with "-L", "-P" must be specified before "-L"
-F0, -F1 Disable/enable binding to foreign IP addresses
-m <clients> Maximum clients VLMCSD can handle at the same time
-e Logging to command line interface (stdout). Useful when running VLMCSD on Docker Container, or floppy on Virtual Machine
-D Run VLMCSD in foreground, useful when in the debugging. Windows is not compatible with this feature
-K (0|1|2|3) Set white-listing level which product VLMCSD accepts or refuses (default 0)
"0" Activate all products with an unknown, retail or beta/preview KMS IDs
"1" Activate products with a retail or beta/preview KMS ID but refuse to activate products with an unknown KMS ID
"2" Activate products with an unknown KMS ID but refuse products with a retail or beta/preview KMS ID
"3" Activate only products with a known volume license RTM KMS ID and refuse all others
-c (0|1) Disable (0)/Enable (1) client time checking
If the client time is different than 4 hours compare to the KMS Host, the host will deny the activation (default 0)
Note: It is recommended that the VLMCSD has a reliable time service (e.g. sync the time with time.windows.com)
-M (0|1) Disable (0)/Enable (1) maintaining clients (default 0)
Note: Enabling this service is not recommended, except you have to do so to prevent the activation failling
It is because the VLMCSD can only keep maximum of 16777215 clients. If that number exceed, VLMCSD will no longer accept any new connect, nor activation requests
-E (0|1) Disable (0)/Enable (1) starting VLMCSD with empty client list (Default 0)
Note: It is recommended to keep the default, because Office will not activate unless your KMS Host has at least 5 active clients.
See more: https://learn.microsoft.com/en-us/office/troubleshoot/administration/0xc004f038-computer-not-activate
-t <seconds> Disconnect client after an amount of time of inactivity (default 30)
-d Disconnect each client after processing one activation request.
-k Do not disconnect clients after processing an activation request (default if "-d" defined in external VLMCSD configuration file).
-N (0|1) Disable (0)/Enable (default, 1) NDR64. Only useful when on Windows Vista/7 32-bit, where enabling NDR64 will make VLMCSD by running higher Windows build number.
-B (0|1) Disable (0)/Enable (1) bind time feature negotiation in RPC protocol.
-p <file> Create pid file filename. This is used by standard init scripts (typically found in "/etc/init.d").
-i <file> Use external VLMCSD configuration file. Default name of that file is "vlmcsd.ini".
-j <file> Use external VLMCSD ePID database. Default name of that file is "vlmcsd.kmd".
-R <interval> Renew activation every <interval> (default 1w).
-A <interval> Retry activation every <interval>, if the previous activation/reactivation is failed (default 2h).
-l <file> Writes VLMCSD log into a file. Note: Make sure you have read+write access to that file.
-T0, -T1 Disable (0)/Enable logging client connection with time and date (default 1).
-v Allow logging verbose.
-q Don't allow log verbose (default).
-V Display version information and exitHowever, your configuration may need to be verified before implement in practical. To do it, you can use vlmcs (Volume License Management Service - Client Emulator)
$ ./vlmcs -l
Volume License Management Service - Client Emulator
Build Date: Aug 19 2025
Usage: ./vlmcs [<Host>:<port> | <FQDN>:<port> ] [Advanced Options]
Basic Operation:
<host>: Host name of the KMS to use. Blank means leaving the default local hosting
<FQDN>: Target to the VLMCSD server with a Domain or FQDN
<port>: TCP port name of the KMS to use. Blank means leaving the default port 1688.
Advanced options:
-v: Verbose logging
-l: Using available Application ID, which can be shown in "./vlmcs -x"
-4: Force KMS V4 protocol
-5: Force KMS V5 protocol
-6: Force KMS V6 protocol
-i: Use IP protocol (4 or 6)
-j: Load external KMS data file
-e: Show some valid examples
-x: Show valid Apps
-d: No DNS names, use NetBIOS names (no effect if -w is used)
-V: Show version information and exit
-a: Use custom Application GUID
-s: Use custom Activation Configuration GUID
-k: Use custom KMS GUID
-c: Use custom Client GUID. Default: Use random
-o: Use custom previous Client GUID. Default: ZeroGUID
-K: Use a specific (possibly invalid) protocol version
-w: Use custom workstation name. Default: Use random
-r: Fake required clients
-n: Fixed # of requests (Default: Enough to charge)
-m: Pretend to be a virtual machine
-G: Get ePID/HwId data and write to <file>. Can't be used with -l, -4, -5, -6, -a, -s, -k, -r and -n
-T: Use a new TCP connection for each request.
-N: <0|1> disable or enable NDR64. Default: 1
-B: <0|1> disable or enable RPC bind time feature negotiation. Default: 1
-t: Use specific license status (0 <= T <= 6)
-g: Use a specific binding expiration time in minutes. Default 43200
-P: Ignore priority and weight in DNS SRV records
-p: Don't use multiplexed RPC bindNormally, the recommendation for the daemon service is ...
vlmcsd -P 1688 -H 26100 -C 1033 -T0 -e -v -D... which means
-
-P 1688- It exposes the port 1688 of TCP (default port of KMS). -
-H 26100- Host build is 26100. You can alter this to your current latest build number. -
-C 1033- The locale language is English (US) -
-T0- Do not check the current time. It is for the validation -
-e- Logging tostdout. Useful to check logging on Docker or onsystemd -
-v- Verbose logging -
-D- Running in foreground
When deployed, Volume License Management Service usually works out of the box if installed via Docker or the systemd install script, but some deployment and operational aspects still require attention.
Usually, some environments (with a high number of computers) require a large number of activation requests and a small, single server may not good enough. Since vlmcsd is designed for small, easy deployment, you can try deploy it into multiple devices in your organization, with the same configuration.
Microsoft, by default, limits the current version of KMS Host to the maximum version you can activate for Windows clients. That means, you cannot (practically) use the host build number of Windows Server 2016 to activate a "client" of Windows Server 2022 or Windows 11 (because build number of Windows Server 2016 is 14393, while Windows Server 2022 has build number of 20348 and Windows 11 has "minimum" build of 22000, except the case of Windows Server 2022 can activate Windows 11).
The same thing also happen on the "client" KMS Host, when use the client build, you may cannot activate the Windows Server (all versions).
That is the reason in the recommendation/default configuration for the daemon, the host build -H is always set to the latest version of Windows Server on the database of the Volume License Management Service, because it helps the daemon always replies to all of clients correctly.
However, if you don't use external Volume License Database .kmd, the default database and the default host build number are always up-to-date.
You can see the following table to know which version of KMS host can activate which client (Source from Microsoft Learn)
| CSVLK group | CSVLK can be hosted on |
Windows editions activated by this KMS host |
|---|---|---|
| Volume License for Windows Server 2025 |
|
|
| Volume License for Windows Server 2022 |
|
|
| Volume License for Windows Server 2019 |
|
|
| Volume License for Windows Server 2016 |
|
|
| Volume license for Windows 10 |
|
|
KMS activations are valid for up to 180 days. Clients will try to re-activate at default intervals (e.g., retry interval is typically 1 day by default for failed attempts). Clients also renew the license periodically (by default every 14 days).
Microsoft requires that the KMS "client" is only be activated if there are 25 clients (in the case of Windows Client/Window Server editions) or 5 clients (in the case of Microsoft Office) contact the server in the last 30-day, and caching them in the most 50 recent contacts.
By default of Volume License Management Service, the daemon will automatically "pre-charge" itself up to 24 clients of Windows and 4 clients of Office (leaving 1 remaining for the complete charging).
You can also try -E1 command to experience this, in some case you need to "trick" to strict client to verify these actual markup, instead of the fake "pre-charge" ones. However, be careful of the error "0xC004F038: The computer couldn't be activated" error in KMS activation.
Some deployments require special strict versions of KMS. For example, your deployment is pretty new and you do not want to install any "pre-release" version of Windows or Office - which may lead into the service disruption, unstable, or crashing. You can try the -K flags to do this.
"0" Activate all products with an unknown, retail or beta/preview KMS IDs
"1" Activate products with a retail or beta/preview KMS ID but refuse to activate products with an unknown KMS ID
"2" Activate products with an unknown KMS ID but refuse products with a retail or beta/preview KMS ID
"3" Activate only products with a known volume license RTM KMS ID and refuse all othersBy default, time checking is disabled, as the goal of the Volume License Management Service design is to make client activation as easy as possible.
However, if you host KMS as a monolithic service, you should enable this feature (using -c1) to detect and prevent unauthorized activation. This feature checks whether the time is 4 hours different.
If you are hosting Volume License Management Service in the network where Active Directory or self-hosting domain is active, having a SRV on the DNS Server may help the client determine which is the best and reliable server to contact with. The SRV looks like this
| Property | Value |
|---|---|
| Type | SRV |
| Service/Name | _vlmcs |
| Protocol | _tcp |
| Priority | 0 |
| Weight | 0 |
| Port number | 1688 |
| Hostname | <FQDN-of-KMS-host> |
Replace <FQDN-of-KMS-host> with your actual KMS Host's FQDN.
In non-Microsoft DNS Server, like bind9 or dnsmasq, the DNS configuration may look like this (do not forget to replace the target and example.com with your actual deployment, see the SRV record configuration)
; _service._proto.name. TTL class SRV priority weight port target.
_vlmcs._tcp.example.com. 86400 IN SRV 0 0 1688 net-srv-01.example.com.
Currently (in case no external database is loaded), the Volume License Management Service can only activate these following products (try to fetch the database with vlmcs -x)
$ ./vlmcs -x
You may use these product names or numbers:
1 = Windows Vista Business 127 = Windows Server 2022 Standard
2 = Windows Vista Business N 128 = Windows Server 2022 Datacenter
3 = Windows Vista Enterprise 129 = Windows Server 2022 Datacenter: Azure Edition
4 = Windows Vista Enterprise N 130 = Windows Server 2022 Standard (SAC)
5 = Windows 7 Enterprise 131 = Windows Server 2022 Datacenter (SAC)
6 = Windows 7 Enterprise E 132 = Windows Server 2025 Standard
7 = Windows 7 Enterprise N 133 = Windows Server 2025 Datacenter
8 = Windows 7 Professional 134 = Windows Server 2025 Datacenter: Azure Edition
9 = Windows 7 Professional E 135 = Office Professional Plus 2010
10 = Windows 7 Professional N 136 = Office Small Business Basics 2010
11 = Windows 7 Embedded POSReady 137 = Office Standard 2010
12 = Windows 7 Embedded Standard 138 = Office Access 2010
13 = Windows 7 ThinPC 139 = Office Excel 2010
14 = Windows 8 Core 140 = Office Groove 2010
15 = Windows 8 Core Country Specific 141 = Office InfoPath 2010
16 = Windows 8 Core N 142 = Office Mondo 1 2010
17 = Windows 8 Core Single Language 143 = Office Mondo 2 2010
18 = Windows 8 Core ARM 144 = Office OneNote 2010
19 = Windows 8 Professional WMC 145 = Office OutLook 2010
20 = Windows 8 Embedded Industry Professional 146 = Office PowerPoint 2010
21 = Windows 8 Embedded Industry Enterprise 147 = Office Project Pro 2010
22 = Windows 8 Enterprise 148 = Office Project Standard 2010
23 = Windows 8 Enterprise N 149 = Office Publisher 2010
24 = Windows 8 Professional 150 = Office Visio Premium 2010
25 = Windows 8 Professional N 151 = Office Visio Pro 2010
26 = Windows 8.1 Core 152 = Office Visio Standard 2010
27 = Windows 8.1 Core ARM 153 = Office Word 2010
28 = Windows 8.1 Core Country Specific 154 = Office Professional Plus 2013 (Preview)
29 = Windows 8.1 Core N 155 = Office Access 2013 (Preview)
30 = Windows 8.1 Core Single Language 156 = Office Excel 2013 (Preview)
31 = Windows 8.1 Professional Student 157 = Office Groove 2013 (Preview)
32 = Windows 8.1 Professional Student N 158 = Office InfoPath 2013 (Preview)
33 = Windows 8.1 Professional WMC 159 = Office Lync 2013 (Preview)
34 = Windows 8.1 Core Connected 160 = Office Mondo 2013 (Preview)
35 = Windows 8.1 Core Connected Country Specific 161 = Office OneNote 2013 (Preview)
36 = Windows 8.1 Core Connected N 162 = Office Outlook 2013 (Preview)
37 = Windows 8.1 Core Connected Single Language 163 = Office PowerPoint 2013 (Preview)
38 = Windows 8.1 Enterprise 164 = Office Project Pro 2013 (Preview)
39 = Windows 8.1 Enterprise N 165 = Office Project Standard 2013 (Preview)
40 = Windows 8.1 Professional 166 = Office Publisher 2013 (Preview)
41 = Windows 8.1 Professional N 167 = Office Visio Pro 2013 (Preview)
42 = Windows 8.1 Embedded Industry Professional 168 = Office Visio Standard 2013 (Preview)
43 = Windows 8.1 Embedded Industry Automotive 169 = Office Word 2013 (Preview)
44 = Windows 8.1 Embedded Industry Enterprise 170 = Office Professional Plus 2013
45 = Windows 10/11 Home 171 = Office Standard 2013
46 = Windows 10/11 Home Preview 172 = Office Access 2013
47 = Windows 10/11 Home Country Specific 173 = Office Excel 2013
48 = Windows 10/11 Home Country Specific Preview 174 = Office InfoPath 2013
49 = Windows 10/11 Home N 175 = Office Lync 2013
50 = Windows 10/11 Home N Preview 176 = Office Mondo 2013
51 = Windows 10/11 Home Single Language 177 = Office OneNote 2013
52 = Windows 10 Enterprise 2015 LTSB S 178 = Office OutLook 2013
53 = Windows 10 Enterprise 2015 LTSB SN 179 = Office PowerPoint 2013
54 = Windows 10 Enterprise 2016 LTSB S 180 = Office Project Pro 2013
55 = Windows 10 Enterprise 2016 LTSB SN 181 = Office Project Standard 2013
56 = Windows 10 Enterprise LTSC (2019, 2021)/Windows 11 Enterprise LTSC 2024 S 182 = Office Publisher 2013
57 = Windows 10 Enterprise LTSC (2019, 2021)/Windows 11 Enterprise LTSC 2024 SN 183 = Office Visio Pro 2013
58 = Windows 10/11 Enterprise for Virtual Desktops 184 = Office Visio Standard 2013
59 = Windows 10/11 S (Lean) 185 = Office Word 2013
60 = Windows 10/11 SE 186 = Office Standard 2016
61 = Windows 10/11 SE N 187 = Office Professional Plus 2016
62 = Windows 10/11 Education 188 = Office Access 2016
63 = Windows 10/11 Education N 189 = Office Excel 2016
64 = Windows 10/11 Professional 190 = Office Mondo 2016
65 = Windows 10/11 Professional N 191 = Office Mondo R 2016
66 = Windows 10/11 Professional Education 192 = Office OneNote 2016
67 = Windows 10/11 Professional Education N 193 = Office Outlook 2016
68 = Windows 10/11 Professional Workstation 194 = Office Powerpoint 2016
69 = Windows 10/11 Professional Workstation N 195 = Office Project Pro 2016
70 = Windows 10/11 Enterprise 196 = Office Project Pro 2016 C2R
71 = Windows 10/11 Enterprise Preview 197 = Office Project Standard 2016
72 = Windows 10/11 Enterprise N 198 = Office Project Standard 2016 C2R
73 = Windows 10/11 Enterprise N Preview 199 = Office Publisher 2016
74 = Windows 10/11 Enterprise S Preview 200 = Office Skype for Business 2016
75 = Windows 10/11 Enterprise SN Preview 201 = Office Visio Pro 2016
76 = Windows 10/11 Enterprise for Virtual Desktops Preview 202 = Office Visio Pro 2016 C2R
77 = Windows IoT Enterprise LTSC (2021, 2024) 203 = Office Visio Standard 2016
78 = Windows 10/11 Enterprise G 204 = Office Visio Standard 2016 C2R
79 = Windows 10/11 Enterprise G N 205 = Office Word 2016
80 = Windows 8/10 Preview Enterprise 206 = Office Standard 2019
81 = Windows 8/10 Preview Professional 207 = Office Professional Plus 2019
82 = Windows 8/10 Preview ProfessionalWMC 208 = Office Professional Plus 2019 Preview
83 = Windows 8/10 Preview Core 209 = Office Access 2019
84 = Windows 8/10 Preview CoreARM 210 = Office Excel 2019
85 = Windows Server 2008 Web 211 = Office Outlook 2019
86 = Windows Server 2008 Compute Cluster 212 = Office Powerpoint 2019
87 = Windows Server 2008 Standard 213 = Office Project Pro 2019
88 = Windows Server 2008 Standard without Hyper-V 214 = Office Project Pro 2019 Preview
89 = Windows Server 2008 Enterprise 215 = Office Project Standard 2019
90 = Windows Server 2008 Enterprise without Hyper-V 216 = Office Publisher 2019
91 = Windows Server 2008 Datacenter 217 = Office Skype for Business 2019
92 = Windows Server 2008 Datacenter without Hyper-V 218 = Office Visio Pro 2019
93 = Windows Server 2008 Enterprise for Itanium 219 = Office Visio Pro 2019 Preview
94 = Windows MultiPoint Server 2010 220 = Office Visio Standard 2019
95 = Windows Server 2008 R2 Web 221 = Office Word 2019
96 = Windows Server 2008 R2 HPC Edition 222 = Office LTSC Professional Plus 2021
97 = Windows Server 2008 R2 Standard 223 = Office LTSC Professional Plus 2021 Preview
98 = Windows Server 2008 R2 Enterprise 224 = Office LTSC Standard 2021
99 = Windows Server 2008 R2 Datacenter 225 = Office Access LTSC 2021
100 = Windows Server 2008 R2 Enterprise for Itanium 226 = Office Excel LTSC 2021
101 = Windows Server 2012 Essentials 227 = Office Outlook LTSC 2021
102 = Windows Server 2012 Datacenter 228 = Office Powerpoint LTSC 2021
103 = Windows Server 2012 Standard 229 = Office Project Pro 2021
104 = Windows Server 2012 MultiPoint Premium 230 = Office Project Pro 2021 Preview
105 = Windows Server 2012 MultiPoint Standard 231 = Office Project Standard 2021
106 = Windows Server 2012 R2 Next Standard 232 = Office Publisher LTSC 2021
107 = Windows Server 2012 R2 Next Web 233 = Office Skype for Business LTSC 2021
108 = Windows Server 2012 R2 Essentials 234 = Office Visio LTSC Pro 2021
109 = Windows Server 2012 R2 Datacenter 235 = Office Visio LTSC Pro 2021 Preview
110 = Windows Server 2012 R2 Standard 236 = Office Visio LTSC Standard 2021
111 = Windows Server 2012 R2 Cloud Storage 237 = Office Word LTSC 2021
112 = Windows Server 2016 Azure Core 238 = Office LTSC Professional Plus 2024
113 = Windows Server 2016 Essentials 239 = Office LTSC Professional Plus 2024 Preview
114 = Windows Server 2016 Datacenter 240 = Office LTSC Standard 2024
115 = Windows Server 2016 Standard 241 = Office Access LTSC 2024
116 = Windows Server 2016 ARM64 242 = Office Excel LTSC 2024
117 = Windows Server 2016 Datacenter (SAC) 243 = Office Outlook LTSC 2024
118 = Windows Server 2016 Standard (SAC) 244 = Office PowerPoint LTSC 2024
119 = Windows Server 2016 Cloud Storage 245 = Office Project Pro LTSC 2024
120 = Windows Server 2019 Azure Core 246 = Office Project Pro LTSC 2024 Preview
121 = Windows Server 2019 Essentials 247 = Office Project Standard LTSC 2024
122 = Windows Server 2019 Datacenter 248 = Office Skype for Business LTSC 2024
123 = Windows Server 2019 Standard 249 = Office Visio LTSC Pro 2024
124 = Windows Server 2019 ARM64 250 = Office Visio LTSC Pro 2024 Preview
125 = Windows Server 2019 Datacenter (SAC) 251 = Office Visio LTSC Standard 2024
126 = Windows Server 2019 Standard (SAC) 252 = Office Word LTSC 2024| Error code | Error message | Activation type |
|---|---|---|
| 0x8007000D | The KMS host you are using cannot handle your product. It only supports legacy versions. | KMS client |
| 0x8004FE21 | This computer is not running genuine Windows. | MAK/KMS client |
| 0x80070005 | Access denied. The requested action requires elevated privileges. | MAK/KMS client/KMS host |
| 0x8007007b | DNS name does not exist. | KMS client |
| 0x80070490 | The product key you entered didn't work. Check the product key and try again, or enter a different one. | MAK |
| 0x800706BA | The RPC server is unavailable. | KMS client |
| 0x8007232A | DNS server failure. | KMS host |
| 0x8007232B | DNS name does not exist. | KMS client |
| 0x8007251D | No records found for DNS query. | KMS client |
| 0x80092328 | DNS name does not exist. | KMS client |
| 0xC004B100 | The activation server determined that the computer could not be activated. | MAK |
| 0xC004C001 | The activation server determined the specified product key is invalid | MAK |
| 0xC004C003 | The activation server determined the specified product key is blocked | MAK |
| 0xC004C008 | The activation server determined that the specified product key could not be used. | KMS |
| 0xC004C020 | The activation server reported that the Multiple Activation Key has exceeded its limit. | MAK |
| 0xC004C021 | The activation server reported that the Multiple Activation Key extension limit has been exceeded. | MAK |
| 0xC004F009 | The Software Protection Service reported that the grace period expired. | MAK |
| 0xC004F00F | The Software Licensing Server reported that the hardware ID binding is beyond level of tolerance. | MAK/KMS client/KMS host |
| 0xC004F014 | The Software Protection Service reported that the product key is not available | MAK/KMS client |
| 0xC004F02C | The Software Protection Service reported that the format for the offline activation data is incorrect. | MAK/KMS client |
| 0xC004F035 | The Software Protection Service reported that the computer could not be activated with a Volume license product key. | KMS client/KMS host |
| 0xC004F038 | The Software Protection Service reported that the computer could not be activated. The count reported by your Key Management Service (KMS) is insufficient. Please contact your system administrator. | KMS client |
| 0xC004F039 | The Software Protection Service reported that the computer could not be activated. The Key Management Service (KMS) is not enabled. | KMS client |
| 0xC004F041 | The Software Protection Service determined that the Key Management Server (KMS) is not activated. KMS needs to be activated. | KMS client |
| 0xC004F042 | The Software Protection Service determined that the specified Key Management Service (KMS) cannot be used. | KMS client |
| 0xC004F050 | The Software Protection Service reported that the product key is invalid. | MAK/KMS/KMS client |
| 0xC004F051 | The Software Protection Service reported that the product key is blocked. | MAK/KMS |
| 0xC004F064 | The Software Protection Service reported that the non-genuine grace period expired. | MAK |
| 0xC004F065 | The Software Protection Service reported that the application is running within the valid non-genuine period. | MAK/KMS client |
| 0xC004F06C | The Software Protection Service reported that the computer could not be activated. The Key Management Service (KMS) determined that the request timestamp is invalid. | KMS client |
| 0xC004F074 | The Software Protection Service reported that the computer could not be activated. No Key Management Service (KMS) could be contacted. Please see the Application Event Log for additional information. | KMS client |