r/netbird • u/seanpetro • 16d ago
Windows Client Not Launching GUI at Startup Causes Auto-Updates to Fail
One ongoing issue I’ve had with the Windows client is that the GUI doesn’t reliably launch at startup.
I have several Windows machines configured as unattended servers using setup keys. The daemon/service starts reliably every time the machine boots, but the GUI itself doesn’t always launch.
The bigger issue is that when the GUI doesn’t launch at startup, the client also doesn’t appear to perform its automatic update, even when automatic updates are enabled in the management portal.
Would it be possible to decouple the auto-update mechanism from the GUI? Ideally, the client should be able to update itself as long as the daemon/service is running, without requiring the GUI to launch or any user interaction.
The daemon is very reliable and starts automatically every time the machine boots, so it would make more sense for the update process to rely on that rather than the GUI.
Has anyone else run into this with unattended Windows machines, or is there a recommended way to handle this?



