SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-05-11 02:31:41 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

NetBird Client for windows 7 #2223

New Issue
Closed
opened 2025-11-20 07:06:09 -05:00 by saavagebueno · 12 comments
saavagebueno commented 2025-11-20 07:06:09 -05:00
Owner
Copy Link

Originally created by @sgm456 on GitHub (Aug 22, 2025).

A client build for Windows 7 is required. Many PCs still use Windows 7.

Originally created by @sgm456 on GitHub (Aug 22, 2025). A client build for Windows 7 is required. Many PCs still use Windows 7.
saavagebueno added the feature-requestsystem-compatibility-issuewindows labels 2025-11-20 07:06:09 -05:00
saavagebueno commented 2025-11-20 07:06:10 -05:00
Author
Owner
Copy Link

@nazarewk commented on GitHub (Aug 22, 2025):

(not knowing the technical background for Windows 7 vs 10+) Is there anything preventing the current installers from being used with Windows 7 system?

@nazarewk commented on GitHub (Aug 22, 2025): (not knowing the technical background for Windows 7 vs 10+) Is there anything preventing the current installers from being used with Windows 7 system?
saavagebueno commented 2025-11-20 07:06:11 -05:00
Author
Owner
Copy Link

@sgm456 commented on GitHub (Aug 22, 2025):

the golang version on which the client is compiled does not support win 7

@sgm456 commented on GitHub (Aug 22, 2025): the golang version on which the client is compiled does not support win 7
saavagebueno commented 2025-11-20 07:06:11 -05:00
Author
Owner
Copy Link

@nazarewk commented on GitHub (Aug 22, 2025):

the golang version on which the client is compiled does not support win 7

I'm afraid there is nothing we can do about it ourselves short of finding a volunteer to maintain a NetBird client community fork based on an older Go version.

@nazarewk commented on GitHub (Aug 22, 2025): > the golang version on which the client is compiled does not support win 7 I'm afraid there is nothing we can do about it ourselves short of finding a volunteer to maintain a NetBird client community fork based on an older Go version.
saavagebueno commented 2025-11-20 07:06:11 -05:00
Author
Owner
Copy Link

@1nerdyguy commented on GitHub (Aug 22, 2025):

Win7 went EoL in 2020. It went end of extended (ESU) in 2023.

Can we just let it die? sometimes, making poor decisions (keeping win 7) means you have to pay the penalty (no Netbird for you)

EDIT:

I hate this.
https://github.com/stunndard/golangwin7patch

@1nerdyguy commented on GitHub (Aug 22, 2025): Win7 went EoL in 2020. It went end of extended (ESU) in 2023. Can we just let it die? sometimes, making poor decisions (keeping win 7) means you have to pay the penalty (no Netbird for you) EDIT: I hate this. https://github.com/stunndard/golangwin7patch
saavagebueno commented 2025-11-20 07:06:11 -05:00
Author
Owner
Copy Link

@sgm456 commented on GitHub (Aug 27, 2025):

https://github.com/stunndard/golangwin7patch
not worked

@sgm456 commented on GitHub (Aug 27, 2025): https://github.com/stunndard/golangwin7patch not worked
saavagebueno commented 2025-11-20 07:06:11 -05:00
Author
Owner
Copy Link

@sgm456 commented on GitHub (Aug 27, 2025):

Yes, Windows 7 EOL.
Yes, not everyone has Windows 7 installed.
But, Windows 7 is still used by many people, and is the de facto corporate standard in many organizations.
A non-working client for Windows 7 is an obstacle to the implementation of netbird and expansion of the client base.
It is easier to have another build of the client than to reinstall the OS.

@sgm456 commented on GitHub (Aug 27, 2025): Yes, Windows 7 EOL. Yes, not everyone has Windows 7 installed. But, Windows 7 is still used by many people, and is the de facto corporate standard in many organizations. A non-working client for Windows 7 is an obstacle to the implementation of netbird and expansion of the client base. It is easier to have another build of the client than to reinstall the OS.
saavagebueno commented 2025-11-20 07:06:11 -05:00
Author
Owner
Copy Link

@1nerdyguy commented on GitHub (Aug 27, 2025):

Anecdotes being Anecdotes, I haven't seen Win7 alive in corporate in at least 2 years, thankfully. Heck, Win10 is dying at the end of the year..

Personally, I'd say this is such a niche case i'd question the worth of the developers time.

@1nerdyguy commented on GitHub (Aug 27, 2025): Anecdotes being Anecdotes, I haven't seen Win7 alive in corporate in at least 2 years, thankfully. Heck, Win10 is dying at the end of the year.. Personally, I'd say this is such a niche case i'd question the worth of the developers time.
saavagebueno commented 2025-11-20 07:06:12 -05:00
Author
Owner
Copy Link

@sgm456 commented on GitHub (Aug 27, 2025):

The original wireguard client works fine under windows 7. Probably because wiregard is needed by all users, not just those who have adopted the new windows. This is a balanced and reasonable policy.

@sgm456 commented on GitHub (Aug 27, 2025): The original wireguard client works fine under windows 7. Probably because wiregard is needed by all users, not just those who have adopted the new windows. This is a balanced and reasonable policy.
saavagebueno commented 2025-11-20 07:06:12 -05:00
Author
Owner
Copy Link

@TonyBostonTB commented on GitHub (Sep 2, 2025):

