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

My Amazon WorkSpaces Windows WorkSpace is stuck in the starting, rebooting, or stopping status.

Short descriptionThe WorkSpace status depends on health checks of the WorkSpace's components, such as PCOIP Standard Agent, SkylightWorkSpacesConfigService, or Web Access agent. Sometimes the WorkSpace's operating system (OS) takes a long time to boot. Or, the WorkSpace's components fail to report the actual status of the WorkSpace. These issues might cause the status to become stuck in the starting, rebooting, or stopping state.

ResolutionIf your Windows WorkSpace is stuck in the starting, rebooting, or stopping status, then review the following common causes and troubleshooting tips:Pending updatesIf the Workspaces console or client application sends a reboot command to the WorkSpace, then the WorkSpace might be busy applying updates. A reboot action also initiates any pending WorkSpaces component updates.Windows updates or other operating system (OS) activity can delay the boot process, and WorkSpaces health checks might take longer to reflect the actual status. Wait a few minutes, and then try again to connect to the WorkSpace.WorkSpaces services in stopped state or blocked by antivirus softwareTo verify that the required WorkSpaces services are started at the OS level, follow these steps:1.    Connect to the WorkSpace using Remote Desktop Connection (RDP).2.    Open Administrative Tools.3.    Open the context (right-click) menu for Services, and then choose Open. Check if the Status is Stopped for any of the following services:STXHD Hosted Application ServicePCoIP Standard Agent for WindowsSkyLightWorkspaceConfigService4.    If the status is Stopped, then open the context (right-click) menu for the service, and choose Start. The status now Running.5.    Verify that the Startup Type for all three services is set to Automatic. To change the 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 the three services is Running, then antivirus software might be blocking the services. To fix this, set up an allow list for the locations where the service components are installed. For more information, see Required configuration and service components for WorkSpaces.Network adapters turned onVerify that both network adapters on the WorkSpace are turned on:1.    Connect to the WorkSpace using RDP.2.    Open the Start menu, and then navigate to Control Panel > Network and Internet > Network and Sharing Center.3.    Verify that there are two networks listed in the View your active networks section. If there's only one network listed, then choose Change adapter settings. Confirm that Ethernet 3 is turned on. If necessary, open the context (right-click) menu for Ethernet 3, and then choose Enable.Restart the WorkSpaceIf you still have issues, then restart the WorkSpace from the WorkSpaces console. Wait a few minutes for the WorkSpace to come online, and then try again to connect to the WorkSpace. The status of the WorkSpace changes within 90 minutes.

Related informationWhy can't I create a new WorkSpace?