Python/R Console Takes Too Long to Start on Windows (Console Stuck Loading) #10691
Unanswered
Santoshjnawali
asked this question in
Q&A
Replies: 2 comments 6 replies
-
|
Can you try using the command Developer: Startup Performance to find out what part of startup is causing a problem for you? It will help you see if it's some specific extension or some part of what Positron is doing. |
Beta Was this translation helpful? Give feedback.
6 replies
-
|
I just tried with 2026.01-59 on my Windows 11 box and things aren't too bad. I do have a fairly performant machine: |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment



Uh oh!
There was an error while loading. Please reload this page.
-
On my Windows device, the Python and R interpreters take a very long time to start. The console often gets stuck on “loading” and fails to display logs, and interpreter detection is inconsistent. Sometimes the wait is so long that I lose patience before the console loads. I have daily updates enabled, and I have been experiencing these issues for a long time.
Interpreter startup is extremely slow
Console stays in a “starting” state with no logs
The interpreter sometimes isn’t detected until I reload
Extensions start very slowly
Is anyone else on Windows experiencing this? Is there anything we can do at the user level to improve startup time?
Beta Was this translation helpful? Give feedback.
All reactions