- Edited by Field Commander A9 Friday, May 22, 2015 1:42 AM
product key always change to -mkkg7 during upgrade and fails to activate
Everytime I update to a new Windows 10 Ent x64 preview build, Windows's product keys gets changed to *-mkkg7, and then windows fails to activate with a "dns name not found" error. I have to manually enter the correct cdkey everytime.
May 21st, 2015 5:58am
Everytime I install a new Windows 10 Ent x64 preview build, Windows's product keys gets changed to *-mkkg7, and then windows fails to activate with a "dns name not found" error. I have to manually enter the correct cdkey everytime.
Hi
Are you trying to install the insider preview? How did you install and activate the system? The product key is
VTNMT-2FMYP-QCY43-QR9VK-WTVCK, the key is not required for the installation, but maybe needed for recovery scenarios.
https://www.microsoft.com/en-us/evalcenter/evaluate-windows-enterprise-insider-preview
Regards
Free Windows Admin Tool Kit Click here and download it now
May 22nd, 2015 1:36am
Everytime I install a new Windows 10 Ent x64 preview build, Windows's product keys gets changed to *-mkkg7, and then windows fails to activate with a "dns name not found" error. I have to manually enter the correct cdkey everytime.Hi
Are you trying to install the insider preview? How did you install and activate the system? The product key is
VTNMT-2FMYP-QCY43-QR9VK-WTVCK, the key is not required for the installation, but maybe needed for recovery scenarios.
https://www.microsoft.com/en-us/evalcenter/evaluate-windows-enterprise-insider-preview
R
May 22nd, 2015 1:42am
I'm on Enterprise Edition too. It did not matter if it was an upgrade or a clean install, I've always needed to re-enter the Product Key to get my Windows 10 to activate. The key listed is for Build 10074 and later. I can only assume this problem will
go away once Windows 10 goes to RTM. If you think this is a bug, you should be reporting it using your Windows Feedback App found in Windows 10.
Free Windows Admin Tool Kit Click here and download it now
May 22nd, 2015 2:01am
I'm on Enterprise Edition too. It did not matter if it was an upgrade or a clean install, I've always needed to re-enter the Product Key to get my Windows 10 to activate. The key listed is for Build 10074 and later. I can only assume this problem will go away once Windows 10 goes to RTM. If you think this is a bug, you should be reporting it using your Windows Feedback App found in Windows 10.No it isn't. I've got enterprise preview installed on 2 seperate PCs and this bug only happens on 1 of them, the other always activates automatically after update.
May 22nd, 2015 2:09am
That's interesting, maybe it's a part of the A and B testing Microsoft is doing would be my next guess. I've seen posts where people never had to input the product key more than once, then there are people like me that had to input it each time a new build
comes out. You have two computers doing one of each. I know Microsoft has been experimenting with blur effects vs. transparencies on the desktop and with different log-on methods to access your computer. Could this just be another part of the testing process
Microsoft is doing?
Free Windows Admin Tool Kit Click here and download it now
May 25th, 2015 2:35am
I'd say somthing so important(to make their lawyers happy) as the activation machenism is very unlikely to be A-B tested this late in the develop cycle.
- Edited by Field Commander A9 Monday, May 25, 2015 2:42 AM
May 25th, 2015 2:41am
Hi,
Here's a helpful link:
Press Windows key + R
Type: slui.exe 3
Hit Enter
Enter the product key and click Next to activate over the Internet. Check the result.
Regards
Free Windows Admin Tool Kit Click here and download it now
May 28th, 2015 9:31am
I think you'll find that the -MKKG7 key is the Generic Volume License Key (GVLK) for Windows 8.1 Enterprise that's published by Microsoft; in Windows products that's the key that's installed by default unless the user explicitly provides a different key. With that key installed your Windows 10 Preview installation is eligible for both KMS and TBA activation that's configured for Windows 8.1 Enterprise, which I suspect is the reason that Microsoft used the 8.1 key. I'll hazard a guess that the "dns name not found" error message is the result of the KMS code trying to find a KMS server.
Of course, unless someone's asleep at the switch there will be a new GVLK for the production version of Windows 10.
Data point: my installations have been cheerfully activated by the corporate KMS; I've never been asked for a product key.
Why that happens on one machine but not another is interesting. By any chance is one of the systems from a royalty OEM (Dell, Lenovo, HP, etc.) and the other from a screwdriver shop/homebuilt/brand-X vendor? Or is one of the systems a repurposed server? Differences in the BIOS might be messing with the activation logic.
June 1st, 2015 4:58pm
For the record, I'm testing on a home built machine and needing to re-enter the key each time a new build comes out.
Free Windows Admin Tool Kit Click here and download it now
June 1st, 2015 5:16pm
Why that happens on one machine but not another is interesting. By any chance is one of the systems from a royalty OEM (Dell, Lenovo, HP, etc.) and the other from a screwdriver shop/homebuilt/brand-X vendor? Or is one of the systems a repurposed server? Differences in the BIOS might be messing with the activation
June 2nd, 2015 2:59am
This one worked for me. Thanks!
Free Windows Admin Tool Kit Click here and download it now
June 28th, 2015 2:03am
This topic is archived. No further replies will be accepted.
Other recent topics
