[GH-ISSUE #407] Barrierd is not closed #320

New issue

Open

opened 2026-05-05 06:02:15 -06:00 by gitea-mirror · 4 comments

gitea-mirror commented

2026-05-05 06:02:15 -06:00

Owner

Originally created by @MichaelMcDonnell on GitHub (Aug 21, 2019).
Original GitHub issue: https://github.com/debauchee/barrier/issues/407

Operating Systems

Server: Windows 10 Version 1809

Barrier Version

2.3.1-release

Steps to reproduce bug

Install Barrier
Chose File->Quit
Open the task manager
Notice that barrierd is still running
Uninstall barrier in App & features
Notice that the "c:\Program Files\Barrier" folder is left over and barrierd.exe is in it.

Other info

When did the problem start to occur? When I quit Barrier
Is there a way to work around it? Yes, you can manually terminate Barrier with the task manager.
Does this bug prevent you from using Barrier entirely? No

Originally created by @MichaelMcDonnell on GitHub (Aug 21, 2019). Original GitHub issue: https://github.com/debauchee/barrier/issues/407 ### Operating Systems ### Server: Windows 10 Version 1809 ### Barrier Version ### 2.3.1-release ### Steps to reproduce bug ### 1. Install Barrier 2. Chose File->Quit 3. Open the task manager 4. Notice that barrierd is still running 5. Uninstall barrier in App & features 6. Notice that the "c:\Program Files\Barrier" folder is left over and barrierd.exe is in it. ### Other info ### * When did the problem start to occur? When I quit Barrier * Is there a way to work around it? Yes, you can manually terminate Barrier with the task manager. * Does this bug prevent you from using Barrier entirely? No

gitea-mirror added the

bug

installer/package

labels 2026-05-05 06:02:15 -06:00

gitea-mirror commented

2026-05-05 06:02:19 -06:00

Author

Owner

@noisyshape commented on GitHub (Aug 21, 2019):

barrierd.exe is the Barrier daemon which is managed as a Windows service. Running 24/7 is the intended behavior. The GUI process can't manage the service without running with admin privileges.

The problem with the uninstallation is that the service is stopped and deleted as the last step of uninstallation after the installed files are supposed to be removed. There's a related problem with reinstallation/upgrading. I'll take a look at some Inno Setup scripts for proper service management.

@noisyshape commented on GitHub (Aug 21, 2019): barrierd.exe is the Barrier daemon which is managed as a Windows service. Running 24/7 is the intended behavior. The GUI process can't manage the service without running with admin privileges. The problem with the uninstallation is that the service is stopped and deleted as the last step of uninstallation after the installed files are supposed to be removed. There's a related problem with reinstallation/upgrading. I'll take a look at some Inno Setup scripts for proper service management.

gitea-mirror commented

2026-05-05 06:02:20 -06:00

Author

Owner

@AdrianKoshka commented on GitHub (Aug 22, 2019):

Thank you @noisyshape! :)

@AdrianKoshka commented on GitHub (Aug 22, 2019): Thank you @noisyshape! :)

gitea-mirror commented

2026-05-05 06:02:22 -06:00

Author

Owner

@MichaelMcDonnell commented on GitHub (Aug 22, 2019):

Thanks @noisyshape! It surprises me that Barrier has to use a service. I thought that it would be able to function as long as it was running in the tray. That means there is no way to truly close Barrier without manually stopping the service?

@MichaelMcDonnell commented on GitHub (Aug 22, 2019): Thanks @noisyshape! It surprises me that Barrier has to use a service. I thought that it would be able to function as long as it was running in the tray. That means there is no way to truly close Barrier without manually stopping the service?

gitea-mirror commented

2026-05-05 06:02:24 -06:00

Author

Owner

@yume-chan commented on GitHub (Oct 5, 2021):

Related to #346

@yume-chan commented on GitHub (Oct 5, 2021): Related to #346

gitea-mirror referenced this issue

2026-05-05 07:57:30 -06:00

[PR #320] [MERGED] Build and Publish Release Mac version on Azure Pipelines #1606