- Newest
- Most votes
- Most comments
The stuck-Starting state with both restart and restore failing is a known pattern. AWS has a Knowledge Center article that documents the three most common causes: one or more required WorkSpaces services (SkyLightWorkspaceConfigService, PCoIP Standard Agent, or DCV Server depending on your protocol) stopped or set to Manual startup, the management network interface (Ethernet 3) being disabled, or antivirus software blocking required components. Worth checking those first before doing another full rebuild.
Also, AWS has a free SSM Automation runbook called AWSSupport-RecoverWorkSpace that does reboot then restore then rebuild in sequence and stops as soon as the workspace comes back healthy. That alone would save you the data loss from going straight to a full rebuild every time. There's also an approval-gated variant if you want a human confirmation step before anything destructive runs.
Two quick questions that would help narrow this down: is the affected workspace Windows or Linux? And has any antivirus or endpoint security software been recently updated on that machine? The fix path is pretty different depending on those two things.
answered 2 months ago
Thank you very much for your help, Regarding the runbook - that's new to me, I'll check it out. In answer to your two questions:
- I am running Windows 2022 workspaces, and they are all on the DCV protocol.
- No antivirus software, etc., has been installed by us or by the user on the Workspace endpoint.
answered 2 months ago
Relevant content
asked 8 years ago
asked 3 years ago
asked 7 years ago
asked 2 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago
