Not all C5 error trigger the log. It depends on how severe the error is and whether the VFP internal debug system can step in before Windows captures the error and exits VFP.

+++ Rick ---

>In an existing app I'm debugging an issue that causes a C5 error.
>
>On some machines an error message pops up just saying "Microsoft Visual FoxPro has stopped working. A problem caused the program to stop working correctly" etc.
>
>On others a different, more detailed message comes up (see attached image). In this case it seems to also write a VFP9Err.log file to ..\Common Files\Microsoft Shared\VFP\
>
>I can repro the issue on my Win10 x64 laptop, but of course I get only the simple/non-informative message, VFP9Err.log does not get created.
>
>How can I cause the VFP9Err.log file to be created on my laptop?