Adding a Windows 7 client is the wrong trade-off for a security product. It forces the project to pin old toolchains and libraries, inflates the test matrix, and drags in risky crypto defaults — all to support an OS that’s been end-of-life for years. Those systems shouldn't even connect to the internet.

@TonyBostonTB commented on GitHub (Sep 2, 2025): Adding a Windows 7 client is the wrong trade-off for a security product. It forces the project to pin old toolchains and libraries, inflates the test matrix, and drags in risky crypto defaults — all to support an OS that’s been end-of-life for years. Those systems shouldn't even connect to the internet.
saavagebueno commented 2025-11-20 07:06:12 -05:00
Author
Owner
Copy Link

@sgm456 commented on GitHub (Sep 5, 2025):

Mozilla Extends Firefox Support on Windows 7/8.1 and macOS 10.12-10.14 Until March 2026

@sgm456 commented on GitHub (Sep 5, 2025): Mozilla Extends Firefox Support on Windows 7/8.1 and macOS 10.12-10.14 Until March 2026
saavagebueno commented 2025-11-20 07:06:12 -05:00
Author
Owner
Copy Link

@nazarewk commented on GitHub (Sep 5, 2025):

Mozilla Extends Firefox Support on Windows 7/8.1 and macOS 10.12-10.14 Until March 2026

If I'm reading it correctly, this is just half a year before you lose the web browser itself on the system.

I feel your pain. I'm sad to see Windows XP and Windows 7 go (I can't stand anything in between or after myself), but there is no reasonable way to proceed with supporting them when most of the other upstream projects/tools have already stopped (including those that we build upon).

The only meaningful way forward would be a very expensive (probably equivalent of ~2 or more developer salaries) extended support contract (with some company specializing in such) that could fund the development of such a "feature" on its own. It might even be a challenge to even find developers willing to implement and maintain such work, this is why I mention companies specialized in maintaining legacy software (last I heard, this is a very lucrative and expensive branch of the industry).

@sgm456 I'm sorry, but I will be closing this issue as it doesn't lead anywhere meaningful. It's not possible for us to support legacy systems after our core building block (Go programming language) has already stopped.

@nazarewk commented on GitHub (Sep 5, 2025): > Mozilla Extends Firefox Support on Windows 7/8.1 and macOS 10.12-10.14 Until March 2026 If I'm reading it correctly, this is just half a year before you lose the web browser itself on the system. I feel your pain. I'm sad to see Windows XP and Windows 7 go (I can't stand anything in between or after myself), but there is no reasonable way to proceed with supporting them when most of the other upstream projects/tools have already stopped (including those that we build upon). The only **meaningful** way forward would be a very expensive (probably equivalent of ~2 or more developer salaries) extended support contract (with some company specializing in such) that could fund the development of such a "feature" on its own. It might even be a challenge to even find developers willing to implement and maintain such work, this is why I mention companies specialized in maintaining legacy software (last I heard, this is a very lucrative and expensive branch of the industry). @sgm456 I'm sorry, but I will be closing this issue as it doesn't lead anywhere meaningful. It's not possible for us to support legacy systems after our core building block (Go programming language) has already stopped.
saavagebueno commented 2025-11-20 07:06:12 -05:00
Author
Owner
Copy Link

@1350962574 commented on GitHub (Sep 24, 2025):

@sgm456 You can use GoWin7Fixer to fix the Windows binary file of 'NetBird' so that it can run normally on Windows 7. I hope it helps you.

Image Image
@1350962574 commented on GitHub (Sep 24, 2025): @sgm456 You can use [GoWin7Fixer](https://github.com/stunndard/golangwin7patch) to fix the Windows binary file of 'NetBird' so that it can run normally on Windows 7. I hope it helps you. <img width="357" height="647" alt="Image" src="https://github.com/user-attachments/assets/69338ac8-0d42-415b-8d5c-53347e60b1b2" /> <img width="690" height="449" alt="Image" src="https://github.com/user-attachments/assets/ef1ca26c-e169-4831-bbab-9e58e69acad9" />
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
2021 Q4
2022 Q1
2022 Q1
accessibility
acl
agent
agent
Android
Android
api
authentik
automation
azure
battery-usage
bug
cache
client
client-ui
cloud
cloud-only
cloudflare
community
compatibility
config-idp
config-issue
connection
contribution
coturn
cross-vpn
dashboard
data-usage
distribution
dns
docker
documentation
duplicate
enhancement
enhancement
event-stream
feature-request
freebsd
getting-started
go
good first issue
gui
help wanted
home-assistant
idp
inconsistency
integration
integrations
ios
ipv6
jwt
k8s
keycloak
linux
login
macos
management-service
missing-docs
mobile
moved-internal
needs-review
netbird-ui
networking
new-platform
nginx
notification
okta
openwrt
packaging
peer-management
peer-management
peer-management
performance
postgres
posture-checks
psk
pull-request
Mirrored from GitHub Pull Request
 question
refactor
relay
release
rfc
routes
security
security-related
self-hosting
server
signal
sleep-issue
ssh
ssl
status
store
synology
system-compatibility-issue
test-suite
third-party-integration
triage
triage-needed
troubleshooting
UX
waiting-feedback
windows
wontfix
zitadel
No Label feature-request system-compatibility-issue windows
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#2223
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?