Error message "Cannot read executable filename for process with id" using PuTTY plugin

Questions Royal TS (for Windows)
1

Hi there,

I’m recently seeing the above mentioned error message when I’m trying to establish a connection via SSH using the PuTTY plugin. It shows different process IDs until it finally bails out after about 20 seconds and shows me with the Window Picker.

It is a fairly recent issue which has only started a couple of days ago.

Any ideas here?

image

2

Okay, so the process IDs in question were MMCs. I closed all of them, and the last process ID was Fujitsu’s DeskUpdate (the computer I’m using is a Fujitsu workstation). I closed that as well, and now I don’t receive any error message at all, just a the Window Picker after a short while. Very strange!

3

That’s weird. I’m not able to reproduce the issue. Can you reproduce it on a different machine as well?

4

Sorry for the late response. No, I couldn’t reproduce it because I didn’t h ave access to a different machine. However, the issue hasn’t resurfaced so far. So fingers crossed it was just a one-time incident, probably related to increased solar flare activity.

5

I see. Thanks for getting back. Please let me know if you see the issue again.

cheers,
Stefan

6

I can confirm this:

Cannot read executable filename for process with id 103272: Access denied

7

Looks like Royal tries to find the Putty session for embedding the terminal, and searches every process ID for its name. But thats only a uqualified guess from my side

8

We actually know the PuTTY process ID and we are looking for a specific window created by that process ID. We don’t pull in a window from a different/unknown process id.

9

Just updated to 5.2.60420. I see the same error here.

10

That’s weird. Are you running a Windows Insider build? Do you have some secuity/personal firewall tool installed which may interfere?

11

If I start Royal with Admin rights, the error message is gone, and its way quicker to embed the connection

12

Hmm, it looks like that the PuTTY executable is started elevated then but I have no clue how that’s even possible. Are you using the shipped PuTTY version included with Royal TS or are you using your own PuTTY from a specified path in the plugin settings?

13

Nope, plain Windows 10 Pro, Version 1903 - 18362.836. No securiy software except antivirus. Same error on another computer runing Windows 10 1803 (Busines)

14

Using shipped putty. Plugin - Terminal - putty has no modifications

15

Can you please check if the process started by Royal TS (when not started as admin/elevated) is elevated using the task manager:

https://winaero.com/blog/how-to-check-if-a-process-is-running-as-administrator-elevated-in-windows/#:~:text=Start%20Task%20Manager%20and%20switch,Elevated%22%2C%20and%20click%20OK.

16

Restarted Royal in non-elevated mode. See screenshot from task manager. Not elevated and error message is present.

image

17

So there seems to be a permission problem though. Unless you start Royal TS elevated, you are not able to access process information of a child process started by Royal TS. I’m honestly not sure how this can happen on your system’s. Maybe some policy? Is this a domain user logging on to a domain joined machine? Maybe you can try with a local user account?

18

This error comes both on a Business domain joined computer, and the one im using now, a private Win10 computer without any domain related settings. A standard login through a Microsoft account.

19

I too use a Microsoft account to log on to my machine but I can’t repro the issue. Any other tool/software which comes to mind?

20

is it possible that you are starting putty out of a onedrive folder?