Issue: "Error: Unable to connect to the elevated service." when using Admin By Request Tool from Windows Terminal

[JensGJ]

Issue Description

Gsudo works perfect both with Windows PowerShell (5.1.19041.1682) and PowerShell Core (7.2.5) - as long as they are running in their own windows. When running either of them through Windows Terminal, I get the error Unable to connect to the elevated service

Steps to Reproduce

1. Open Windows Terminal with either PowerShell 7 or PowerShell 5
2. Run gsudo
3. Error occurs

Screenshots

Context:

• Windows version: 10 (21H2, 19044.1766)
• gsudo version: gsudo v1.3.0 (Branch.master.Sha.24fb735f547e1e5dd7aa22fdd77777fa8c923a1c)
• We are using the Admin By Request Tool from FastTrack Software (https://www.adminbyrequest.com/).
  Opening for admin access in that tool before running gsudo does not make a difference (and outside Windows Terminal gsudo also works fine without the need for requesting admin access from Admin By Request).

[gerardog]

Hi,
I was able to reproduce this issue after installing Admin By Request Tool.
What I see is that when gsudo is run from WT, the Api call to System.Diagnostics.Process.Start does not returns after the elevated process is created. Instead, it waits until that process has ended. I believe this is a bug in Admin By Request Tool, not gsudo.
Let´s see how we can report this problem to them so we can work it out together.

[gerardog]

Tried to create a ticket to FastTrack Software, but unfortunately The free plan does not include support.
Do you have a paid plan?

[gerardog]

I was able to reproduce the problem taking gsudo out of the equation. So, this is caused by AdminByRequest, and not gsudo.

Please take a look at the screenshot. You will see that if you do Start-Process cmd.exe -Verb RunAs from PowerShell in a regular console, the new CMD stays open, while your original PowerShell console returns your control to you. If you do the same from a Windows Terminal, that PowerShell will hang until the new CMD is closed (it shouldn't).

I tweeted to @AdminByRequest. Let's hope they get the bug report.

[JensGJ]

Thanks a lot. I've forwarded the case to our support department - they should be able to make a ticket at AdminByRequest.
I've replicated your test and get the same result here - e.g. the issue is not related to gsudo.

[gerardog]

Just came here to rant about what a terrible uninstall experience that tool provides. It refuses to uninstall and provides no instructions. Also f*** up my user and removed admin rights from it, without even warning me. I just had a secondary admin account by chance, otherwise would have to hack myself to recover my machine.

I'm closing this issue since it is an external problem.

[JensGJ]

Thanks for the effort. We have a paid plan. I'll check if I can make a support ticket tomorrow. Best regards Jens Gyldenkærne Jensen Copenhagen Business School Fra: Gerardo Grignoli ***@***.***> Sendt: fredag den 24. juni 2022 01:21 Til: gerardog/gsudo ***@***.***> Cc: Jens Gyldenkærne Jensen ***@***.***>; Author ***@***.***> Emne: Re: [gerardog/gsudo] Issue: "Error: Unable to connect to the elevated service." when using Admin By Request Tool from Windows Terminal (Issue #141) Tried to create a ticket to FastTrack Software, but unfortunately The free plan does not include support. Do you have a paid plan? - Reply to this email directly, view it on GitHub<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgerardog%2Fgsudo%2Fissues%2F141%23issuecomment-1165004029&data=05%7C01%7C%7Ca4679c1e1aa84519026108da556efe70%7C875c414e5d004cdbb77adeae5d6ab201%7C1%7C0%7C637916232461519555%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=yNHRkvcfK4Y3DIXj5ZVihlAmKo05pPW%2Flo6gOc8S8GY%3D&reserved=0>, or unsubscribe<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAKGDGL4TQZFHVOGU4CD7XP3VQTWMTANCNFSM5ZT2SPKA&data=05%7C01%7C%7Ca4679c1e1aa84519026108da556efe70%7C875c414e5d004cdbb77adeae5d6ab201%7C1%7C0%7C637916232461519555%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=hPVPlszvh4SENaHkXPpimVmfs1Ezd2%2FOdFuAMLdqiPg%3D&reserved=0>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[gerardog]

Hi @JensGJ, did you had any luck reporting this to ABR? what was their response?

[JensGJ]

Hi Gerado. Long story short: The first time I reported the issue (on Windows 10), it was fixed with an update of Admin By Request. The second time - after upgrade to Windows 11 - was stuck in our local support since they were not able to reproduce the error. So unfortunately I don't use gsudo on my workstation. It works fine on our servers (but this is also without Admin By Request and without Windows Terminal). Med venlig hilsen Jens Gyldenkærne Jensen

[gerardog]

Thank you so much for your response Jens.