Salad logoSalad logo
Salad logoSalad logo
Quickstart
Your PCHow to find your GPU or CPU specificationsWhat GPU or CPU is Salad detecting?Identifying your CPUIdentifying your motherboardHow to update your NVIDIA driversHow to update your AMD driversHow to update your Intel driversHow to reinstall your GPU driversHow to enable Compute mode on AMD driversHow to disable ECCWhat is WSL?How to enable virtualization support on your machineEnable virtualization on ASUS PCsEnable virtualization on Acer PCsEnable virtualization on Dell PCsEnable virtualization on HP PCsEnable virtualization on Lenovo PCsEnable virtualization by motherboard: MSI (American Megatrends)Enable virtualization by motherboard: GigabyteHow to improve internet speed for container jobsUsing remote desktop with SaladHow to check if your Salad installer is safeHow to create a support ticketHow to create a HAR file
Discord
GuidesYour PC

Using remote desktop with Salad

Why Remote Desktop (RDP) stops Salad's container environment, which remote-access tools work instead, and how to run a headless PC.

Salad's container environment needs an interactive desktop session on the PC. Windows Remote Desktop and every other tool built on the Remote Desktop Protocol (RDP) replaces that session with a remote one, so while you are connected, and often after you disconnect, Salad cannot start or keep its container environment running and jobs fail.

This affects:

  • Windows Remote Desktop Connection (mstsc) and the Remote Desktop app
  • Microsoft Remote Desktop for Mac, iOS and Android
  • Any third-party tool that uses RDP under the hood

Use a screen-mirroring tool instead

Tools that mirror the existing desktop session, rather than creating a new one, usually work fine with Salad:

  • Parsec
  • AnyDesk
  • Chrome Remote Desktop
  • VNC-based tools (TightVNC, RealVNC, UltraVNC)
  • TeamViewer

If you have been using RDP, disconnect, then restart the PC so a normal desktop session is created, and start Salad from that session.

Running a PC without a monitor (headless)

After a reboot, Windows waits at the sign-in screen. There is no desktop session yet, so Salad cannot start the container environment, and auto-start does not help. Make Windows sign in automatically:

  1. Press Windows + R, type netplwiz and press Enter.
  2. Untick Users must enter a user name and password to use this computer, click OK and enter your password. If the checkbox is missing on Windows 11, turn off Settings > Accounts > Sign-in options > Require Windows Hello sign-in for Microsoft accounts first, then reopen netplwiz.
  3. Reboot to confirm the PC lands on the desktop by itself.

Pair this with auto-start and disabling sleep so Salad resumes Chopping after Windows updates. Some GPUs also need a monitor or an HDMI dummy plug connected to run at full performance.

Still stuck?

If Salad still reports a problem after switching tools and rebooting, see Failed to start container environment, then send Salad Support your machine ID, a screenshot of the notification and your zipped logs as described in How to create a support ticket.

Edit on GitHub

Last updated on

How to improve internet speed for container jobs

Why Salad's speed test reads lower than yours, and what to change (wired connection, USB Wi-Fi, other traffic) to qualify for more container jobs.

How to check if your Salad installer is safe

Verify the file hash of your Salad installer against the official GitHub release so you know it is genuine.

On this page

Use a screen-mirroring tool insteadRunning a PC without a monitor (headless)Still stuck?