The debugged executable did not respond

[bds107]

Hi everyone,
Strange. When I try to start a program from the IDE using F5, I sometimes get this error. After about three retry attempts, it works.
The error says: The debugged executable did not respond to communication for 10 seconds. Disconnecting. And an [OK] button.
Does anyone have any ideas on what I can change?

[SPH]

Maybe an antivirus...

[bds107]

Maybe an antivirus...

It's possible.
I've excluded the PowerBASIC folder and projects from testing in Windows Defender.
I'll keep trying and see what happens.

[mk-soft]

I've done this many times before.

Install PureBasic in C:\WinApp and add this folder to the whitelist.
Add the project folder to the whitelist.
Compiler option -> compile and start -> create temporary executable in source folder.

[BarryG]

I was sick of adding the temp executable to Defender's whitelist, so now I compile to the source directory instead which is under my main PureBasic folder. I've whitelisted that single folder now and the false messages have gone away. However, I still upload my compiled exes to VirusTotal.com so I can see what my users will experience (no point sticking my head in the sand), and get the exes whitelisted if need be.

[mk-soft]

The problem is when the executable is constantly changing during programming.
The virus scanner always strikes.
You don't have to add the individual executable to the whitelist, but the folder of the project and create the executable there.
The constant uploading to virustotal leads to PB programmes being blocked more and more, as all manufacturers adopt their list here.