I tested with 12587.

The issue is not fixed.

In the past I would get a hang up when the process locked and I had to quit TheIDE.

Now, I get a message telling me that the binary can't be opened for writing. So I guess it is an improvement. The process can't be killed by windows manager and I need to shut down TheIDE.

A few months ago I tried everything to fix this but gave up. I was using WinAPI (WaitForSingleObject if I remember correctly) to wait for the process. Yet the process would not finish and TheIDE would hang forever.

			dword exitcode;
			int start = msecs();
			while(GetExitCodeProcess(hProcess, &exitcode) && exitcode == STILL_ACTIVE && msecs(start) < 3000)
				Sleep(1);

This behaves better than WaitForSingleObject since it won't lock forever, but I suppose testing GetExitCodeProcess after 3 seconds will still give an active result in the case where the exe can't be written too. Maybe that should be logged somewhere and shown in TheIDE?

There must be a more aggressive way o killing a process as a fail safe?