By using AWS re:Post, you agree to the AWS re:Post Terms of Use

The screen does not work after starting the virtual server

0

The first time you start the EC2 virtual server, it works fine. The next day the EC2 virtual server screen stops working. A blue startup screen is shown, and after a while the screen turns white. Although the virtual server must run 24/7

Reinstalling the virtual server and creating a new one did not help

OS: Microsoft Windows Server 2025 Base, Instance type - c5.4xlarge,

!Screen with proof that the screen does not work (/media/postImages/original/IMQHNvotkySLKO5XIoLJLDaQ)

asked 23 days ago37 views
1 Answer
0

Based on the symptoms you've described, it appears your Amazon EC2 Windows instance is experiencing a boot or display issue. While Windows Server 2025 is not a current version (the latest as of now is 2022), I'll provide some general troubleshooting steps for Windows Server instances on EC2.

  1. Console Output: Check the instance's console output for any error messages or additional information. This can be done through the EC2 console by selecting the instance and choosing Actions > Monitor and troubleshoot > Get system log.

  2. Last Known Good Configuration: If the instance is stuck on a blue screen or not booting properly, you might need to perform a Last Known Good Configuration. This involves taking the disk offline and attaching it to a helper EC2 instance, then using the EC2Rescue tool to restore the last known good configuration.

  3. EC2Rescue Tool: This AWS tool can help diagnose and fix various issues with Windows instances. It can be particularly useful for instances that are unresponsive or stuck in a boot loop.

  4. Check Instance Status: Verify if the instance is passing both status checks in the EC2 console. If it's failing the system status check, there might be an underlying hardware or networking issue.

  5. RDP Settings: Ensure that Remote Desktop Protocol (RDP) settings haven't been changed inadvertently. You may need to use the EC2Rescue tool to check or modify RDP-related settings.

  6. Driver Issues: There could be issues with display drivers. Try updating to the latest EC2Config service and PV drivers.

  7. Resource Utilization: Check if the instance is over-utilized, which could cause it to become unresponsive. Monitor the instance's CPU, memory, and disk usage through CloudWatch metrics.

If these steps don't resolve the issue, you may need to create a new AMI from the problematic instance (without rebooting) and launch a new instance from this AMI. If the problem persists, it would be advisable to contact AWS support for further assistance, especially if you've already tried reinstalling and creating a new instance without success.

Remember to regularly back up your data and consider using Amazon EBS snapshots to easily restore your instance to a previous working state if needed.
Sources
Troubleshoot issues connecting to your Amazon EC2 Windows instance - Amazon Elastic Compute Cloud
Perform Last Known Good Configuration in Amazon EC2 | AWS re:Post
Troubleshoot Amazon EC2 Windows instance start issues - Amazon Elastic Compute Cloud
Troubleshoot Amazon EC2 instance stop issues - Amazon Elastic Compute Cloud

profile picture
answered 23 days ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions