Windows License Activation Failed

  

Aug 20, 2011  Let’s try to temporarily disable Windows Firewall and Kaspersky Antivirus program. After that, perform a Clean Boot for activation. For the detailed steps of how to enter into Clean Boot, please refer to the following Microsoft KB article: How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7. A dialog box should now display titled 'Windows Activation'. Enter your server product key there, and you should then be able to activate windows from that dialog. Use Software Licensing Manager Tool: Run 'Command Prompt' using 'Run as administrator'. In the command prompt box enter: slmgr -upk and press return. You should then see a box titled.

We have added a couple of Windows Server 2016 installs, and I have added Volume Activation Services configured for KMS type activation to one of them and installed our Server 2016 KMS key. With the services installed, I activated the firewall rule for KMS (port 1688) and verified that the 'VLMCS' entry was added to DNS. Windows Activation fails. If you have tried to enter your license key and activate it over the Internet, during installation or later by bringing up SLUI.EXE 3 and failed, you have another option and that is to activate Windows 8 using the telephone. To do so, type SLUI.EXE 4 in search bar and hit Enter to open the following dialog box.

License

Discus and support Windows 10 Pro activation failed Error code: 0xC004F025 in Windows 10 Updates and Activation to solve the problem; Hello, I'm new here and hope not to break some rules. Мy problem is the following, I bought a Dell laptop and I'm trying to activate Windows Pro 10... Discussion in 'Windows 10 Updates and Activation' started by BobbyTrade, Jun 25, 2019.

Event Id 4103 Windows License Activation Failed

Aug 27, 2015  If your Windows 10/8/7 activation fails, when you tried to activate your copy of Windows over the Internet, with errors 0x80004005, 0x8004FE33. For activation issues involving Windows Server 2016 VMs failing to activate despite having the KMS client setup key configured, or for activation issues with Azure VMs using other versions of Windows, please review the remaining steps below. Windows activation or validation fails when you try to activate Windows operating systems over the Internet.

Thema:

Windows 10 Pro activation failed Error code: 0xC004F025

  1. Windows 10 Pro activation failed Error code: 0xC004F025 - Similar Threads - Pro activation failed

  2. Re-activating Windows 10 Error code: 0xC004F025

    in Windows 10 Updates and Activation
    Re-activating Windows 10 Error code: 0xC004F025: I upgraded my motherboard and CPU, and now apparently my Windows 10 is no longer 'active'. I had Windows 7 on the PC originally, did a free upgrade to Windows 10 way back. I don't know what my original Windows 7 product key was, and it only shows the last 5 digits of my...

  3. Error code 0xc004F025

    in Windows 10 Updates and Activation
    Error code 0xc004F025: Just upgraded my whole computer but using my same hardrive.. I have windows 10 but it won't activate because of error code.https://answers.microsoft.com/en-us/windows/forum/all/error-code-0xc004f025/2f22869d-4a04-43cb-a94c-f9137ea2b1c2'

  4. Windows 10 Home activation error code: 0xC004F025

    in Windows 10 Updates and Activation
    Windows 10 Home activation error code: 0xC004F025: I took the hard drive out of my Toshiba laptop which the motherboard had failed and placed it into another Toshiba of mine both having had OEM versions of windows 7 and the windows 10 was a free upgrade. selecting the troubleshoot option, and then the I have made hardware...

  5. Windows 10 Activation Error Code: 0xC004F025

    in Windows 10 Updates and Activation
    Windows 10 Activation Error Code: 0xC004F025: So I'm having issues with activating Windows 10 at the moment. I had it running on my old rig but recently built a new one. I bought Windows 10 Home back in 2018. [img]At least it should be the Home version. However right now it's showing as Windows 10 Enterprise. I don't...

  6. Windows 10 Activation Error Code: 0xC004F025

    in Windows 10 Support
    Windows 10 Activation Error Code: 0xC004F025: So I'm having issues with activating Windows 10 at the moment. I had it running on my old rig but recently built a new one. I bought Windows 10 Home back in 2018. [img]At least it should be the Home version. However right now it's showing as Windows 10 Enterprise. I don't...

  7. Windows activation after hardware change error code 0XC004F025

    in Windows 10 Updates and Activation
    Windows activation after hardware change error code 0XC004F025: I built a new PC and put my HDD from my previous computer in which contained my copy of Windows 10 Home.Here's the info from slmgr.vbs /dlv[ATTACH]I've tried running the troubleshooter in the activation section in Settings but once I click on the option 'I have...

  8. Windows 10 Pro activation failed Error code: 0xC004F025

    in Windows 10 Updates and Activation
    Windows 10 Pro activation failed Error code: 0xC004F025: Windows 10 Pro activation failed Error code: 0xC004F025https://answers.microsoft.com/en-us/windows/forum/all/windows-10-pro-activation-failed-error-code/1211a8c3-f1d6-433c-a4cd-c7a259f84468'

  9. i can't activate my windows error code 0xC004F025

    in Windows 10 Customization
    i can't activate my windows error code 0xC004F025: im trying to use solution 2 type my pc key on change product key but I upgrade when windows was free so that why I don't know my key help me...

  10. Can't Activate My Windows 10 Error Code: 0xC004F025

    in Windows 10 Customization
    Can't Activate My Windows 10 Error Code: 0xC004F025: I'm trying to activate my Windows 10 Pro but I keep getting this Error Code: 0xC004F025 after like 15min loading, when I click on, activate button and I think due to this problem my windows defender is not working too. Can anyone resolve my issue here....

  1. 0xc004f025

    ,

  2. 0xc004f025 activation windows 10

    ,

  3. windows error code 0xc004f025

    ,
  4. 0xc004f025 windows 10,
  5. error code 0xc004f025,
  6. windows activation error 0xc004f025,
  7. 0xc004f025 windows 10 activation error,
  8. c004f025,
  9. error 0xc004f025,
  10. error 0xc004f025 windows 10,
  11. windows 10 activation error 0xc004f025,
  12. windows 10 0xc004f025,
  13. windows error 0xC004F025,
  14. error code 0xc004f025 windows 10,
  15. windows activation 0xc004f025

