Microsoft Activation Issue

Question

I have a base image and I use OEM for Windows 10 IOT Enterprise and prod image use that key which provided by OEM. But lastly we can not get a confirmation microsoft support, error says Unfortunately, we can’t complete the process because our records do not recognize this as a valid product.

You may be able to return the software to your seller. To learn more about your Microsoft product’s license rights, please visit microsoft.com/howtotell.

Alternatively, if your device meets the minimum requirements, you may consider purchasing a newer version of the software from store.microsoft.com.

You can now close this window.” Than I checked the prod image and I saw different partial product key first one belongs to base image and second one unknown key. In prod image side and base image side nothing changed and before we use almost a one year same process but last 2 months we struggle with this issue.

Answer 1

Hello again Melisa Temur,

Just following up. The error message confirms that the Product Key used in your base image has been invalidated by the Microsoft Activation Clearinghouse, likely due to the activation count exceeding the allowable threshold for that specific ePKEA (Embedded Product Key Entry Activation) or MAK string. This exhaustion explains the sudden failure after a year of successful deployments.

Regarding the "unknown" key you observed, it is critical to understand that running sysprep /generalize strips specific system information, including the installed product key, to create a hardware-independent image. If the subsequent automated re-insertion of your OEM key fails during the Specialize or OOBE configuration pass because the Microsoft servers reject it, the OS reverts to the default generic installation key for the Windows 10 IoT Enterprise SKU. This generic key is a placeholder used solely for installation and cannot be used for activation, which is why you see a mismatch compared to your base image. The system has not necessarily fallen back to a GVLK (Volume License) unless your source media was incorrect; rather, it is simply sitting in an unlicensed state with the generic SKU key.

To prescribe the exact fix, I need to verify the current licensing channel of the failing unit to ensure the image hasn't been corrupted. Please open Command Prompt as Administrator, run slmgr /dlv, and report the specific "Description" line (e.g., "Windows(R) Operating System, OEM_DM channel" or "OEM_COA_NSLP") and the "Partial Product Key". Do not post the full key. In the interim, you must contact your authorized Microsoft Distributor immediately; since the key is flagged server-side, no local troubleshooting steps will resolve this, and you will need a new key issuance or a "High Assurance" unlock if you are the direct OEM partner.

Hope you found something useful in the answer. If it helped you get more insight into the issue, please consider accepting the answer. Thank you.

VP

Answer 2

Hello Melisa Temur

The error explicitly indicates that the Microsoft Clearinghouse has blacklisted the injected Product Key. For Windows 10 IoT Enterprise, OEMs utilize either an Embedded Product Key Entry Activation (ePKEA) for disconnected environments or a Product Key Entry Activation (PKEA) which relies on standard Multiple Activation Key (MAK) thresholds. When a PKEA exceeds its activation limit or an ePKEA is flagged for unauthorized distribution, the activation servers reject the PID. Consequently, the Software Protection Platform service automatically falls back to the default Generic Volume License Key (GVLK) for IoT Enterprise, which explains the appearance of the second, unknown partial key in your production image. No local registry modifications or sysprep configurations will override a server-level key block. You must contact your authorized Microsoft OEM Distributor to validate the key status and request a replacement.

The optimal method is injecting the key directly into the ACPI MSDM table using the OA 3.0 Tool (oa3tool.exe) or defining it within the Microsoft-Windows-Setup component under the UserData node during the windowsPE configuration pass. To provide the most accurate guidance for restructuring your deployment process once you receive the new key, I need more specifics regarding your current topology. Please clarify whether your OEM licensing agreement specifies the use of ePKEA, PKEA, or OA 3.0. Furthermore, please execute slmgr.vbs /dlv on the affected production image and specify whether the Description field indicates the channel as OEM:NONSLP, OEM:DM, or Volume:MAK.

Do you find this answer useful? Should you have more questions, feel free to leave a comment. If the answer helps you get more insight into the issue, please consider accepting it. Thank you and have a nice day!

VP

Answer 3

It seems that the issue you are experiencing with the OEM activation key for Windows 10 IoT Enterprise may be related to a mismatch between the product key used in your production image and the key expected by Microsoft. Here are some steps you can take to troubleshoot this issue:

1. Verify Product Key: Ensure that the product key you are using in the production image matches the OEM key provided for Windows 10 IoT Enterprise. You can check the key in the firmware of the device as it may be different from what is displayed in the system.
2. Use the Correct Tools: Instead of relying on slmgr /dli or slmgr /dlv, consider using the OA3Tool to validate the product key against the installed Windows edition. This tool can help confirm that the Digital Product Key (DPK) is correctly injected and recognized.
   • Run OA3TOOL /Validate to check the MSDM table and ensure it complies with the required formats.
   • Use OA3TOOL /CheckEdition to cross-check the injected DPK with the target Windows edition.
3. Check for Changes: Since you mentioned that this process has worked for almost a year, consider any recent changes in your environment or updates that may have affected the activation process. It might be worth checking if there have been any updates to the Windows version or the OEM activation process.
4. Contact Microsoft Support: If the issue persists, it may be necessary to reach out to Microsoft support for further assistance. They can provide specific guidance based on your situation and the error messages you are encountering.
5. Consider Reinstallation: If all else fails, you might need to consider reinstalling the operating system using the correct media that matches the OEM key to avoid mismatches.

By following these steps, you should be able to identify the cause of the activation issue and take appropriate action to resolve it.