No R versions are being discovered when creating a "New folder from template"

[njaques1227]

I have been trying to find a solution for this on the web and with the help of AI, but I have been unable to find it. R is installed on my computer; however, when I try to create a "New folder with template", the R version does not appear, and so I cannot create the folder.

After waiting for than a few minutes, nothing is showing up. I have shut down the program and restarted my computer, and still it doesn’t change.

As you can see in the picture, R is being used in Positron, and I have been able to run commands in the editor window (opening an R file works for me).

What else should I be looking at?

[juliasilge]

Can you share the logs from the "R Language Pack" output channel, to see what is happening with R discovery?

I can't quite see in your screenshot if the R console is up and healthy? I see that R 4.5.2 is the active interpreter session, but can you also say whether your console is working correctly?

[njaques1227]

Hi @juliasilge

I just did some simple commands. It appears that the console is working.

Below is the output results. Ignore the Problem alert. That was for something else

[juliasilge]

• What happens if you manually run the command Interpreter: Discover All Interpreters? Does it hang or complete without error?
• What happens if you run Workspaces: Manage Workspace Trust? Does it show that your workspace is trusted? (Runtime discovery can't run if it isn't)
• Can you check the developer tools console for any log messages that start with "[Runtime startup]" or "[New Folder Flow]"?

[njaques1227]

When I run Interpreter: Discover All Interpreters, I get this error

Even though it says that R is active here

When I run Workspaces: Manage Workspace Trust, it shows that the R file is trusted as well as my other working directories

When I looked up Developer: Toggle Developer Tools, there were no errors that started with "[Runtime startup]"

but when I typed in "[New Folder Flow]" I got the follow error message

[juliasilge]

Can you open these logs directly (you can do it from the three dots here via "Open Output in Editor") and then paste the logs as text?

[ray-lucio]

Here you go:

2026-05-28 17:01:54.055 [info] Log level: Info 2026-05-28 17:01:54.055 [info] Refreshing testthat status 2026-05-28 17:01:54.055 [info] Not working in an R package 2026-05-28 17:01:54.055 [info] Context key 'testthatIsConfigured' is 'false' 2026-05-28 17:01:54.055 [info] Context key 'testthatHasTests' is 'false' 2026-05-28 17:01:54.055 [info] Default R interpreter path specified in 'positron.r.interpreters.default': C:\Users\Raymond.Lucio\AppData\Local\Programs\R\R-4.6.0\bin\x64\R.exe 2026-05-28 17:01:54.055 [info] [recommendedWorkspaceRuntime] Recommending R runtime from 'positron.r.interpreters.default' setting: C:\Users\Raymond.Lucio\AppData\Local\Programs\R\R-4.6.0\bin\x64\R.exe 2026-05-28 17:01:54.056 [info] Candidate R binary at C:\Users\Raymond.Lucio\AppData\Local\Programs\R\R-4.6.0\bin\x64\R.exe 2026-05-28 17:01:54.056 [info] Default R interpreter path specified in 'positron.r.interpreters.default': C:\Users\Raymond.Lucio\AppData\Local\Programs\R\R-4.6.0\bin\x64\R.exe 2026-05-28 17:01:54.056 [info] R installation discovered: { "usable": true, "supported": true, "reasonDiscovered": [ "Found in a location specified via user settings" ], "reasonRejected": null, "binpath": "C:\\Users\\Raymond.Lucio\\AppData\\Local\\Programs\\R\\R-4.6.0\\bin\\x64\\R.exe", "homepath": "C:\\Users\\Raymond.Lucio\\AppData\\Local\\Programs\\R\\R-4.6.0", "semVersion": { "options": {}, "loose": false, "includePrerelease": false, "raw": "4.6.0", "major": 4, "minor": 6, "patch": 0, "prerelease": [], "build": [], "version": "4.6.0" }, "version": "4.6.0", "arch": "x86_64", "current": false, "orthogonal": true, "default": true } 2026-05-28 17:01:54.873 [info] Registry key HKEY_CURRENT_USER\SOFTWARE\R-core\R64\InstallPath reports the current R installation is at C:\Users\Raymond.Lucio\AppData\Local\Programs\R\R-4.6.0 2026-05-28 17:01:54.873 [info] Identified the current R binary: C:\Users\Raymond.Lucio\AppData\Local\Programs\R\R-4.6.0\bin\x64\R.exe 2026-05-28 17:01:56.261 [info] Possibly found R on PATH: C:\Users\Raymond.Lucio\AppData\Local\Programs\R\R-4.6.0\bin\x64\R.EXE. 2026-05-28 17:01:56.261 [info] Resolved R binary at C:\Users\Raymond.Lucio\AppData\Local\Programs\R\R-4.6.0\bin\x64\R.exe. 2026-05-28 17:01:56.355 [info] Registry key HKEY_CURRENT_USER\SOFTWARE\R-core\R64\4.6.0\InstallPath reports an R installation at C:\Users\Raymond.Lucio\AppData\Local\Programs\R\R-4.6.0 2026-05-28 17:01:56.356 [info] Ignoring ad hoc R binary /usr/bin/R because it does not exist. 2026-05-28 17:01:56.357 [info] Ignoring ad hoc R binary /usr/local/bin/R because it does not exist. 2026-05-28 17:01:56.357 [info] Ignoring ad hoc R binary /opt/local/bin/R because it does not exist. 2026-05-28 17:01:56.357 [info] Ignoring ad hoc R binary /opt/homebrew/bin/R because it does not exist. 2026-05-28 17:01:56.368 [info] Candidate R binary at C:\Users\Raymond.Lucio\AppData\Local\Programs\R\R-4.6.0\bin\x64\R.exe 2026-05-28 17:01:56.368 [info] Default R interpreter path specified in 'positron.r.interpreters.default': C:\Users\Raymond.Lucio\AppData\Local\Programs\R\R-4.6.0\bin\x64\R.exe 2026-05-28 17:01:56.368 [info] R installation discovered: { "usable": true, "supported": true, "reasonDiscovered": [ "Found in Windows registry", "Found in PATH, via the whichcommand", "Found in the primary location for R versions on this operating system" ], "reasonRejected": null, "binpath": "C:\\Users\\Raymond.Lucio\\AppData\\Local\\Programs\\R\\R-4.6.0\\bin\\x64\\R.exe", "homepath": "C:\\Users\\Raymond.Lucio\\AppData\\Local\\Programs\\R\\R-4.6.0", "semVersion": { "options": {}, "loose": false, "includePrerelease": false, "raw": "4.6.0", "major": 4, "minor": 6, "patch": 0, "prerelease": [], "build": [], "version": "4.6.0" }, "version": "4.6.0", "arch": "x86_64", "current": true, "orthogonal": true, "default": true }

