Not Recommended
I launched from this AMI but it is not working. Also alarms checks are not passed.
Not recommended for users who need to do some testing on Windows 10 on EC2. It is totally a waste of time.
To clarify again, the instance launches when it is a xlarge or larger. You will be sadly frustrated trying to initialize Windows 10, which requires 8Gb of memory, on an instance with 4Gb or less of memory. Once booted, the reboot time is less and the instance can be scaled down to 4Gb, maybe even as low as 2Gb of memory, provided you are not running intensive workloads. If you need instant uptime - DO NOT STOP THE INSTANCE. Simply disconnect from RDP without shutting down the instance.
The instance works best as an xlarge or larger (2xlarge, 4xlarge), if you want blazing performance. If you have time to burn, then stick with the medium or small instance.
I also had the same issue launching Windows 10 on EC2. For the other users who are saying to wait 10 minutes after the instance has launched to connect must be kidding themselves. How are you going to wait 10 minutes each time when an instance needs to be stopped restarted. For users who need a Win 10, go with S3. It worked right away.
It does work. You should have waited for full boot, as stated in guide. ~10 minutes AFTER instance reported as "Running" i've made a screenshot and connected successfuly.