It creates minidump in Project/Saved/Logs folder, but CrashReportClient.exe doesn’t find it upon crashing.
Upgraded to release version of windows 10 yesterday and I haven’t changed any settings for Windows Error Reporting and don’t know reason for this or how to fix it.
error report is same every time:
MachineId:
EpicAccountId:
No minidump found for this crash.
PS. I intentionally wrote a c++ line causing it to crash to get crash report popping up.
I’m looking into this issue currently. Windows 10 is not something that we have tested with 4.8 so this could be reason for this issue. 4.9 on other hand, has been tested a slight amount but is still expected to have some OS related issues with Windows 10.
I tried to reproduce this on 4.9 by typing ‘debug crash’ into console to cause a crash and my crash reporter was able to find minidump. Can you try 4.9 Preview 2 to see if this issue persists?
Could you provide logs from one of your project’s Saved > Logs folder that has crashed previously? Also, what version of Windows 10 are you on, such as Home, Professional, or Education? One thing to check, which shouldn’t give this exact error that you’re getting but it’s worth a try, would be to open Epic Games Launcher and make sure that you’re also installing debug symbols. You can do this by going to Library tab, clicking down arrow beside “Launch” on any version of engine past 4.9.2 and selecting “Options”. There should be a check box for “Editor symbols for debugging”, ensure that this is checked.
Thank you for that information VigiFyre. I’m still looking into this issue but not having much luck so far. I’ll be sure to let you know whenever I find out more.
Logs from CrashReportClient might be useful. crashed process should write crash into a folder in WER report queue folder. On my Win7 machine that’s \AppData\Local\Microsoft\Windows\WER\ReportQueue. You should be able to check it writes this successfully and that will tell you whether it’s an engine or crash reporter issue.