Office LTSC Professional Plus 2024 relies on volume licensing infrastructure, utilizing either a Key Management Service (KMS) or a Multiple Activation Key (MAK) to authenticate. When activation fails, it typically points to a disruption in network communication with the host server, residual product keys from previous Office installations (like Office 2019 or 2021) creating conflicts, or an outdated KMS host that lacks the 2024 Volume License Pack. This troubleshooting guide provides the exact command-line diagnostic checks and configuration steps to clear conflicting licenses, force a host connection, and successfully activate your deployment.
Diagnosing Specific Volume Activation Error Codes
Before changing configuration files, you must identify the exact reason the activation request is being rejected. The Windows activation framework outputs specific hexadecimal error codes that distinguish a network failure from a license quota issue.
To find your specific error code, open Command Prompt as an administrator and execute the following command to query the Software Protection Platform:
cscript "%ProgramFiles%\Microsoft Office\Office16\ospp.vbs" /dstatus
Note: Office LTSC 2024 continues to use the "Office16" internal directory path. If you installed the 32-bit version on a 64-bit OS, use %ProgramFiles(x86)% instead.
Match the error code in your command output to the table below to determine your next action:
| Error Code | Observable Cause | Required Fix |
|---|---|---|
| 0xC004F074 | KMS Client cannot reach the KMS Host. DNS auto-discovery failed or Port 1688 is blocked. | Manually assign the KMS host name and open outbound firewall rules. |
| 0xC004C020 | The assigned MAK has exceeded its maximum allowed activation limit on Microsoft's servers. | Request a MAK quota increase via the Volume Licensing Service Center (VLSC). |
| 0xC004F038 | The KMS host lacks the required minimum threshold of 5 unique client requests. | Add more Office LTSC clients to the network to meet the minimum threshold. |
Removing Residual License Conflicts
Upgrading a machine from an older perpetual release often leaves hidden product keys in the Windows registry. The Office LTSC 2024 installer does not automatically purge these, causing the activation wizard to attempt authentication against an expired or invalid endpoint.
- Step 1: Launch Command Prompt with administrative privileges.
- Step 2: Run cscript "%ProgramFiles%\Microsoft Office\Office16\ospp.vbs" /dstatus to list all installed keys.
- Step 3: Look through the output for any line reading "Last 5 characters of installed product key: XXXXX". Note the 5 characters for any license that is not your LTSC 2024 key.
- Step 4: Execute cscript "%ProgramFiles%\Microsoft Office\Office16\ospp.vbs" /unpkey:XXXXX (replace XXXXX with the identified characters).
- Step 5: The terminal will output "Product key uninstall successful". Repeat this until only your LTSC 2024 key remains, or until the list is entirely clear.
Configuring KMS Host and DNS Settings Manually
If your enterprise environment does not use DNS SRV records to automatically broadcast the KMS server's location, Office LTSC 2024 will fail to activate. You must point the software directly to your activation server.
From an elevated Command Prompt, follow this sequence:
- Step 1: Install your LTSC 2024 Generic Volume License Key (GVLK) by typing cscript "%ProgramFiles%\Microsoft Office\Office16\ospp.vbs" /inpkey:[Your-25-Character-GVLK] and pressing Enter.
- Step 2: Assign the host address by typing cscript "%ProgramFiles%\Microsoft Office\Office16\ospp.vbs" /sethst:[kms.yourdomain.com] (replace the bracketed text with your actual KMS server IP or FQDN).
- Step 3: If your network administrator changed the default activation port, set it by typing cscript "%ProgramFiles%\Microsoft Office\Office16\ospp.vbs" /setprt:[Port Number]. If using the default, you can skip this step. The default is 1688.
- Step 4: Force the activation request by typing cscript "%ProgramFiles%\Microsoft Office\Office16\ospp.vbs" /act.
To verify success, look for the line "
Updating the KMS Host Server
If the client connects successfully but activation is still rejected, the issue likely resides on the server side. A KMS host running Windows Server 2019 or 2022 cannot authenticate Office LTSC 2024 clients out of the box. The server administrator must download and install the official Microsoft Office LTSC 2024 Volume License Pack. Once installed on the host, the administrator must input the KMS Host Key provided in the Microsoft 365 Admin Center and activate the server against Microsoft's endpoints. Only then will the host successfully process your local client's request.
Maintaining Document Workflows with WPS Office


Troubleshooting enterprise volume licensing, waiting for an IT administrator to update a KMS host, or dealing with blocked MAK limits through the Volume Licensing Service Center can lock you out of editing critical documents for days. WPS Office cannot interact with Microsoft's KMS registry settings or authenticate your LTSC 2024 key. However, if your immediate goal is to open, edit, and export your files while the licensing issue is being resolved, WPS Office provides a direct bypass to the problem.
Because WPS Office relies on its own independent licensing and installation framework, it completely sidesteps KMS port 1688 restrictions, DNS auto-discovery failures, and registry conflicts. To regain immediate access to your work:
- Step 1: Install WPS Office on your local machine. It requires no volume licensing deployment tools.
- Step 2: Right-click your locked `.docx`, `.xlsx`, or `.pptx` file, select "Open With", and choose WPS Office.
- Step 3: Edit your document using the native ribbon interface. WPS Office reads and writes directly in standard XML formats, ensuring no formatting is lost when you eventually send the file back to a user on a Microsoft environment.
- Step 4: Utilize built-in tools like the PDF editor and integrated AI writing assistant to complete tasks without needing secondary applications or waiting for your enterprise activation server to come back online.
Frequently Asked Questions
Why does the activation script return error 0x80070005?
Error 0x80070005 translates to "Access Denied." This occurs when you attempt to run the ospp.vbs script from a standard user Command Prompt. Modifying software licensing registries requires elevated privileges. Close your current terminal, click the Start menu, type "cmd", right-click Command Prompt, and select "Run as administrator" before repeating your activation commands.
Can I activate via MAK without an internet connection?
Yes. If your workstation is air-gapped, you can use Telephone Activation. Open a Command Prompt as administrator and run slui.exe 4. Select your country to generate an Installation ID. Call the provided Microsoft toll-free number, input the Installation ID via your phone's keypad, and you will receive a Confirmation ID. Type this Confirmation ID into the prompt window to activate offline.
How do I switch from a MAK to a KMS deployment?
If your machine was mistakenly installed with a MAK and you want it to authenticate against your corporate KMS server, you must overwrite the MAK with the official LTSC 2024 Generic Volume License Key (GVLK). Run the input key command (/inpkey:GVLK-KEY) using the KMS client key published in Microsoft's deployment documentation, then run the activation command (/act). The software will automatically switch its licensing channel to KMS.
Will repairing the installation fix a blocked MAK key?
No. Repairing or reinstalling the software only resets local application files. A blocked Multiple Activation Key indicates that the total number of activations assigned to your organization's key has been exhausted on Microsoft's remote authentication servers. You must contact Microsoft Volume Licensing Support to request an increase to your MAK activation limit; local repairs will have no effect.




