Why is my Windows WorkSpace stuck in the start, reboot, or stop status?

Resolution

Check for updates

If the WorkSpaces console or client application sends a reboot command to the WorkSpace, then the WorkSpace might be busy when it applies updates. A reboot action also initiates pending WorkSpaces component updates. Operating system (OS) updates or other OS activities might delay the reboot process. Also, WorkSpaces health checks might take longer to reflect the actual status. Wait a few minutes, and then try to connect to the WorkSpace.

Verify that the required WorkSpaces services start at the OS level

Complete the following steps:

1. Use Remote Desktop Protocol (RDP) to connect to the WorkSpace.
2. Choose Administrative Tools.
3. Choose Services, and then choose Open.
4. Check whether the Status is Stopped for the SkyLightWorkspaceConfigService service.
   Note: For PCoIP WorkSpaces, also check the status for the PCoIP Standard Agent for Windows and STXHD Hosted Application Service services. For WorkSpaces Streaming Protocol (WSP) WorkSpaces, also check the status for the DCV Server and WSP Adapter for DCV services.
5. If the status is set to Stopped, then open the context menu for the service. Then, choose Start.
6. Verify that the Startup Type for all services in your WorkSpace is set to Automatic.
7. Under Startup Type, open the context menu for the service, and then choose Properties.
8. For Startup type, choose Automatic, and then choose Ok.

If the status for each service is Running, then antivirus software might be blocking the services. To resolve this issue, set up an allowlist for the locations that the required WorkSpaces service components use.

If any of the preceding services aren't installed, then reboot the WorkSpace. Wait for 15 minutes. If the service doesn't install after a reboot, then contact AWS Support.

Verify that the management network interface is on

Complete the following steps:

1. Use RDP to connect to the WorkSpace.
2. Choose Start, and then choose Control Panel.
3. Choose Network and Internet, and then choose Network and Sharing Center.
4. Verify that View your active networks lists two network connections.
5. If there's only one network listed, then choose Change adapter settings.
6. Confirm that Ethernet 3 is on. If Ethernet 3 isn't on, then open the context menu, and then choose Enable.

Restart the WorkSpace from the WorkSpaces console

If you still have issues, then wait until the status of the WorkSpace shows as Unhealthy. Then, restart the WorkSpace. Wait for a few minutes for the WorkSpace to come online, and then try to connect to the WorkSpace. The status of the WorkSpace changes within 15 minutes.