I've created an app with a C++ backend and a HTML-based frontend. I've also created a setup file by using Inno setup including all the needed DLLs and other files. I've tested in several different machines, virtual and real ones, in order to check its consistency. I've also given it to different people as well to test it.
In one of these cases, however, the app crashed. I also have created a C++ logger, but unfortunately didn't give any additional valuable info.
I assumed that it may have to do with Windows permission issues, so I created different C++ executables by changing the manifest file in Visual Studio, but no luck.
As far as I know, in order to deal with these kind of situations, one either uses the remote debugger of Visual Studio on the host machine, or use Windbg on the target machine, but these two ways require either network access to the target machine or knowledge of Windows debugging from the end user.
I'd like to know what one can do if there is no network access and the end user is not capable of debugging even by following instructions. Is there a way, either by C++ or through Windows, to generate a crash dump file that can be used afterwards for debugging?