gsudo staying open after using in Windows Terminal

[privacyguy123]

Title says it all - after closing Windows Terminal it's still showing as a running process on Windows 10.

[gerardog]

That would be the 'credentials cache'. It's the elevated gsudo instance that stays idle for 5 minutes in case you need to elevate again without UAC popup, but its limited to (only allows) the same caller process (WT). It should go away 5 minutes after the last gsudo command ended (if you created a gsudo profile, then that would be 5 minutes after you closed the tab). Let me know if it doesn't.

If you don't like the credentials cache you can disable it with gsudo config CredentialsCacheDuration 00:00:00 or any duration (HH:MM:SS).
In the upcoming v0.7 release you could also do gsudo -k to expedite the service closing (inspired in *nix sudo -k / sudo --reset-timestamp, or edit the profile to use gsudo --nocache cmd.

Nonetheless you gave me an idea: The credential cache could just detect that the allowed process (WT) has ended, and therefore end the service. Dully noted.

[privacyguy123]

Thanks! Appreciate the quick & in depth reply.