- Newest
- Most votes
- Most comments
Usually when you provision an EC2 instance that's running Windows, you're paying for compure resources + a licensing fee (that's why a Windows EC2 costs more than an equivalent Linux instance).
There are a number of reasons that activation could have failed, the steps to take are described here https://repost.aws/knowledge-center/windows-activation-fails
Am i supposed to supply my own license?
There is an option to bring your own licence (BYOL), could you have selected that? https://aws.amazon.com/windows/resources/licensing/#Using_Microsoft_software_licenses_on_the_AWS_Cloud (note that it's difficult to "accidentally" select that, if you meant to go for the default option of paying for EC2 + licence)
General details about what you're paying for and what it entitles you to (including support etc.) is at https://aws.amazon.com/windows/faq/#ms-amz
The licensing section is also worthwhile if your issue isn't resolved at this point https://aws.amazon.com/windows/faq/#licensing
Relevant content
- asked 2 years ago
- asked a year ago
AWS OFFICIALUpdated 9 months ago- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 3 years ago
Thank you. Very informative. Ran through the options in the article you shared, but still getting the following message: We cant activate windows as we cant connect to the activation server... Error code 0xC004F074
I ran the automation to activate both online and offline... But both failed. I Created a throw away instance and opened all ports in and out. Even disabled firewall just to see if this will work... Will not do it in prod obviously... Still no luck...