search

Wind4 / vlmcsd

KMS Emulator in C (currently runs on Linux including Android, FreeBSD, Solaris, Minix, Mac OS, iOS, Windows with or without Cygwin)
https://forums.mydigitallife.net/threads/50234
8.35k stars 2.23k forks source link

0x87E10BC6 when running slmgr -ato #37

Closed smaitlx closed 4 years ago

smaitlx commented 4 years ago

Attempting to activate Windows Server 2019 Datacenter initially succeeds but during subsequent attempts to activate will return 0x87E10BC6. Additionally, the "Activate Windows" watermark appears in the lower right.

smaitlx commented 4 years ago

Additional testing.... Windows 10 Enterprise Build 1909 works as expected.

Running slui 0x2a 0x87e10bc6 as indicated by slmgr -ato returns the following: Code: 0x87E10BC6 Description: Unablemto find a detailed error description. Unknown facility code 0x7E1 (2017L) Facility error: 0xBC6 (3014L)

smaitlx commented 4 years ago

The Settings panel on the affected OS shows:

Edition: Windows Server 2019 Datacenter Activation: Windows is not activated Product ID: 00430-70000-00001-AA496 Product Key: CPR8F

We can't activate Windows on this device right now. You can try activating again later or go to the Store to buy genuine Windows.

Error code: 0xC004F025

smaitlx commented 4 years ago

Doing some additional testing, but running the following command seems to have fixed it:

slmgr /ipk [KMS client setup key]

To get the KMS client setup key, go to https://docs.microsoft.com/en-us/windows-server/get-started/kmsclientkeys

The command replaces the internal key within Windows with the key supplied after /ipk. Going to do a reboot and see if the /ato still returns an error. If this fixed it, it suggests that the affected OS somehow didn't have the correct key for KMS client functionality.

smaitlx commented 4 years ago

Rebooted and the issue seems to still be resolved. I believe the root cause was within Windows and not a bug. I will update if that changes.