[GH-ISSUE #5151] Client Auto Update Windows #10680

Open
opened 2026-08-05 01:26:52 -04:00 by saavagebueno · 5 comments
Owner

Originally created by @numenory on GitHub (Jan 22, 2026).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/5151

Scenario

Auto update enabled.
Windows client set to start at boot.
Client version is out of date.

Reboot/Start machine - peer/client automatically connects, no update occurs

Currently in order to get the auto update to trigger, you have you explicitly disconnect and then connect again.

Request:

When a windows client reboots/starts, it checks for an update and if auto update is enabled it installs the update.

Originally created by @numenory on GitHub (Jan 22, 2026). Original GitHub issue: https://github.com/netbirdio/netbird/issues/5151 Scenario Auto update enabled. Windows client set to start at boot. Client version is out of date. Reboot/Start machine - peer/client automatically connects, no update occurs Currently in order to get the auto update to trigger, you have you explicitly disconnect and then connect again. Request: When a windows client reboots/starts, it checks for an update and if auto update is enabled it installs the update.
saavagebueno added the feature-request label 2026-08-05 01:26:52 -04:00
Author
Owner

@1nerdyguy commented on GitHub (Jan 22, 2026):

+1 on this. We do a lot of systems with a setup key for always on connectivity to a limited profile, and then users switch profiles. We're still managing updates outside of Netbird due to this.

<!-- gh-comment-id:3785385544 --> @1nerdyguy commented on GitHub (Jan 22, 2026): +1 on this. We do a lot of systems with a setup key for always on connectivity to a limited profile, and then users switch profiles. We're still managing updates outside of Netbird due to this.
Author
Owner

@richardwarriner commented on GitHub (Jan 23, 2026):

+1 I have been staring at the tray icon telling there was an update, expecting it to spontaneously update at some point. I did a manual disconnect and reconnect, and it did indeed update, although the tray app didn't appear, and I had to manually run it.

I have Netbird connected 24/7 so as a minimum it would need to update on reboot, which surely counts as a disconnect?

But for machines that reboot rarely, it seems it is still a manual job

<!-- gh-comment-id:3789187382 --> @richardwarriner commented on GitHub (Jan 23, 2026): +1 I have been staring at the tray icon telling there was an update, expecting it to spontaneously update at some point. I did a manual disconnect and reconnect, and it did indeed update, although the tray app didn't appear, and I had to manually run it. I have Netbird connected 24/7 so as a minimum it would need to update on reboot, which surely counts as a disconnect? But for machines that reboot rarely, it seems it is still a manual job
Author
Owner

@Oriann commented on GitHub (Mar 9, 2026):

Have this problem too. PC reboot should initiate netbird update process, manually disconnecting and reconnecting is not valid for a lot of workstations.

<!-- gh-comment-id:4023314914 --> @Oriann commented on GitHub (Mar 9, 2026): Have this problem too. PC reboot should initiate netbird update process, manually disconnecting and reconnecting is not valid for a lot of workstations.
Author
Owner

@SasSam commented on GitHub (Mar 27, 2026):

Auto update doesn't do what its name suggests. It should help us keep the client up to date without any interaction. Also, triggering the auto update is not possible remotely because I need to disconnect the peer first. Therefore, I've lost the entire connection, so I wouldn't be able to reconnect the peer remotely.

<!-- gh-comment-id:4142963382 --> @SasSam commented on GitHub (Mar 27, 2026): Auto update doesn't do what its name suggests. It should help us keep the client up to date without any interaction. Also, triggering the auto update is not possible remotely because I need to disconnect the peer first. Therefore, I've lost the entire connection, so I wouldn't be able to reconnect the peer remotely.
Author
Owner

@sjansen1 commented on GitHub (Apr 23, 2026):

Netbird selfupdate is a bit unreliable on Windows and macOS, the client starts the update process (System Critical, Update Netbird), but sometimes the client does not start again (Windows, macOS) and didnt update anything (macOS), a second or third try is mostly successful, but that is confusing for our endusers and delay working.

<!-- gh-comment-id:4302898893 --> @sjansen1 commented on GitHub (Apr 23, 2026): Netbird selfupdate is a bit unreliable on Windows and macOS, the client starts the update process (System Critical, Update Netbird), but sometimes the client does not start again (Windows, macOS) and didnt update anything (macOS), a second or third try is mostly successful, but that is confusing for our endusers and delay working.
Sign in to join this conversation.
No Label feature-request
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#10680