There can be many reasons, and it is difficult to diagnose and recommend a solution without studying the actual system and process. If you are really interested in this, I can suggest how you can debug these problems.
- Download Process Monitor
- Bring the process Monitor and filter the entire process except pythonw. PythonW is a process that starts when IDLE starts.
- Now start monitoring in the process monitor.
- Connect IDLE and wait until the process monitoring log is stable.
- Now study the LOG to find out what could go wrong.
- If you need more help, just post a magazine here and we can try to figure out what is wrong with your system.
To simulate your problem, I renamed my idle.pyw to idle_1.pyw and tried to call IDLE. He did not pass without any message. Then I picked up the Monitor process and filtered out the pythonw process and tried to run IDLE again. I found a message in the log that was consistent with the problem.

As you can see, I highlighted an error that shows which error is yes. Try a process handler, and this will probably muffle the problem if there is nothing for you :-) Remember that just do a ThreadExit search in the log, the error should be slightly higher than the operation. In case you find it difficult to understand the problem, just post a scroll next to ThreadExit , and we can help you.
Update from the provided image 
As you can see in the log, FSECURE.DLL has suddenly shut down the thread. FSECURE (antivirus / firewall) does not believe that this process has legal rights to perform any operation. If you need to know more details about which operation was blocked, you can get it from the Fsecure log. In most cases, as you did, starting as an administrator will help the process gain the right not to block Fsecure.
I have no experience with Fsecure, but most antiviruses have a Whitelist entry where, if you add a process, this will not stop it from blocking it.
source share