Why is my Windows WorkSpace stuck in the starting, rebooting, or stopping status?

Resolution

WorkSpace status depends on health checks of the components from the WorkSpace, including the required WorkSpaces services. The operating system (OS) for the WorkSpace might take a long time to boot. Or, the components fail to report the actual status of the WorkSpace. These issues cause the status to become stuck in the starting, rebooting, or stopping state.

Pending updates

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

WorkSpaces services in stopped state, blocked by antivirus software, or not installed

To verify that the required WorkSpaces services are started at the OS level, complete the following steps:

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

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

If any of the preceding services isn't installed, then to automatically install the service, reboot the WorkSpace. Wait for 15 minutes. If the service still isn't installed after a reboot, then you must open a support case.

Management network interface must be on

To verify that the management network interface is on, complete the following steps:

1. Use RDP to connect to the WorkSpace.
2. Open the Start menu, 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.
   If there's only one network listed, then choose Change adapter settings. Confirm that Ethernet 3 is on. If it's not, then open the context (right-click) menu for Ethernet 3, and then choose Enable.

Restart the WorkSpace from WorkSpaces console

If you still have issues, then wait until the status of the WorkSpace shows as Unhealthy in the console. 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.