All Products
Search
Document Center

Desktop failure or exception displayed after remote logon of an ECS instance running Windows

Last Updated: Dec 30, 2020

Disclaimer: This article may contain information about third-party products. Such information is for reference only. Alibaba Cloud does not make any guarantee, express or implied, with respect to the performance and reliability of third-party products, as well as potential impacts of operations on the products.

 

Problem description

This article describes how to display the desktop or display exception after you remotely log on to an ECS instance running Windows.

 

Cause

The possible reasons are mainly composed of the following three aspects.

 

Solution

Alibaba Cloud reminds you that:

  • Before you perform operations that may cause risks, such as modifying instance configurations or data, we recommend that you check the disaster recovery and fault tolerance capabilities of the instances to ensure data security.
  • If you modify the configurations and data of instances including but not limited to ECS and RDS instances, we recommend that you create snapshots or enable RDS log backup.
  • If you have authorized or submitted security information such as the logon account and password in the Alibaba Cloud Management console, we recommend that you modify such information in a timely manner.

Insufficient system resources

Log on to the instance. For more information about how to log on to the instance, see connect to a Windows instance by using a management Terminal. In the top navigation bar, choose project management> processes. When you confirm that the memory usage is too high, close the process that occupies more resources. You can also click user to check whether multiple sessions exist. If yes, you can log off the disconnected session, that is, the program on the corresponding connection terminal is also logged off, and then tested.

 

If you cannot connect to the terminal on the console, the system may be down. We recommend that you restart the server in the console, and check the system logs to identify the cause.

 

System Display Settings

Problem description

The browsing page opened on the server is black, and other interfaces are also black.

blob.png

 

Solution

  1. Right-click an empty area of the desktop, select the screen resolution, and click display in the interface that opens.
    blob.png
  2. Choose change window color on the left.
    blob.png
  3. Confirm that the default color is high contrast black. Select Windows basic from the drop-down list, and then click save changes.
    blob.png

 

The explorers .exe process is abnormal

  1. Log on to an instance. For more information about how to log on to an instance, see use a management terminal to connect a Windows instance. In the Task Manager window, click files in the actions column. > Create a new task, enter Explorer. Exe, and click OK.
    bb.png
  2. When the desktop returns to normal, only the display problem of the currently connected desktop is solved, but the logon of the new account is still not restored. Follow these steps. If the backup has not been restored, see more information to perform the operation.
    Tip: This method only solves the problem that the desktop is not loaded automatically. The root cause problem is still an abnormal system, so scan the system as soon as possible to avoid other hidden dangers.
  3. Log on to the instance and select start > Run > gpedit.msc > User configuration > Windows settings > Script (login /logout), and then add the login script file c:\\ Windows \Explorer. Then click apply > Confirm.
    708.jpg
  4. Log on to the terminal and run the gpupdate command to refresh the group policy. explorer processes are automatically loaded when you log on later.
    710.jpg

 

References

If the desktop is not restored, do the following.

  1. If the system prompts that explorer cannot be found, you can try to restore the file. Open task manager and click new task > Browse and search for windowsxs on the right side of the c:\\ Explorer directory.
  2. Copy the last modified exploration. EXE process to the C:\Winodws directory.
    709.jpg
  3. If the problem persists, we recommend that you use snapshots to roll back your system and scan your system in a timely manner. If your business still cannot solve the problem, step 3 or step 4 of exploring. EXE process is abnormal.

 

Application scope

  • ECS