Active Python executable becomes an empty file

Nov 5, 2020
Reaction score
I have implemented a batch processing system using the task scheduling mechanism available on Windows 10 but I have run into a problem where python.exe is written to such that it becomes an empty file. I am at a complete loss to understand why this happens. The batch processing system is written in command files and uses start /b call /c <command-file> where <command-file> calls the file to be run. That file can be implemented as any executable file including Python scripts. It is running as SYSTEM so has the permissions to overwrite python.exe but I am pretty certain it is not my scripts because they interact with the D: drive not the C: drive where my Active Python 3.4.3 installation resides. Of course, I may be wrong. My C drive is a SSD and D drive is a hard drive. Both are 4 years old.


Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question