Windows License Activation Failed. Error 0x80070005

Azure uses the following KMS endpoints for Windows product activation of Azure Virtual Machines:

  • Azure public cloud regions - kms.core.windows.net:1688
  • Azure China national cloud regions - kms.core.chinacloudapi.cn:1688
  • Azure Germany national cloud regions - kms.core.cloudapi.de:1688
  • Azure US Gov national cloud regions - kms.core.usgovcloudapi.net:1688

Azure VMs will activate using the Azure KMS service if all of the following are true:

  1. Windows is configured with the appropriate KMS client setup key for that version of Windows.
  2. Windows is configured to use the Azure KMS service, e.g. kms.core.windows.net:1688 for VMs in Azure public cloud regions.
  3. VM has network connectivity to the KMS endpoint, e.g. kms.core.windows.net:1688 for VMs in Azure public cloud regions. For example, if the guest OS firewall or an Azure network security group (NSG) rule does not allow TCP port 1688 outbound, the activation request will be blocked.
  4. Source IP address of KMS activation requests from the VM must be an IP address within the Azure IP ranges. This is necessary because the Azure KMS service only allow requests through if the source IP is within the Azure IP ranges. If you are using ExpressRoute, please see Azure VM may fail to activate over ExpressRoute. If you are using site-to-site VPN please see Use Azure custom routes to enable KMS activation with forced tunneling.

Windows activation works the same way regardless if the VM is using Azure Hybrid Use Benefit (HUB) or not.

Note that while using an Automatic Virtual Machine Activation (AVMA) key may work on some Azure VMs, the use of AVMA keys is not supported because not all Azure hosts are guaranteed to support it. So while it may work initially, when the VM moves to a different Azure host when deallocated and started, when the Redeploy option is used, or when planned maintenance occurs, it may end up on an Azure host that does not support AVMA.

Run slmgr.vbs /dlv from within the VM to check #1 and #2 above. In the example below, VOLUME_KMSCLIENT is what tells you a KMS client setup key was used, and Registered KMS machine name: kms.core.windows.net:1688 is what confirms that it is configured to activate against the Azure KMS service. Note that the KMS endpoint differs for public versus national cloud regions as listed at the beginning of this article.

If slmgr.vbs /dlv shows RETAIL channel, run the following commands to set the KMS client setup key for the version of Windows Server 2016 being used, and force it to retry activation.

For example, for Windows Server 2016 Datacenter, you would run:

This step is not necessary for VMs created from the Windows Server 2016 gallery image, as the gallery image has the appropriate KMS client setup key already configured.

For activation issues involving Windows Server 2016 VMs failing to activate despite having the KMS client setup key configured, or for activation issues with Azure VMs using other versions of Windows, please review the remaining steps below.

Windows VMs should be configured with the KMS client setup key for the version of Windows being used, and have connectivity to port 1688 at kms.core.windows.net in order to activate successfully.

If you are using site-to-site VPN with forced tunneling, please see Use Azure custom routes to enable KMS activation with forced tunneling.

If you are using ExpressRoute with a default route published, please see Azure VM may fail to activate over ExpressRoute.

