tailscale: Tailscale fails to start after updating Windows 10 2004 -> 21H1
I’m on a corp managed computer as well and facing the error “Please restart the Tailscale Windows Service.”, but on my end it was working a few hours ago. I decided to update from 2004 to 21H1 and after the reboot, I started facing this issue. Already tried rebooting the service, tried reinstalling the client, also installed the unstable build and the problem continues. My Tailscale service was showing as running, restarted the system, reinstalled Tailscale to the stable version and now I’m getting those errors below.
---------------------------
Tailscale Error
---------------------------
Tailscale service stopped.
Version 1.8.5 (t118cf0cd7-gc6fd9c9d5)
LogID: f58e11d9b96dc7b5813eb4e920ba18fe09073b1246cd8e617dae98f7d6535a8f
(Ctrl-C to copy this text)
---------------------------
OK
---------------------------
The Tailscale service on Local Computer started and then stopped.
Some services stop automatically if they are not in use by other services or programs.
Windows could not start the Tailscale service on Local Computer
Error 1067: The process terminated unexpectedly
_Originally posted by @Oujiii in https://github.com/tailscale/tailscale/issues/803#issuecomment-852566516_
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 15 (7 by maintainers)
yes, tried that several times - but did it again, turns out I need a restart after deinstalling! Thanks for your comment @Oujiii ! 😃
So order that worked for me:
For most problems where the taskbar icon says to restart the backend, please delete
%LOCALAPPDATA%\Tailscale\*and wait about a minute to be asked to login again.This happens when a different state file in C:\Windows gets deleted. We’re going to move that state file out of C:\Windows for the next release.
@jiaminghe, closed bugs are worked on so I suggest you open a new bug. You can reference the new bug from this one if you’d like.
Even if they have the same symptoms, they’re likely different problems.
A process that has seemed to work for some users is to make sure all traces of an older version of the wintun device are removed.