-
×InformationWindows update impacting certain printer icons and names. Microsoft is working on a solution.
Click here to learn moreInformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center.
-
×InformationWindows update impacting certain printer icons and names. Microsoft is working on a solution.
Click here to learn moreInformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center.
- HP Community
- Desktops
- Business PCs, Workstations and Point of Sale Systems
- Re: T620 thin client not able to activate Win 10 IoT
Create an account on the HP Community to personalize your profile and ask a question
12-23-2019 11:36 PM - edited 12-23-2019 11:38 PM
Hi everyone,
I've got some HP T620's and they have got Windows 7 embedded installed standard. I'm using HP Device Manager for new images and when I install Windows 10 IoT on the thin client, I can't activate Windows 10 IoT on them.
I configured a T620 manually and installed Windows 10 IoT, configured settings and captured an image with HP Device Manager so I can send tasks with this image to other thin client.
The error: "We can't activate Windows on this device because the product key was already user on another device. If you think it wasn't user on another device, select Troubleshoot below. Error code: 0xC004C008."
Selecting Troubleshoot gives me the message: "Unable to activate Windows. We can't activate your copy of Windows. Make syre you're connect to the internet and try again."
Before I never had problems with imaging HP thin client by HP Device Manager.
Does that sound familiar to someone or does anyone knows what to do?
Many thanks for your reply.
Best regards,
Rick
Solved! Go to Solution.
Accepted Solutions
01-08-2020 05:49 AM
I've entered another Windows Key from KMS and the issue was gone. I did a capture from that machine and now it works when I image other thin clients via HPDM.
Thanks for your reply., MayRob2.
01-08-2020 05:16 AM
I had a similar issue on t630 with Win10 IoT 2016. Both units had the same hostname so I did a hostname change with a reimage via HPDM and the issue was gone.
On another circumstance the Windows Key was showing a wrong key in the Windows Activation dialog but when using wmic it provided the correct one that could be entered and then it activated correctly:
At the command prompt, type: wmic path SoftwareLicensingService get OA3xOriginalProductKey. This will reveal the correct product key.
Didn't find what you were looking for? Ask the community