Resetting Tailscale on Windows after a 503 no-backend error

Tailscale on Windows can stay on "Starting..." when the client cannot reach its background service. In the case I was troubleshooting, trying to log in from PowerShell returned:

PS C:\Users\VmAdmin> tailscale login
503 Service Unavailable: no backend

A related error to look for is:

open \\.\pipe\ProtectedPrefix\Administrators\Tailscale\tailscaled: The system cannot find the file specified.

These errors point to a local service problem, but don't identify why the service is unavailable. Resetting state is a recovery option if restarting the service doesn't resolve it.

#Check the service first

Open PowerShell as Administrator and check the service:

Get-Service Tailscale

Start it if it's stopped, or restart it if it's running, then try tailscale status again. If it still fails, keep the logs from C:\ProgramData\Tailscale\Logs before resetting anything. Tailscale's daemon documentation identifies that as the Windows log directory.

#Reset local state

A reset can require a new login, device approval, and a new device entry or IP address. Make sure you have access to the machine independently of Tailscale before stopping the service.

The following sequence stops the service and moves its local data aside. Close the Tailscale tray app first, then run:

Stop-Service Tailscale -Force
Get-Process tailscaled -ErrorAction SilentlyContinue | Stop-Process -Force

Once the service has stopped, rename the folder so the previous state and logs are retained:

cd C:\ProgramData
Rename-Item -Path "Tailscale" -NewName "Tailscale.bak"

If Tailscale.bak already exists, choose another backup name. If the rename fails because files are still in use, resolve that before continuing.

Start the service and authenticate again:

Start-Service Tailscale
tailscale up --force-reauth

Follow the login link, then check tailscale status and access to the resource you need.

This moves the service's data directory; it isn't a complete removal of every Tailscale setting on Windows. Tailscale's reset instructions list additional per-user and legacy locations. Resetting state also doesn't establish that a Windows update or a Wintun driver problem caused the error.

Once the new registration works, check the admin console for an obsolete device entry before removing it. Keep the saved logs if the service fails again, since repeated resets won't explain the underlying fault.