I am having issues activating Windows 10 ESU license on VMware workstation 16 VMs

Check the following areas that commonly block Windows 10 ESU activation and cause generic portal errors like “Something’s wrong,” especially on VMs:

1. Confirm ESU prerequisites inside the VM
   ESU activation will fail if the required updates are missing or pending reboot.
   • In the VM, open Settings > Update & Security > Windows Update > View update history and verify that all ESU prerequisite updates and the licensing monthly rollup/security-only/standalone package are installed successfully.
   • If any ESU prerequisite was just installed, restart the VM and try activation again.
   • If the ESU key was installed with slmgr.vbs /ipk and you see error 0xC004F050 (“The Software Licensing Service reported that the product key is invalid”), this usually means either the ESU licensing update is missing or the VM has not been restarted after installing prerequisites.
2. Verify the correct ESU key and edition in the VM
   • Make sure the ESU key being used matches Windows 10 Enterprise and the specific ESU program year purchased.
   • If the key does not match the OS edition in the VM, activation will fail with “product key is invalid” errors.
3. Check network connectivity from the VM to Microsoft activation services
   If the VM cannot reach the activation service, the portal or in-OS activation can fail with generic messages or errors like 0x80072EE2 or 0x80072EE7:
   • Ensure the VM has working internet access.
   • If using a firewall or proxy (host or guest), allow the ESU activation endpoints used by VAMT/online activation:
     • https://activation.sls.microsoft.com/BatchActivation/BatchActivation.asmx
     • https://go.microsoft.com/fwlink/?LinkId=82160 (redirects to the previous URL)
     • Or allow the domains: activation.sls.microsoft.com and go.microsoft.com.
   • If the VM cannot have direct internet access, use VAMT proxy activation or phone activation as alternatives, as described in the ESU guidance.
4. If using VAMT for ESU activation on the VM
   • If VAMT reports that the ESU product key is invalid when adding it or applying it to the VM, update VAMT’s configuration files:
     1. Download the updated VAMT files (includes pkconfig_win7.xrm-ms and pkconfig_vista.xrm-ms).
     2. Copy them into C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\VAMT3\pkconfig, replacing the existing files.
     3. Close and restart VAMT, then re-add and reapply the ESU key to the VM.
   • If VAMT shows “Unable to verify product key” or “The Software Licensing Service reports that the product key is invalid” when targeting the VM, this typically indicates missing ESU prerequisite updates inside that VM; install them, reboot, and retry.
5. Run ESU activation explicitly with the activation ID (inside the VM)
   If the ESU key appears installed but the VM still shows License Status: Unlicensed:
   • Run slmgr /ato <Activation ID> inside the VM, where <Activation ID> is the ESU activation ID for the installed ESU key.
   • This ensures the ESU activation is targeted correctly rather than only the base Windows license.
6. If errors persist
   • If slmgr.vbs /ipk still returns 0xC004F050 after confirming prerequisites and rebooting, collect C:\Windows\Logs\CBS\CBS.log from the VM and contact Microsoft Support for deeper analysis.
   • If using VAMT and seeing TLS or connection errors when acquiring confirmation IDs, ensure TLS 1.2 is enabled for .NET 4.x on the VAMT host (not the VM) using the documented registry settings, then retry the proxy activation workflow.

These checks apply equally to Windows 10 Enterprise running on VMware Workstation VMs; ESU activation logic is the same as on physical hardware, so focus on prerequisites, correct key/edition, and network or VAMT configuration.

References:

• Troubleshoot issues in ESU
• Cannot perform Win10 ESU Offline Activation using Proxy Scenario 2 activation - Microsoft Q&A
• Extended Security Updates (ESU) Slovenia Win10 - Microsoft Q&A
• ESU Enrol not yet showing on one device - Microsoft Q&A