[juliasilge]

Thanks, @ray-lucio! That's very interesting that you can see Python interpreters but not R in the failing folders.

Can you open one of the folders where Python starts but R doesn't, and look to see if you have any settings for that folder? You can do that from the command palette with Preferences: Open Workspace Settings (JSON). Do you see anything there, such as interpreters.startupBehavior settings? R interpreters and Python interpreters register independently, and there is a per-language interpreters.startupBehavior setting that, when set to "Disabled" for a language, prevents that language's interpreters from registering at all. Because this setting can be set per-language and per-folder (in a folder's .vscode/settings.json), it could explain what you are seeing: R disabled in some folders, Python unaffected, and "Discover All Interpreters" doing nothing because re-discovery just re-attempts the blocked registration. The setting stops the interpreter from starting but not from being discovered.

Another thing to check would be, with that folder open, open the Command Palette and run "Developer: Toggle Developer Tools", go to the Console tab, and search for is disabled. If this is the cause, you should see a line like: Attempt to register language runtime ... but language 'r' is disabled. While you are there, could you also search for [Runtime startup] and paste those lines? That tells us how far startup got.

[ray-lucio]

I looked at two different folders, and had the same results:

The JSON is empty.

No results showed when searching for "is disabled".

Runtime startup results:
workbench.desktop.main.js:22156 ERR [Runtime startup] Error starting affiliated runtimes:
Error: spawn EPERM

error @ workbench.desktop.main.js:22156

[juliasilge]

Thanks for sticking with this, @ray-lucio! The logs you shared are actually really useful. They show that R 4.6.0 is being discovered just fine ("usable": true, "supported": true), so this isn't a discovery problem. I am now wondering if this line from the developer tools console might help us dig into what's going on:

[Runtime startup] Error starting affiliated runtimes: Error: spawn EPERM

spawn EPERM means Windows is refusing to launch the R kernel process (ark.exe). That fits what you're seeing: R is found, but it can't actually start, so the console ends up in the "No interpreters found" state. It's telling that Python works in the same folders, because Python and R share the same supervisor process. The difference is the R kernel binary (ark.exe), which lives inside Positron's extension folder (a user-writable location), whereas your Python kernel runs from a more "trusted" install location. Corporate security tooling (AppLocker, WDAC, or some antivirus/EDR products) commonly blocks execution of programs from user-writable paths, which would produce exactly this error.

A few things that would help me confirm and narrow it down:

1. Kernel Supervisor logs. With a failing folder open, open the Output panel and switch the dropdown to "Kernel Supervisor" (and also grab "R Language Pack" again). Could you paste the text from around the time you try to start R? That log shows the exact command and the full path to ark.exe.

2. Is execution policy in play? Do you know if your machine has AppLocker, WDAC, or managed antivirus/EDR? A quick test: find ark.exe inside the Positron install (it'll be under a path like ...\resources\app\extensions\positron-r\resources\ark\), and try running it directly from a terminal (ark.exe --version). If you get "blocked by group policy" or "Access is denied," that confirms it.

3. Where do the folders live? For the folders where R fails vs. the ones where it works, are they local (e.g. C:\Users\...), in OneDrive, or on a network/mapped drive? The working directory we hand to the kernel can also trigger this kind of block, so the location difference may matter.

4. What exactly does the picker show? When you say you only see Python, is R completely absent from the interpreter list, or is it listed but fails when you try to select it?

Once we have the supervisor log and know whether execution is being blocked, we hopefully will be able to pin this down! 🤞

[ray-lucio]

1. Kernel Supervisor logs.

2026-06-01 10:30:29.826 [info] 15:30:28 [Positron] Kallichore server PID 17720 is not running
2026-06-01 10:30:29.826 [info] 15:30:28 [Positron] Could not reconnect to Kallichore server at npipe:\\.\pipe\kallichore-17720. Starting a new server
2026-06-01 10:30:29.826 [info] 15:30:28 [Positron] Generated connection file path: C:\Users\RAYMON~1.LUC\AppData\Local\Temp\kallichore-5a31fa47-29256.json
2026-06-01 10:30:29.826 [info] 15:30:28 [Positron] Using named pipe transport
2026-06-01 10:30:29.826 [info] 15:30:28 [Positron] Starting Kallichore server c:\Program Files\Positron\resources\app\extensions\positron-supervisor\resources\kallichore\kcserver.exe with connection file C:\Users\RAYMON~1.LUC\AppData\Local\Temp\kallichore-5a31fa47-29256.json and 15000ms startup timeout
2026-06-01 10:30:29.827 [info] 15:30:29 [Positron] Kallichore terminal started in 876ms with PID 33928
15:31:01 [Positron] Connection file was not created after 31701ms; output:

"c:\Program Files\Positron\resources\app\extensions\positron-supervisor\resources\kallichore\kcserver.exe" --log-level debug --log-file C:\Users\RAYMON~1.LUC\AppData\Local\Temp\kallichore-5a31fa47-29256.log --connection-file C:\Users\RAYMON~1.LUC\AppData\Local\Temp\kallichore-5a31fa47-29256.json --resource-sample-interval 1000 --transport named-pipe --idle-shutdown-hours 1
15:30:30 �[0m�[34m[INFO] �[0mUsing named pipe: \\.\pipe\kallichore-31988
Listening on named pipe: \\.\pipe\kallichore-31988

  ,            _   _           _
 /|   /       | | | | o       | |
  |__/   __,  | | | |     __  | |     __   ,_    _
  | \   /  |  |/  |/  |  /    |/ \   /  \_/  |  |/
  |  \_/\_/|_/|__/|__/|_/\___/|   |_/\__/    |_/|__/
  A Jupyter Kernel supervisor. Version 0.1.64.
  Copyright (c) 2026, Posit Software PBC. All rights reserved.

15:30:30 �[0m�[34m[INFO] �[0mWrote connection details to C:\Users\RAYMON~1.LUC\AppData\Local\Temp\kallichore-5a31fa47-29256.json
15:30:30 �[0m�[36m[DEBUG] �[0m(1) kcserver: Starting Kallichore
15:30:30 �[0m�[34m[INFO] �[0mStarting global resource monitor with 1000ms interval
15:30:30 �[0m�[34m[INFO] �[0mServer set to shut down after 1 hours of inactivity
15:30:30 �[0m�[34m[INFO] �[0mStarting named pipe HTTP server on: \\.\pipe\kallichore-31988

15:31:01 [Positron] Failed to start Kallichore server: Error: Connection file was not created after 31701ms; output:

"c:\Program Files\Positron\resources\app\extensions\positron-supervisor\resources\kallichore\kcserver.exe" --log-level debug --log-file C:\Users\RAYMON~1.LUC\AppData\Local\Temp\kallichore-5a31fa47-29256.log --connection-file C:\Users\RAYMON~1.LUC\AppData\Local\Temp\kallichore-5a31fa47-29256.json --resource-sample-interval 1000 --transport named-pipe --idle-shutdown-hours 1
15:30:30 �[0m�[34m[INFO] �[0mUsing named pipe: \\.\pipe\kallichore-31988
Listening on named pipe: \\.\pipe\kallichore-31988

  ,            _   _           _
 /|   /       | | | | o       | |
  |__/   __,  | | | |     __  | |     __   ,_    _
  | \   /  |  |/  |/  |  /    |/ \   /  \_/  |  |/
  |  \_/\_/|_/|__/|__/|_/\___/|   |_/\__/    |_/|__/
  A Jupyter Kernel supervisor. Version 0.1.64.
  Copyright (c) 2026, Posit Software PBC. All rights reserved.

15:30:30 �[0m�[34m[INFO] �[0mWrote connection details to C:\Users\RAYMON~1.LUC\AppData\Local\Temp\kallichore-5a31fa47-29256.json
15:30:30 �[0m�[36m[DEBUG] �[0m(1) kcserver: Starting Kallichore
15:30:30 �[0m�[34m[INFO] �[0mStarting global resource monitor with 1000ms interval
15:30:30 �[0m�[34m[INFO] �[0mServer set to shut down after 1 hours of inactivity
15:30:30 �[0m�[34m[INFO] �[0mStarting named pipe HTTP server on: \\.\pipe\kallichore-31988

15:31:05 [Positron] Kallichore server PID 17720 is not running
15:31:05 [Positron] Could not reconnect to Kallichore server at npipe:\\.\pipe\kallichore-17720. Starting a new server
15:31:05 [Positron] Generated connection file path: C:\Users\RAYMON~1.LUC\AppData\Local\Temp\kallichore-5b11c830-29256.json
15:31:05 [Positron] Using named pipe transport
15:31:05 [Positron] Starting Kallichore server c:\Program Files\Positron\resources\app\extensions\positron-supervisor\resources\kallichore\kcserver.exe with connection file C:\Users\RAYMON~1.LUC\AppData\Local\Temp\kallichore-5b11c830-29256.json and 15000ms startup timeout
15:31:06 [Positron] Kallichore terminal started in 247ms with PID 33740
15:31:06 [Positron] Read named pipe connection information from C:\Users\RAYMON~1.LUC\AppData\Local\Temp\kallichore-5b11c830-29256.json: \\.\pipe\kallichore-30436, constructed base path: http://npipe:\\.\pipe\kallichore-30436:
15:31:06 [Positron] Kallichore 0.1.64 server online with 0 sessions
15:31:06 [Positron] Running as pid 30436 (terminal pid 33740)
15:31:06 [Positron] Kallichore server started in 256ms
15:31:06 [Positron] Streaming Kallichore server logs from C:\Users\RAYMON~1.LUC\AppData\Local\Temp\kallichore-5b11c830-29256.log (log level: debug)
15:31:06 [INFO] Using named pipe: \\.\pipe\kallichore-30436
15:31:06 [INFO] Wrote connection details to C:\Users\RAYMON~1.LUC\AppData\Local\Temp\kallichore-5b11c830-29256.json
15:31:06 [DEBUG] (1) kcserver: Starting Kallichore
15:31:06 [INFO] Starting global resource monitor with 1000ms interval
15:31:06 [INFO] Server set to shut down after 1 hours of inactivity
15:31:06 [INFO] Starting named pipe HTTP server on: \\.\pipe\kallichore-30436
15:31:06 [INFO] Client connected to named pipe: \\.\pipe\kallichore-30436
15:31:06 [Positron] Creating session: {"sessionId":"python-f2fb1ae6","sessionMode":"console","createdTimestamp":1780327862277,"startReason":"Affiliated Python runtime for workspace"}
15:31:06 [INFO] Client connected to named pipe: \\.\pipe\kallichore-30436
15:31:06 [INFO] new_session("python-f2fb1ae6") - X-Span-ID: "5157b273-8992-4cd2-a591-a1c47b1250c1"
15:31:06 [DEBUG] (2) kcserver::server: Created log file for session python-f2fb1ae6 at "C:\\Users\\RAYMON~1.LUC\\AppData\\Local\\Temp\\kernel_log_python-f2fb1ae6.txt"
15:31:06 [DEBUG] (2) kcserver::kernel_session::environment: Created interrupt event with handle: 676
15:31:06 [INFO] Client connected to named pipe: \\.\pipe\kallichore-30436
15:31:06 [INFO] start_session("python-f2fb1ae6") - X-Span-ID: "94ba5896-6720-47b7-a514-e564e2496d61"
15:31:06 [WARN] [session python-f2fb1ae6] startup_environment_arg specified but startup_environment is None (ignored)
15:31:06 [DEBUG] (2) kcserver::kernel_state: [session python-f2fb1ae6] status 'idle' => 'starting' (start API called)
15:31:06 [DEBUG] (2) kcserver::kernel_session::startup: Wrote connection file for session python-f2fb1ae6 at "C:\\Users\\RAYMON~1.LUC\\AppData\\Local\\Temp\\connection_python-f2fb1ae6.json"
15:31:06 [DEBUG] (2) kcserver::kernel_session: Starting kernel for session python-f2fb1ae6: ["C:\\Users\\Raymond.Lucio\\OneDrive - Asurion\\data_science\\atc\\registration_and_churn_research\\20260413_refresh\\automation_files\\python_version\\.venv\\Scripts\\python.exe", "c:\\Program Files\\Positron\\resources\\app\\extensions\\positron-python\\python_files\\posit\\positron_language_server.py", "-f", "C:\\Users\\RAYMON~1.LUC\\AppData\\Local\\Temp\\connection_python-f2fb1ae6.json", "--logfile", "C:\\Users\\RAYMON~1.LUC\\AppData\\Local\\Temp\\kernel-IGyipU\\kernel.log", "--loglevel=error", "--session-mode=console"]
15:31:25 [INFO] [session python-f2fb1ae6] Connected to heartbeat socket at tcp://127.0.0.1:59654.
15:31:25 [INFO] [session python-f2fb1ae6] Received initial heartbeat from kernel
15:31:25 [DEBUG] (16) kcserver::zmq_ws_proxy: [session python-f2fb1ae6] Starting ZeroMQ-WebSocket proxy
15:31:25 [INFO] Client connected to named pipe: \\.\pipe\kallichore-30436
15:31:25 [INFO] upgrade to websocket: python-f2fb1ae6
15:31:25 [INFO] channels_upgrade: using named pipes for session python-f2fb1ae6
15:31:25 [INFO] create_named_pipe_channel: starting for session python-f2fb1ae6
15:31:25 [INFO] Creating named pipe for session 'python-f2fb1ae6' at \\.\pipe\kallichore-1ece57b8ebf1477ca7c88688e964994d
15:31:25 [INFO] create_named_pipe_channel: returning path \\.\pipe\kallichore-1ece57b8ebf1477ca7c88688e964994d for session python-f2fb1ae6
15:31:25 [INFO] Named pipe handler started for \\.\pipe\kallichore-1ece57b8ebf1477ca7c88688e964994d and session python-f2fb1ae6
15:31:25 [INFO] Named pipe server created successfully: \\.\pipe\kallichore-1ece57b8ebf1477ca7c88688e964994d
15:31:25 [INFO] Client connected to named pipe: \\.\pipe\kallichore-1ece57b8ebf1477ca7c88688e964994d
15:31:25 [INFO] [client python-f2fb1ae6-0] Handling named pipe connection with WebSocket protocol for session python-f2fb1ae6
15:31:25 [DEBUG] (8) kcserver::client_session: [client python-f2fb1ae6-0] Detected WebSocket handshake request on named pipe
15:31:25 [DEBUG] (8) kcserver::client_session: [client python-f2fb1ae6-0] Sent WebSocket handshake response on named pipe
15:31:25 [INFO] [client python-f2fb1ae6-0] Successfully created WebSocket stream from named pipe (with handshake)
15:31:25 [INFO] [client python-f2fb1ae6-0] Connecting to websocket
15:31:25 [INFO] [client python-f2fb1ae6-0] Got message 837d2ccf of type execute_request; sending to Jupyter socket Shell
15:31:25 [INFO] [client python-f2fb1ae6-0] Got message 96bfb8be5f of type comm_open; sending to Jupyter socket Shell
15:31:25 [DEBUG] (8) kcserver::zmq_ws_proxy: [session python-f2fb1ae6] Forward from 'IOPub' to WebSocket: status
15:31:25 [DEBUG] (8) kcserver::kernel_state: [session python-f2fb1ae6] status 'starting' => 'busy' (execute_request)
15:31:25 [INFO] [client python-f2fb1ae6-0] Got message 8804cb3b8c of type comm_open; sending to Jupyter socket Shell
15:31:25 [INFO] [client python-f2fb1ae6-0] Got message a31d537b4c of type comm_info_request; sending to Jupyter socket Shell
15:31:25 [INFO] [client python-f2fb1ae6-0] Got message be7367bb-e0b8-4161-9d41-28cc781c7917 of type comm_msg; sending to Jupyter socket Shell
15:31:25 [INFO] [client python-f2fb1ae6-0] Got message 7177e4b4dc of type comm_info_request; sending to Jupyter socket Shell
15:31:25 [INFO] [client python-f2fb1ae6-0] Got message 56a81d0985 of type comm_info_request; sending to Jupyter socket Shell
15:31:25 [DEBUG] (8) kcserver::zmq_ws_proxy: [session python-f2fb1ae6] Forward from 'IOPub' to WebSocket: status
15:31:25 [DEBUG] (8) kcserver::kernel_state: [session python-f2fb1ae6] status 'busy' => 'idle' (execute_request)
15:31:25 [DEBUG] (14) kcserver::zmq_ws_proxy: [session python-f2fb1ae6] Forward from 'Shell' to WebSocket: execute_reply
15:31:25 [DEBUG] (8) kcserver::zmq_ws_proxy: [session python-f2fb1ae6] Forward from 'IOPub' to WebSocket: status
15:31:25 [DEBUG] (8) kcserver::kernel_state: [session python-f2fb1ae6] status 'idle' => 'busy' (comm_open)
15:31:25 [DEBUG] (8) kcserver::zmq_ws_proxy: [session python-f2fb1ae6] Forward from 'IOPub' to WebSocket: comm_msg
15:31:25 [DEBUG] (8) kcserver::zmq_ws_proxy: [session python-f2fb1ae6] Forward from 'IOPub' to WebSocket: status
15:31:25 [DEBUG] (8) kcserver::kernel_state: [session python-f2fb1ae6] status 'busy' => 'idle' (comm_open)
15:31:25 [DEBUG] (8) kcserver::zmq_ws_proxy: [session python-f2fb1ae6] Forward from 'IOPub' to WebSocket: status
15:31:25 [DEBUG] (8) kcserver::kernel_state: [session python-f2fb1ae6] status 'idle' => 'busy' (comm_open)
15:31:25 [DEBUG] (16) kcserver::zmq_ws_proxy: [session python-f2fb1ae6] Forward from 'IOPub' to WebSocket: comm_msg
15:31:25 [DEBUG] (16) kcserver::zmq_ws_proxy: [session python-f2fb1ae6] Forward from 'IOPub' to WebSocket: status
15:31:25 [DEBUG] (16) kcserver::kernel_state: [session python-f2fb1ae6] status 'busy' => 'idle' (comm_open)
15:31:25 [DEBUG] (8) kcserver::zmq_ws_proxy: [session python-f2fb1ae6] Forward from 'IOPub' to WebSocket: status
15:31:25 [DEBUG] (8) kcserver::kernel_state: [session python-f2fb1ae6] status 'idle' => 'busy' (comm_info_request)
15:31:25 [DEBUG] (8) kcserver::zmq_ws_proxy: [session python-f2fb1ae6] Forward from 'IOPub' to WebSocket: status
15:31:25 [DEBUG] (8) kcserver::kernel_state: [session python-f2fb1ae6] status 'busy' => 'idle' (comm_info_request)
15:31:25 [DEBUG] (8) kcserver::zmq_ws_proxy: [session python-f2fb1ae6] Forward from 'Shell' to WebSocket: comm_info_reply
15:31:25 [DEBUG] (14) kcserver::zmq_ws_proxy: [session python-f2fb1ae6] Forward from 'IOPub' to WebSocket: status
15:31:25 [DEBUG] (14) kcserver::kernel_state: [session python-f2fb1ae6] status 'idle' => 'busy' (comm_msg)
15:31:25 [DEBUG] (14) kcserver::zmq_ws_proxy: [session python-f2fb1ae6] Forward from 'IOPub' to WebSocket: status
15:31:25 [DEBUG] (14) kcserver::kernel_state: [session python-f2fb1ae6] status 'busy' => 'idle' (comm_msg)
15:31:25 [DEBUG] (16) kcserver::zmq_ws_proxy: [session python-f2fb1ae6] Forward from 'IOPub' to WebSocket: status
15:31:25 [DEBUG] (16) kcserver::kernel_state: [session python-f2fb1ae6] status 'idle' => 'busy' (comm_info_request)
15:31:25 [DEBUG] (16) kcserver::zmq_ws_proxy: [session python-f2fb1ae6] Forward from 'Shell' to WebSocket: comm_info_reply
15:31:25 [DEBUG] (16) kcserver::zmq_ws_proxy: [session python-f2fb1ae6] Forward from 'IOPub' to WebSocket: status
15:31:25 [DEBUG] (16) kcserver::kernel_state: [session python-f2fb1ae6] status 'busy' => 'idle' (comm_info_request)
15:31:25 [DEBUG] (16) kcserver::zmq_ws_proxy: [session python-f2fb1ae6] Forward from 'IOPub' to WebSocket: status
15:31:25 [DEBUG] (16) kcserver::kernel_state: [session python-f2fb1ae6] status 'idle' => 'busy' (comm_info_request)
15:31:25 [DEBUG] (14) kcserver::zmq_ws_proxy: [session python-f2fb1ae6] Forward from 'IOPub' to WebSocket: status
15:31:25 [DEBUG] (14) kcserver::kernel_state: [session python-f2fb1ae6] status 'busy' => 'idle' (comm_info_request)
15:31:25 [DEBUG] (14) kcserver::zmq_ws_proxy: [session python-f2fb1ae6] Forward from 'Shell' to WebSocket: comm_info_reply
15:31:25 [INFO] [client python-f2fb1ae6-0] Got message 81f11d79 of type comm_msg; sending to Jupyter socket Shell
15:31:25 [DEBUG] (16) kcserver::zmq_ws_proxy: [session python-f2fb1ae6] Forward from 'IOPub' to WebSocket: status
15:31:25 [DEBUG] (16) kcserver::kernel_state: [session python-f2fb1ae6] status 'idle' => 'busy' (comm_msg)
15:31:25 [DEBUG] (16) kcserver::zmq_ws_proxy: [session python-f2fb1ae6] Forward from 'IOPub' to WebSocket: comm_msg
15:31:25 [DEBUG] (16) kcserver::zmq_ws_proxy: [session python-f2fb1ae6] Forward from 'IOPub' to WebSocket: status
15:31:25 [DEBUG] (16) kcserver::kernel_state: [session python-f2fb1ae6] status 'busy' => 'idle' (comm_msg)
15:31:25 [INFO] [client python-f2fb1ae6-0] Got message 5c7a516c39 of type comm_open; sending to Jupyter socket Shell
15:31:25 [DEBUG] (14) kcserver::zmq_ws_proxy: [session python-f2fb1ae6] Forward from 'IOPub' to WebSocket: status
15:31:25 [DEBUG] (14) kcserver::kernel_state: [session python-f2fb1ae6] status 'idle' => 'busy' (comm_open)
15:31:25 [DEBUG] (14) kcserver::zmq_ws_proxy: [session python-f2fb1ae6] Forward from 'IOPub' to WebSocket: status
15:31:25 [DEBUG] (14) kcserver::kernel_state: [session python-f2fb1ae6] status 'busy' => 'idle' (comm_open)
15:31:25 [INFO] Client connected to named pipe: \\.\pipe\kallichore-30436
15:31:25 [INFO] get_session("python-f2fb1ae6") - X-Span-ID: "75117108-0b0c-4e70-ada0-cfbe9b37c5a4"
15:31:26 [INFO] [client python-f2fb1ae6-0] Got message d0f9cc71c3 of type comm_open; sending to Jupyter socket Shell
15:31:26 [DEBUG] (14) kcserver::zmq_ws_proxy: [session python-f2fb1ae6] Forward from 'IOPub' to WebSocket: status
15:31:26 [DEBUG] (14) kcserver::kernel_state: [session python-f2fb1ae6] status 'idle' => 'busy' (comm_open)
15:31:26 [DEBUG] (14) kcserver::zmq_ws_proxy: [session python-f2fb1ae6] Forward from 'IOPub' to WebSocket: status
15:31:26 [DEBUG] (14) kcserver::kernel_state: [session python-f2fb1ae6] status 'busy' => 'idle' (comm_open)
15:31:26 [DEBUG] (14) kcserver::zmq_ws_proxy: [session python-f2fb1ae6] Forward from 'IOPub' to WebSocket: comm_msg
16:31:26 [DEBUG] (8) kcserver::server: Idle timeout: checking for idle sessions (1 to check)
16:31:26 [DEBUG] (8) kcserver::server: Session python-f2fb1ae6 has an active connection; server is not idle
17:17:00 [Positron] Session 'python-f2fb1ae6' disconnected while in state 'idle'. This is unexpected; checking server status.
17:17:00 [Positron] Kallichore server PID 30436 is still running
17:17:00 [Positron] The server is still running; attempting to reconnect to session python-f2fb1ae6
17:17:00 [WARN] [client python-f2fb1ae6-0] Lost connection with client; websocket pong counter is behind by 4 pings
17:17:01 [Positron] Successfully restored connection to  python-f2fb1ae6
17:17:01 [INFO] Client connected to named pipe: \\.\pipe\kallichore-30436
17:17:01 [INFO] upgrade to websocket: python-f2fb1ae6
17:17:01 [INFO] channels_upgrade: using named pipes for session python-f2fb1ae6
17:17:01 [INFO] create_named_pipe_channel: starting for session python-f2fb1ae6
17:17:01 [INFO] Creating named pipe for session 'python-f2fb1ae6' at \\.\pipe\kallichore-9a04eb624edc4534a5413a9de0482e30
17:17:01 [INFO] create_named_pipe_channel: returning path \\.\pipe\kallichore-9a04eb624edc4534a5413a9de0482e30 for session python-f2fb1ae6
17:17:01 [INFO] Named pipe handler started for \\.\pipe\kallichore-9a04eb624edc4534a5413a9de0482e30 and session python-f2fb1ae6
17:17:01 [INFO] Named pipe server created successfully: \\.\pipe\kallichore-9a04eb624edc4534a5413a9de0482e30
17:17:01 [INFO] Client connected to named pipe: \\.\pipe\kallichore-9a04eb624edc4534a5413a9de0482e30
17:17:01 [INFO] [client python-f2fb1ae6-1] Handling named pipe connection with WebSocket protocol for session python-f2fb1ae6
17:17:01 [DEBUG] (14) kcserver::client_session: [client python-f2fb1ae6-1] Detected WebSocket handshake request on named pipe
17:17:01 [DEBUG] (14) kcserver::client_session: [client python-f2fb1ae6-1] Sent WebSocket handshake response on named pipe
17:17:01 [INFO] [client python-f2fb1ae6-1] Successfully created WebSocket stream from named pipe (with handshake)
17:17:01 [INFO] [client python-f2fb1ae6-1] Connecting to websocket
18:06:02 [Positron] Session 'python-f2fb1ae6' disconnected while in state 'idle'. This is unexpected; checking server status.
18:06:02 [Positron] Kallichore server PID 30436 is still running
18:06:02 [Positron] The server is still running; attempting to reconnect to session python-f2fb1ae6
18:06:02 [Positron] Successfully restored connection to  python-f2fb1ae6
18:06:02 [WARN] [client python-f2fb1ae6-1] Lost connection with client; websocket pong counter is behind by 4 pings
18:06:02 [INFO] Client connected to named pipe: \\.\pipe\kallichore-30436
18:06:02 [INFO] upgrade to websocket: python-f2fb1ae6
18:06:02 [INFO] channels_upgrade: using named pipes for session python-f2fb1ae6
18:06:02 [INFO] create_named_pipe_channel: starting for session python-f2fb1ae6
18:06:02 [INFO] Creating named pipe for session 'python-f2fb1ae6' at \\.\pipe\kallichore-cbea4039d96d452ebdfa7e8cf816e7ab
18:06:02 [INFO] create_named_pipe_channel: returning path \\.\pipe\kallichore-cbea4039d96d452ebdfa7e8cf816e7ab for session python-f2fb1ae6
18:06:02 [INFO] Named pipe handler started for \\.\pipe\kallichore-cbea4039d96d452ebdfa7e8cf816e7ab and session python-f2fb1ae6
18:06:02 [INFO] Named pipe server created successfully: \\.\pipe\kallichore-cbea4039d96d452ebdfa7e8cf816e7ab
18:06:02 [INFO] Client connected to named pipe: \\.\pipe\kallichore-cbea4039d96d452ebdfa7e8cf816e7ab
18:06:02 [INFO] [client python-f2fb1ae6-2] Handling named pipe connection with WebSocket protocol for session python-f2fb1ae6
18:06:02 [DEBUG] (13) kcserver::client_session: [client python-f2fb1ae6-2] Detected WebSocket handshake request on named pipe
18:06:02 [DEBUG] (13) kcserver::client_session: [client python-f2fb1ae6-2] Sent WebSocket handshake response on named pipe
18:06:02 [INFO] [client python-f2fb1ae6-2] Successfully created WebSocket stream from named pipe (with handshake)
18:06:02 [INFO] [client python-f2fb1ae6-2] Connecting to websocket
18:10:46 [INFO] [client python-f2fb1ae6-2] Got message b7d1e34e of type comm_msg; sending to Jupyter socket Shell
18:10:46 [DEBUG] (16) kcserver::zmq_ws_proxy: [session python-f2fb1ae6] Forward from 'IOPub' to WebSocket: status
18:10:46 [DEBUG] (16) kcserver::kernel_state: [session python-f2fb1ae6] status 'idle' => 'busy' (comm_msg)
18:10:46 [DEBUG] (16) kcserver::zmq_ws_proxy: [session python-f2fb1ae6] Forward from 'IOPub' to WebSocket: comm_msg
18:10:46 [DEBUG] (16) kcserver::zmq_ws_proxy: [session python-f2fb1ae6] Forward from 'IOPub' to WebSocket: status
18:10:46 [DEBUG] (16) kcserver::kernel_state: [session python-f2fb1ae6] status 'busy' => 'idle' (comm_msg)

R languages pack

2026-06-01 10:31:02.318 [info] Log level: Info
2026-06-01 10:31:02.319 [info] Refreshing testthat status
2026-06-01 10:31:02.319 [info] Not working in an R package
2026-06-01 10:31:02.319 [info] Context key 'testthatIsConfigured' is 'false'
2026-06-01 10:31:02.319 [info] Context key 'testthatHasTests' is 'false'
2026-06-01 10:31:25.073 [info] Registry key HKEY_CURRENT_USER\SOFTWARE\R-core\R64\InstallPath reports the current R installation is at C:\Users\Raymond.Lucio\AppData\Local\Programs\R\R-4.6.0
2026-06-01 10:31:25.073 [info] Identified the current R binary: C:\Users\Raymond.Lucio\AppData\Local\Programs\R\R-4.6.0\bin\x64\R.exe
2026-06-01 10:31:25.108 [info] Possibly found R on PATH: C:\Users\Raymond.Lucio\AppData\Local\Programs\R\R-4.6.0\bin\x64\R.EXE.
2026-06-01 10:31:25.109 [info] Resolved R binary at C:\Users\Raymond.Lucio\AppData\Local\Programs\R\R-4.6.0\bin\x64\R.exe.
2026-06-01 10:31:25.147 [info] Registry key HKEY_CURRENT_USER\SOFTWARE\R-core\R64\4.6.0\InstallPath reports an R installation at C:\Users\Raymond.Lucio\AppData\Local\Programs\R\R-4.6.0
2026-06-01 10:31:25.147 [info] Ignoring ad hoc R binary /usr/bin/R because it does not exist.
2026-06-01 10:31:25.147 [info] Ignoring ad hoc R binary /usr/local/bin/R because it does not exist.
2026-06-01 10:31:25.147 [info] Ignoring ad hoc R binary /opt/local/bin/R because it does not exist.
2026-06-01 10:31:25.147 [info] Ignoring ad hoc R binary /opt/homebrew/bin/R because it does not exist.
2026-06-01 10:31:25.217 [info] Candidate R binary at C:\Users\Raymond.Lucio\AppData\Local\Programs\R\R-4.6.0\bin\x64\R.exe
2026-06-01 10:31:25.217 [info] Default R interpreter path specified in 'positron.r.interpreters.default': C:\Users\Raymond.Lucio\AppData\Local\Programs\R\R-4.6.0\bin\x64\R.exe
2026-06-01 10:31:25.217 [info] R installation discovered: {
  "usable": true,
  "supported": true,
  "reasonDiscovered": [
    "Found in Windows registry",
    "Found in PATH, via the `which` command",
    "Found in the primary location for R versions on this operating system"
  ],
  "reasonRejected": null,
  "binpath": "C:\\Users\\Raymond.Lucio\\AppData\\Local\\Programs\\R\\R-4.6.0\\bin\\x64\\R.exe",
  "homepath": "C:\\Users\\Raymond.Lucio\\AppData\\Local\\Programs\\R\\R-4.6.0",
  "semVersion": {
    "options": {},
    "loose": false,
    "includePrerelease": false,
    "raw": "4.6.0",
    "major": 4,
    "minor": 6,
    "patch": 0,
    "prerelease": [],
    "build": [],
    "version": "4.6.0"
  },
  "version": "4.6.0",
  "arch": "x86_64",
  "current": true,
  "orthogonal": true,
  "default": true
}

2. Is execution policy in play?

When I navigate to that folder via cmd and execute I get the following:
Ark 0.1.251

There is an antivirus app on the work laptop and it does show a blocked item:
program files\positron\resources\app\node_modules@vscode\ripgrep\bin\rg.exe

3. Where do the folders live?

One Drive houses all folders including the ones generated by the template option.

4. What exactly does the picker show?

No session is active. If I click on Start Session, I have only two options:
Python 3.13.13 (MicrosoftStore) Suggested
Python 3.13.13 (MicrosoftStore) MicrosoftStore

There are no R versions.

[juliasilge]

Thanks so much for all the detailed logs, @ray-lucio! These are really helpful, and they actually point me away from my earlier guess about ark.exe being blocked, since ark.exe --version runs fine for you, it lives under C:\Program Files\Positron\... (not a user-writable location), and the only thing your antivirus flagged is rg.exe (ripgrep), not ark.

Here is what is puzzling me, and where I would like to focus next. Your R Language Pack logs clearly show R 4.6.0 being found and validated ("usable": true, "supported": true), so R really is being discovered. But in those same windows the picker shows "No suitable interpreters found. Please install R version 4.2.0 or later" and no R appears at all! 😩 Somewhere between R being discovered and R being registered as a usable interpreter, it is getting dropped, which seems like the thing to try to understand.

One strong signal in your Kernel Supervisor log is this line:

Connection file was not created after 31701ms; output: ...

The supervisor process (kcserver.exe) actually wrote its connection file right away, but Positron could not see that file for ~31 seconds, so it timed out and had to retry. A 31-second delay reading a file that was just written in your Temp folder could be a sign of antivirus/EDR real-time scanning or a OneDrive sync filter sitting in the I/O path. R discovery in the same logs also took ~23 seconds, so the whole environment is being throttled by something. That slowness may also be part of why R does not finish registering.

A few things that would help me narrow this down:

1. After opening one of the failing folders, please give it a full minute or two without touching anything (discovery is running very slowly for you), then open the interpreter picker again. Does R ever show up if you wait long enough? I want to know whether this is purely a timing/race issue or whether R never registers no matter how long you wait.

2. With that same failing folder open, run "Developer: Toggle Developer Tools" from the Command Palette, go to the Console tab, and copy out every line containing [Runtime startup] as well as anything mentioning R registration or errors. That will tell me how far R gets in the registration sequence.

3. Try copying one of the failing projects to a plain local path like C:\dev\test, completely outside OneDrive, and open it there. If R shows up and starts fine, that points squarely at the OneDrive sync filter.

4. Separately, you can raise the supervisor startup timeout. In Settings, search for "Kernel Supervisor" and set the startup timeout to something generous like 60 or 90 seconds. That will not fix R missing from the picker, but it should stop the supervisor from timing out and is worth doing in the meantime so we can see if it can get past that part of startup.

5. Finally, and this one likely needs your IT team: since your antivirus has already blocked rg.exe from inside the Positron install, it is worth asking them to add an exclusion for the C:\Program Files\Positron\ folder (and ideally your Temp folder) in whatever AV/EDR product manages the laptop. You probably cannot do this yourself, but if the tests above point at scanning latency, that is likely the real fix.

[ray-lucio]

1. No it doesn't. I also tried running Interpreter: Discover All Interpreters and it did not return any R instances.
   I let the app sit for about an hour.

2. Nothing appears if I type that in.

3. This doesn't change results.

4. I'll see about this.

Today, I received an antivirus warning that hasn't happened in the past.
Category: Trojan
Affected Items: C:\Users....positron\extensions\posit.assistant-0.5.6-universal\dist\extension.js

[juliasilge]

On the antivirus warning, you saw that after updating to 2026.06.0 yesterday or today? We are tracking that in posit-dev/assistant-feedback#16 and hope to get that resolved ASAP!

On your continuing problems with R starting, I have an idea that might sound a little out there. 😅 Two facts you reported point at the same possible root cause:

• Your antivirus flagged ...\resources\app\node_modules\@vscode\ripgrep\bin\rg.exe as a blocked item inside the Positron install.
• You saw [Runtime startup] Error starting affiliated runtimes: Error: spawn EPERM in the developer tools.

rg.exe is ripgrep, the search tool Positron uses for all file searching. As part of discovering R, Positron checks the workspace folder for R-related files (.R, renv.lock, and so on) to decide whether to recommend R, and that check runs ripgrep. If your antivirus blocks rg.exe from launching, that search fails with spawn EPERM, and right now that failure takes down the whole R discovery pass before R can be registered. That is why R shows up in the R Language Pack log as found and usable, but never appears in the interpreter picker.

It also explains why it is folder-dependent, I think! When Positron creates a folder from a template (or you have used R in a folder before), R is remembered for that folder and starts through a path that does not touch ripgrep, so it works. A pre-existing folder opened cold has nothing remembered, so R can only appear through discovery, and discovery is the part that is failing for you.

Two things would confirm this rather speculative idea on my part:

1. Open one of the folders where R does not appear, press Ctrl+Shift+F to open the search panel, and search for any word you know is in your files. I know that sounds a little wacky, but I believe this uses the same rg.exe that R discovery uses. If the search hangs or returns nothing when it clearly should find matches, that would indicate that ripgrep is being blocked.

2. Could you open the R Language Pack log in an editor (the "Open Output in Editor" option) and paste the full text? I specifically want to see whether anything appears after the R installation discovered block, or whether it stops right there.

If this is actually what's going on for you, the real fix has two parts. On your side, this almost certainly needs your IT team to add an antivirus/EDR exclusion for the C:\Program Files\Positron\ folder, since the antivirus is actively blocking files inside the install (it has already blocked rg.exe and flagged other files). On our side, this is a bug we should fix regardless. A blocked file search should quietly skip the recommendation step, not prevent R from being discovered at all. I will open an issue for that.

[juliasilge]

I opened #13969 for the problem I think we can see by tracing through the code, but it would be great to get a little more detail from you to confirm this is actually happening.

[ray-lucio]

@juliasilge thanks for working through this with me. Unfortunately, the threat warning required me to uninstall Positron. If I'm able to get it back and the issue persists, I'll reach out again.