Scenario: A user attempts to launch their virtual desktop, "Win7 Desktop," from within Receiver for Web. The virtual desktop fails to launch, and the user receives a notification stating: Cannot…

Viktor S.Apr 2, 2026

B and D are your answers, and the logic is simple once you stop guessing and start thinking about what that error actually means. "Cannot start desktop" tells you the machine itself is the problem, it is either stuck, unregistered, or in a failed power state, so your fix has to target the machine directly. Option B gives the admin a clean way to do that through Citrix Director, which is exactly what Director is built for, remote machine management and session control without touching the hypervisor console. Option D lets you accomplish the same restart action right from Receiver for Web via the right-click context menu on the desktop icon, which is useful if the admin or an empowered user can act quickly without jumping to another tool. A is a waste of time because refreshing your browser session does nothing to a VM that is already in a bad state, and C is completely off-topic since an SSL cert problem on StoreFront would stop you from loading the store at all, not throw a desktop-specific launch error. Fix the machine, not the frontend.

Fatima Z.Mar 25, 2026

My trick for this one is "R.R." which stands for Restart Right-click, because both fixes share the same DNA, which is the admin either reaching into Director to force a restart or the user right-clicking that stubborn desktop icon to kick it back to life. Does anyone know if the right-click Restart option in Receiver for Web sends the same underlying reset command as what Director fires off, or are those two different mechanisms under the hood?

Kemal J.Apr 14, 2026

I'll be honest, my first instinct was A, because half the time in these scenarios the "fix" they test is just refreshing the session layer, and closing and reopening Receiver for Web is the Citrix equivalent of turning it off and on again. But then I thought about it more carefully and A is wrong because closing the browser does nothing to the underlying desktop session state, it just disconnects your view of a problem that still exists on the broker side. The two that actually make sense are B and D. Director gives the admin the ability to restart the desktop from the management plane without touching the end user's browser at all, which is the correct admin-side action. And D is the right move for users who can right-click the icon in Receiver for Web and select Restart directly, because that sends the restart signal through the session layer to the actual VM. C is a distractor designed to trick people who remember reading about SSL errors in StoreFront deployments, but nothing in this scenario points to a certificate problem, and slapping a new cert on a server does not fix a desktop that is already failing to start after authentication cleared fine.

Mei-Ling H.Apr 21, 2026

B and D are correct. Director gives admins the backend control to force-restart a stuck VM, and right-clicking the desktop icon in Receiver for Web is the quick self-service path that does the same thing from the user-facing side without needing to close and reopen anything (which option A suggests but does not actually address a failed desktop state).