Windows client will sometimes not delete the olm service properly

[Megax1234]

Describe the Bug

On occasion when connecting and then disconnecting from the Pangolin client, the olm service will fail to remove itself from services.exe. After this happens, the next time Pangolin tries to connect, it just constantly sits in a "registering" state. Any attempts to delete the service manually give an error saying the service is "marked for deletion". A reboot solves the issue and removes the service but having to do this repeatedly causes some loss of productivity.

I have also manually killed all Pangolin services with taskkill and from the Task Manager in Windows to try and resolve without a reboot.

Redacted log files will be pasted here:

pangolin-log-2026-05-28T130233.txt

The issue specifically happens before 9:35AM EST on 5/28 in the logs which is when my PC rebooted

Environment

• OS Type & Version: Microsoft Windows 11 Pro (25H2) Build 26200.8524
• Pangolin Version: 1.15.2 Community
• Gerbil Version: 1.3.0
• Traefik Version: 3.5.6
• Newt Version: 1.12.5
• Client Version: 0.10.3

To Reproduce

Unable to find specific steps to reproduce. After my PC has been on for some time and I disconnect and reconnect Pangolin multiple times, it seems to happen.

Expected Behavior

Disconnecting from Pangolin should fully remove the windows olm service and allow a new one to be created for proper connection to private resources

[AstralDestiny]

So you're connecting and when it doesn't connect you decide to instead attempt to delete the service over requesting a stop?

[Megax1234]

The service is stopped in Windows already when the issue happens and is also listed as "Disabled". I am just trying to get rid of the service in hopes that Pangolin will make a new one and allow me to connect.