Product Key Issues

Remove a Conflicting Microsoft Office License Key to Stop Activation Prompts

Khadija KhanKhadija Khan Nov 20, 2026 869 views

Question details

Identify and remove a conflicting Office product key that may be causing repeated activation prompts.

Product
Microsoft Office
Device & OS
Windows
Scenario
A preinstalled Microsoft 365 product remains registered alongside a volume-licensed Office installation.
Observed behavior
Office repeatedly requests activation.
Before you start

Confirm which Office license your organization intends to use and locate OSPP.vbs in the Office installation folder. You may need administrator access and help from your IT administrator to identify the conflicting key.

Solution 1Recommended

Identify and remove the conflicting Office product key

Use the Office Software Protection Platform script when a registered product key conflicts with the Office license you intend to use.

Remove only the key associated with the unwanted or error-producing license. Removing the valid key can deactivate the Office installation you want to keep.

1
Open an elevated command prompt

Open the Windows Start menu, search for Command Prompt, and select Run as administrator.

2
List registered Office licenses

Run cscript "C:\Program Files\Microsoft Office\Office16\OSPP.vbs" /dstatus. If the script is under Program Files (x86), use that path instead. Review the license descriptions, status, errors, and last five characters of each installed product key.

3
Verify the conflicting key

Compare the /dstatus results with the Office product and license your organization uses. If you cannot confidently identify the unwanted key, ask your IT administrator before continuing.

4
Remove the unwanted key

Run cscript "C:\Program Files\Microsoft Office\Office16\OSPP.vbs" /unpkey:XXXXX, replacing XXXXX with the last five characters of the unwanted key. Use the actual script path and do not put a space after /unpkey:.

5
Restart and check Office

Close and reopen an Office app, then check whether the activation prompt returns. If prompted, activate the intended Office license using your organization's instructions.

Identify and remove the conflicting Office product key
If OSPP.vbs is not found: The script location depends on the Office installation. Check the Office installation folders for OSPP.vbs, including Program Files (x86) for 32-bit Office on 64-bit Windows. If no applicable key appears, contact your IT administrator rather than removing a different key.
Free Microsoft Office alternative

Work on Office Documents Without Microsoft Office Activation

WPS Office is a free, lightweight alternative with a familiar interface for working on documents, spreadsheets, and presentations. Its Microsoft Office format support helps you move existing files into WPS, although it does not fix Microsoft Office licensing.

Open and edit documents without resolving a Microsoft Office activation conflictCompatible with Microsoft Office formats including DOCX, XLSX, and PPTXFamiliar editing interface for an easy transitionFree and lightweight office suite
microsoft office alternative - wps office

Frequently Asked Questions

How do I see which Office product keys are installed?

Open Command Prompt as administrator and run cscript "C:\Program Files\Microsoft Office\Office16\OSPP.vbs" /dstatus, adjusting the path if needed. The output shows license information and the last five characters of registered keys.

Which product key should I remove?

Remove only the key you have confirmed belongs to the unwanted or conflicting license. Compare the /dstatus output with your intended Office product, and consult your IT administrator if the results are unclear.

Why does the /unpkey command fail?

Check that OSPP.vbs is at the specified path, that Command Prompt was opened as administrator, and that there is no space between /unpkey: and the key's last five characters.

What if Office still asks for activation after I remove the key?

Restart the Office app and follow your organization's activation instructions for the intended license. If prompts persist or /dstatus does not identify a conflicting key, contact your IT administrator.