License Install Failed For License Type: 1 Result Code: 0xc03f6601 'link'

Troubleshooting Guide: License Install Failed (Error 0xc03f6601)

Applies to: Microsoft Office (2016, 2019, 2021, Microsoft 365), Windows 10/11

If you’ve recently tried to activate Microsoft Office and encountered the error message:

“License install failed for license type: 1 result code: 0xc03f6601”

you’re not alone. This cryptic error typically appears during the licensing or activation phase, often after reinstalling Windows, resetting your PC, or making significant hardware changes. Below, we break down what this error means and how to fix it.

Method 5: Clean Boot Installation

Conflicting software is a known cause of 0xc03f6601. “License install failed for license type: 1 result

1. Press Win + R, type msconfig, press Enter.
2. Go to the Services tab, check "Hide all Microsoft services" , then click "Disable all" .
3. Go to the Startup tab, click "Open Task Manager" , and disable all startup items.
4. Restart your PC.
5. Uninstall Office completely (using Method 1) and reinstall.
6. Once activation succeeds, go back to msconfig and re-enable services/startup items.

2. Clear and reinstall the license

slmgr /upk
slmgr /cpky
slmgr /rearm

Restart PC, then try installing your license again.

Step 3: Convert from KMS Client to Volume/Multiple Activation Key (MAK)

If your system was previously activated via KMS (Key Management Service) and you are trying to use a MAK or Retail key, you must first clear the KMS client settings.

Run this command to remove the KMS product key:

slmgr /upk

Then, run this to clear the remaining KMS license information from the registry: you’re not alone

slmgr /ckms

Now, try installing your new license again:

slmgr /ipk Your-New-Product-Key

Fix: "License install failed for license type: 1 result code: 0xc03f6601"

Encountering the error "License install failed for license type: 1 result code: 0xc03f6601" is a common yet frustrating roadblock when attempting to activate Microsoft products, particularly Windows Server (especially RDS CALs) or certain Volume Licensing editions of Windows 10/11.

This error typically indicates a mismatch between the license you are trying to install and the edition of the operating system or the licensing role currently configured.

Method 4: Check for User Account Control (UAC) or Group Policy Issues

In corporate environments, this error often appears due to an overzealous Group Policy. The Facade: In generic Win32 terms

• For home users: Ensure UAC is set to default (reg query HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System). Set EnableLUA to 1.
• For enterprise users: Contact your IT admin to check if the "Allow Office to activate over the internet" policy is enabled. Also, ensure the Software Protection Service isn't blocked by Windows Firewall (Rule name: Software Protection Platform).

C. Transitioning from Volume to Retail

If your system previously had a Volume License (KMS or MAK) installed—common in corporate environments or evaluation versions—and you attempt to install a standard Retail key without properly uninstalling the Volume License, the remnants of the old licensing ticket can conflict with the new one.

1. Technical Deconstruction of the Error

To understand the failure, we must first deconstruct the components of the error string.

A. "License Type: 1" In the context of Windows Licensing, the "License Type" integer corresponds to the method of activation.

• Type 1: Represents a Retail License in some contexts, but in the context of server failures involving this specific hex code, it most often refers to the inability to validate a Volume License (Volume Multiple Activation Key - MAK) or a KMS client setup key.
• Anomaly: Frequently, users installing Volume licenses will see "Type 5" (Volume). Seeing "Type 1" can sometimes indicate the OS expects a Retail channel key but is receiving a Volume key, or vice versa, causing a channel mismatch.

B. "Result Code: 0xc03f6601" This is the NTSTATUS error code, which is the critical diagnostic component.

• The Facade: In generic Win32 terms, this code often translates to a generic "File not found" or "Element not found."
• The Technical Reality: In the context of sppsvc (Software Protection Service), 0xc03f6601 is mapped to a failure in accessing or writing to the Token Store (Licensing Store).
• The Hidden Meaning: This error is notoriously linked to Permission Issues on the %SystemRoot%\System32\spp directory, or more specifically, corruption within the registry keys governing the licensing policies.