Product Activation Failed Windows 10

Windows License Activation Failed

If your Azure VM experiences Windows activation failures, please try the following steps to resolve the issue. An example of an error message you may see is:

Note that when the grace period has expired and Windows is still not activated, Windows Server 2008 R2 and later versions of Windows will show additional notifications about activating, the desktop wallpaper remains black, and Windows Update will install security and critical updates only, but not optional updates. See also the Notifications section at the bottom of the Licensing Conditions TechNet page.

Steps to Troubleshoot Activation

  1. Download and extract the Psping tool to a local folder in the VM that is failing to activate.http://technet.microsoft.com/en-us/sysinternals/jj729731.aspxTo download the file, first go to Server Manager, Configure this local server, select IE Enhanced Security Configuration, and select Off under Administrators.
  2. Go to Start, search on Windows PowerShell, right-click Windows PowerShell and select Run as administrator.
  3. Make sure the VM is configured to use the Azure KMS server by running the following command. This is set at VM creation, so running this command is just a troubleshooting step to make sure the proper configuration is set.iex '$env:windirsystem32cscript.exe $env:windirsystem32slmgr.vbs /skms kms.core.windows.net:1688'The command should return:Key Management Service machine name set to kms.core.windows.net:1688 successfully. Note that the KMS endpoint differs for public versus national cloud regions as listed at the beginning of this article, so if the VM is in a national cloud region (e.g. China, Germany, or US Gov), replace kms.core.windows.net:1688 with the relevant KMS endpoint for the region where the VM resides.
  4. Verify with Psping that you have connectivity to the KMS server. Switch into the folder where you extracted the Pstools.zip download, then run:.psping.exe kms.core.windows.net:1688In the second-to-last line of the output, make sure you see:Sent = 4, Received = 4, Lost = 0 (0% loss)If Lost is greater than 0, the VM does not have connectivity to the KMS server. In that case, if the VM is in a virtual network and has a custom DNS server specified, you must make sure that DNS server is able to resolve kms.core.windows.net. Or, change the DNS server to one that does resolve kms.core.windows.net. Note that if you remove all DNS servers from a virtual network, VMs will then use Azure's internal DNS service, which is able to resolve kms.core.windows.net.Aside from DNS issues, verify the guest firewall has not been configured in such a way that would block activation attempts. Note that the KMS endpoint differs for public versus national cloud regions as listed at the beginning of this article, so if the VM is in a national cloud region (e.g. China, Germany, or US Gov), replace kms.core.windows.net:1688 with the relevant KMS endpoint for the region where the VM resides.
  5. After verifying successful connectivity to kms.core.windows.net:1688 (or the respective KMS endpoint for the national cloud region where the VM is running) run the following command from that elevated PowerShell prompt. This command attempts activation multiple times in a row.1..12 | % { iex '$env:windirsystem32cscript.exe $env:windirsystem32slmgr.vbs /ato' ; start-sleep 5 }Successful activation will return:Activating Windows(R), ServerDatacenter edition (12345678-1234-1234-1234-12345678) ...
    Product activated successfully.
  6. If activation still failed, and the VM is running Windows Server 2012 R2 Datacenter, Standard, or Essentials, try the command below for the specific SKU. You can verify the OS version by going to Start, searching on Msinfo32, double-clicking Msinfo32.exe, and looking at the OS Name in the right pane.For Windows Server 2012 R2 Datacenter, run the following from the elevated PowerShell prompt:iex '$env:windirsystem32cscript.exe $env:windirsystem32slmgr.vbs /ipk W3GGN-FT8W3-Y4M27-J84CP-Q3VJ9'For Windows Server 2012 R2 Standard, run the following from the elevated PowerShell prompt:iex '$env:windirsystem32cscript.exe $env:windirsystem32slmgr.vbs /ipk D2N9P-3P6X9-2R39C-7RTCD-MDVJX'For Windows Server 2012 R2 Essentials, run the following from the elevated PowerShell prompt:iex '$env:windirsystem32cscript.exe $env:windirsystem32slmgr.vbs /ipk KNC87-3J2TX-XB4WP-VCPJV-M4FWM'After entering the specific command above for the SKU of Windows Server 2012 R2 the VM is using, try activating again:iex '$env:windirsystem32cscript.exe $env:windirsystem32slmgr.vbs /ato'
  7. At this point if you are still unable to activate the VM, check the Application event log for events from source Microsoft-Windows-Security-SPP to help understand why activation is failing.
Windows License Activation Failed

If you are still unable to activate after attempting the above steps, let us know in the comments or contact Azure support.