• Proposed as answer by Sam Boutros Thursday, October 02, 2014 8:32 PM

• Proposed as answer by Sam Boutros Thursday, October 02, 2014 8:32 PM

I believe there is a bug when you do an inplace upgrade with the technical preview for enterprise.

I had a similar issue. It was supposed to install pre activated but did not. Fix is as follows:

1. Open Administrative command prompt (Windows key+x > A)

2. Type: SLUI 3

3. Enter the product key Microsoft provided for recovery scenarios: PBHCJ-Q2NYD-2PX34-T2TD6-233PK

• Proposed as answer by JonRohrich Thursday, October 02, 2014 8:40 PM
• Unproposed as answer by JonRohrich Thursday, October 02, 2014 8:40 PM
• Proposed as answer by JonRohrich Friday, October 03, 2014 12:01 AM
• Marked as answer by Carey FrischMVP, Moderator Thursday, October 23, 2014 5:16 AM

I believe there is a bug when you do an inplace upgrade with the technical preview for enterprise.

I had a similar issue. It was supposed to install pre activated but did not. Fix is as follows:

1. Open Administrative command prompt (Windows key+x > A)

2. Type: SLUI 3

3. Enter the product key Microsoft provided for recovery scenarios: PBHCJ-Q2NYD-2PX34-T2TD6-233PK

• Proposed as answer by JonRohrich Thursday, October 02, 2014 8:40 PM
• Unproposed as answer by JonRohrich Thursday, October 02, 2014 8:40 PM
• Proposed as answer by JonRohrich Friday, October 03, 2014 12:01 AM
• Marked as answer by Carey FrischMVP, Moderator Thursday, October 23, 2014 5:16 AM

I used slmgr.vbs to license mine, as both Enterprise copies have tried to retain their KMS connections.

Win-X, Command Prompt (Admin) or Windows PowerShell (Admin). It will launch to your System32 folder.

cscript slmgr.vbs -ipk PBHCJ-Q2NYD-2PX34-T2TD6-233PK

Wait 1-3 minutes.

cscript slmgr.vbs -ato

Should says that you're activated now.

• Edited by Maymne Thursday, October 02, 2014 11:10 PM Put the actual code in
• Proposed as answer by Maymne Friday, October 03, 2014 7:00 PM

I used slmgr.vbs to license mine, as both Enterprise copies have tried to retain their KMS connections.

Win-X, Command Prompt (Admin) or Windows PowerShell (Admin). It will launch to your System32 folder.

cscript slmgr.vbs -ipk PBHCJ-Q2NYD-2PX34-T2TD6-233PK

Wait 1-3 minutes.

cscript slmgr.vbs -ato

Should says that you're activated now.

• Edited by Maymne Thursday, October 02, 2014 11:10 PM Put the actual code in
• Proposed as answer by Maymne Friday, October 03, 2014 7:00 PM

I used slmgr.vbs to license mine, as both Enterprise copies have tried to retain their KMS connections.

Win-X, Command Prompt (Admin) or Windows PowerShell (Admin). It will launch to your System32 folder.

cscript slmgr.vbs -ipk PBHCJ-Q2NYD-2PX34-T2TD6-233PK

Wait 1-3 minutes.

cscript slmgr.vbs -ato

Should says that you're activated now.

  Indeed. Enterprise is designed for large networks. It uses KMS by default. Windows 8.1 Enterprise was the same.

Hello,

I would like to see some setup logs where the key was not accepted.

Can the setup logs from the \windows\panther folder be made available for download if you saw this failure?

this worked for me, as earlier posted by JonRohrich

1. Open Administrative command prompt (Windows key+x > A)

2. Type: SLUI 3

3. Enter the product key Microsoft provided for recovery scenarios: PBHCJ-Q2NYD-2PX34-T2TD6-233PK

When I did it, I did an in place upgrade from Windows 8.1 Enterprise. I originally upgraded to the regular tech preview but realized my mistake (when I saw no direct access) and upgraded to the enterprise tech preview. Activation didn't tell me it failed, I just noticed the watermark on the screen saying "activate windows".

Logs: https://onedrive.live.com/redir?resid=63C9BF981B802977!65017&authkey=!AJ9Pa7GvWlqKcLM&ithint=folder%2clog

Hello,

I would like to see some setup logs where the key was not accepted.

Can the setup logs from the \windows\panther folder be made available for download if you saw this fa

Hi Darrell, I'm getting what looks like this error, but the solution provided on this thread doesn't work. In the UI, the error message is "That key can't be used to activate this edition of windows", and that's for both the enterprise and consumer keys that I've been able to find. (NKJFK-GPHP7-G8C3J-P6JXR-HQRJR and PBHCJ-Q2NYD-2PX34-T2TD6-233PK)

For a while yesterday, I think I was seeing an error along the lines of "the activation server has rejected that key", but can't replicate that now.

The SKU I'm using is English (United Kingdom) 64-bit, and it was a clean install. I can email you my setup logs if you're interested, just let me know which files you need.

Cheers,
Mike

• Proposed as answer by shanna_jane Saturday, March 14, 2015 9:40 PM

• Proposed as answer by shanna_jane Saturday, March 14, 2015 9:40 PM

FWIW, the activation server error is actually present on the Activate Windows window, so probably relates to the pre-installed product key ending in D3VPT:

I faced the same issue where Windows 10 refused to accept the product key published by Microsoft but using the recovery key mentioned here did the magic :)

thanks a lot!

I already store ,so how I can do?

I restore ad ,so how I gonna do?

Thanks, 

This was the ticket!

Casey A.

this is the activation key required

6P99N-YF42M-TPGBG-9VMJP-YKHCF

this is the activation key required

6P99N-YF42M-TPGBG-9VMJP-YKHCF