starred/Microsoft-Activation-Scripts
1
0
Fork 0
mirror of https://github.com/massgravel/Microsoft-Activation-Scripts.git synced 2026-04-26 06:25:49 +03:00
Code Issues 2 Projects Releases 10 Packages Wiki Activity

[GH-ISSUE #119] Office Online KMS - Hosts Removal #105

New issue
Closed
opened 2026-02-27 10:09:42 +03:00 by kerem · 2 comments
kerem commented 2026-02-27 10:09:42 +03:00
Owner
Copy link

Originally created by @crazyrabbit0 on GitHub (Jul 27, 2022).
Original GitHub issue: https://github.com/massgravel/Microsoft-Activation-Scripts/issues/119

Hi, first off all thanks for all your effort, your script is my favorite!

I have a proposal for Office Online KMS troubleshooting:

When a user has used a different Online KMS activation method (and thus added a KMS Host to the registry),
Online KMS takes a long time and eventually crashes with a generic error code: 0x80070005,
this usually happens when there are multiple KMS Hosts in the registry.

It is possible to fix this error by running this command in PowerShell:
Cscript "$env:WinDir\System32\Slmgr.vbs" /ckms
It essentially removes all KMS Hosts from the registry, so Online KMS can function properly.

Note: Offline KMS works fine regardless, because it doesn't try to add KMS Hosts to the registry.

Originally created by @crazyrabbit0 on GitHub (Jul 27, 2022). Original GitHub issue: https://github.com/massgravel/Microsoft-Activation-Scripts/issues/119 Hi, first off all thanks for all your effort, your script is my favorite! ### I have a proposal for Office Online KMS troubleshooting: When a user has used a different Online KMS activation method (and thus added a KMS Host to the registry), Online KMS takes a long time and eventually crashes with a generic error code: 0x80070005, this usually happens when there are multiple KMS Hosts in the registry. It is possible to fix this error by running this command in PowerShell: `Cscript "$env:WinDir\System32\Slmgr.vbs" /ckms` It essentially removes all KMS Hosts from the registry, so Online KMS can function properly. _**Note:** Offline KMS works fine regardless, because it doesn't try to add KMS Hosts to the registry._
kerem closed this issue 2026-02-27 10:09:42 +03:00
kerem commented 2026-02-27 10:09:43 +03:00
Author
Owner
Copy link

@crazyrabbit0 commented on GitHub (Jul 27, 2022):

I have reproduced this problem several times on many PCs to make sure it was this exact same problem!

I had tried every possible fix mentioned in Stack Overflow and the Microsoft Support Forums,
from simple time/date sync to Dism /RestoreHealth & SFC /ScanNow, as well as every troubleshooting tip in your homepage.

Until I stumbled upon this article from Microsoft, which described the cause for this error as:

The issue occurs when you cohost the Office 2013 KMS host and the Office 2016 KMS host on the same system, and that system is running either Windows 7 or Windows Server 2008 R2.

After reading this I thought that removing all KMS Hosts might fix the problem,
so I searched for the command I mentioned above, which indeed resolved this issue in every PC.

Every PC I tried this on, was running either Windows 10 or 11, not 7 as mentioned in the article
and running Office 2016 only (never had 2013- or 2019+), but they all used multiple KMS activators in the past.

That's why I came to the conclusion, that this was the real problem behind the scenes.

NOTE: I referred to the wrong error code above, it was actually: 0xC004F074.
NOTE 2: When I have free time, I will try to reproduce this error and use MAS 1.6 to see if it can fix it.

<!-- gh-comment-id:1196811952 --> @crazyrabbit0 commented on GitHub (Jul 27, 2022): I have reproduced this problem several times on many PCs to make sure it was this exact same problem! I had tried every possible fix mentioned in **Stack Overflow** and the **Microsoft Support Forums**, from simple time/date sync to `Dism /RestoreHealth & SFC /ScanNow`, as well as every troubleshooting tip in your homepage. Until I stumbled upon [this article](https://support.microsoft.com/en-us/topic/kms-error-0xc004f074-when-you-try-to-activate-office-2016-volume-licensed-client-89502352-f7eb-7dc2-559a-7aae7446efbf) from Microsoft, which described the cause for this error as: > The issue occurs when you cohost the Office 2013 KMS host and the Office 2016 KMS host on the same system, and that system is running either Windows 7 or Windows Server 2008 R2. After reading this I thought that removing all KMS Hosts might fix the problem, so I searched for the command I mentioned above, which indeed resolved this issue in every PC. Every PC I tried this on, was running either **Windows 10** or **11**, not 7 as mentioned in the article and running **Office 2016 only** (never had 2013- or 2019+), but they all used multiple KMS activators in the past. That's why I came to the conclusion, that this was the real problem behind the scenes. _**NOTE:** I referred to the wrong error code above, it was actually: **0xC004F074**._ _**NOTE 2:** When I have free time, I will try to reproduce this error and use MAS 1.6 to see if it can fix it._
kerem commented 2026-02-27 10:09:43 +03:00
Author
Owner
Copy link

@a-1an commented on GitHub (Aug 5, 2022):

Some of the terms used here are incorrect but I do get your point that in some cases when another KMS activator is used and later MAS online KMS option is used then it gets stuck.

The issue was not related to KMS host but added rules for SppExtComObj.exe and sppsvc.exe in IFEO registry entry.

MAS 1.6 solves this issue. Please let me know if you can reproduce this error with MAS 1.6

MAS 1.6 didn't work for me and I did the fix crazyrabbit0 suggested and it worked.

<!-- gh-comment-id:1206359209 --> @a-1an commented on GitHub (Aug 5, 2022): > Some of the terms used here are incorrect but I do get your point that in some cases when another KMS activator is used and later MAS online KMS option is used then it gets stuck. > > The issue was not related to KMS host but added rules for SppExtComObj.exe and sppsvc.exe in IFEO registry entry. > > MAS 1.6 solves this issue. Please let me know if you can reproduce this error with MAS 1.6 MAS 1.6 didn't work for me and I did the fix [crazyrabbit0](https://github.com/crazyrabbit0) suggested and it worked.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
dev
3.10
3.9
3.8
3.7
3.6
3.5
3.4
3.3
3.2
3.1
3.0
2.9
2.8
2.7
2.6
2.5
2.4
2.3
2.2
2.1
2.0
1.9
1.8
1.7
1.6
1.5
1.4
1.3
1.2
Labels
Clear labels   
pull-request

Mirrored from GitHub Pull Request

No labels
pull-request
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Microsoft-Activation-Scripts#105
No description provided.