[Solved] Python error – IDLE’s subprocess didn’t make connection. Either IDLE can’t start or personal firewall software is blocking connection

I am new to programming and i decided to learn Python first, so;

I installed Python, latest version 3.4. and I am trying to open Python IDLE(GUI) mode, so when I open I get message “IDLE’s subprocess didn’t make connection. Either IDLE can’t start or personal firewall software is blocking connection.”.

My firewall is not problem beacuse I put Python throught it. I also tried to reinstall it and it didnt made diffirence. So please if somenone can help!

Thank you on your time 😀

Enquirer: Usce


Solution #1:

Delete all newely created .py files in the directory with Python. for example, – that was my problem that caused the same notification window. Reason in filename conflicts.

Respondent: Igor Tischenko

Solution #2:

It may be a common problem that happens when you have in you current directory a file with same name on one from Python (references : Can’t run Python via IDLE from Explorer [2013] – IDLE’s subprocess didn’t make connection)

It seems it can also happen if you have incorrect environment variables such as HOMEPATH USERPROFILE (references : Issue 14576: IDLE: inconsistent use of HOMEDRIVE, HOMEPATH, and USERPROFILE on Windows)

I’ve found another related question : Python IDLE subprocess error?

My advice if the answer is not there : google may be your friend ! The 3 clues above come from there 🙂

Respondent: Serge Ballesta

Solution #3:

I fixed it, I needed to run IDLE with admin privileges. (I am using Windows 7 x64). Hope this helps.

Respondent: WinMacLinUser

Solution #4:

Simple…rename your .py file with some name different from any keyword name like ‘’ which already exists in python package.

Eg. I named one file as “”. The same error popped up. I renamed it to “”. It worked.
The different naming discards the problem of ambiguity between an already existing file and a newly created file with same name.

Respondent: Sujatha

Solution #5:

The fix is here .

Open task manager, kill pythonw.exe, if you find 2 instances or more. Should work after that.

Respondent: Lakshmi Narayanan

Solution #6:

For me: The drive pointed to by HOMEDRIVE was not writeable. I checked this by running idle the hard way, explicitly using python.exe rather than pythonw.exe:


 Warning: unable to create user config directory
 Check path and permissions.
Respondent: amonroejj

Solution #7:

I had a similar problem with a file called “” and Python 2.7.9 – renaming the file to something else solved my issue. After checking, I noticed that there is a file with the same name under the Python27Lib folder.

Seems to be a bug in IDLE.

Respondent: Karo Kuokkanen

Solution #8:

Just had the same issue. So uninstalled and reinstalled which fixed it and took 10 minutes. The key with Windows machines is delete the old directory (C:Python27 because windows does seem to actually delete things) and when reinstalling specify a new directory (C:Python279 or whatever you choose to call it).

I am using Win 10 with Python 2.7.9.

Respondent: CDS

Solution #9:

Go to C:/Users/[your user]/AppData/Local/Programs/Python/Python35-32 and delete or rename every *.py file in this directory which is named after a certain method, function, module or library. Then run IDLE. Should work.

Hope I could help

Respondent: Fish

Solution #10:

My problem was that the .py file wasn’t on my local machine. It was on a shared directory.

After moving the file to my local machine, I quit getting the error.

Respondent: Eric

Solution #11:

Just to note my particular issue, this happens for me when my RAM gets full and my CPU gets busy.

The problem is because of a network socket timeout on the IPC pipes between the RPC subprocess.
It’s a poor design (insecure and prone to failure) that’s commonly used for IPC instead of process pipes.

The fix is to clear out some RAM and CPU usage and wait a minute before trying again.
And for developers, the fix is to stop using sockets for IPC and use proper process pipes.

Yes, it’s the same exact socket timeout issue you experience with your browser, though on modern browsers, the page just stops loading instead of displaying a timeout error screen.
(note this assumes the case of a good WAN connection, with a local timeout)

Respondent: Tcll

The answers/resolutions are collected from stackoverflow, are licensed under cc by-sa 2.5 , cc by-sa 3.0 and cc by-sa 4.0 .

Most Popular

To Top
India and Pakistan’s steroid-soaked rhetoric over Kashmir will come back to haunt them both clenbuterol australia bossier man pleads guilty for leadership role in anabolic steriod distribution conspiracy