Invalid access to memory Version 5.8 (Dev build 5624 2015-07-21)

<Try to describe precise steps that lead to the problem (where do you click, what keys do you press, what do you see, etc.)>
<If relevant, consider attaching a session log file or a screenshot)>

WinSCP 5.8

Error message:
Invalid access to memory.

Stack trace:
(00590F7F)
(008107FA)
(00812862)
(0080F7DC)
(0005A60A) ntdll.dll
(0000F12E) ntdll.dll.KiUserExceptionDispatcher
(00589348)
(0058908E)
(00589298)
(005891EF)
(00588FE5)
(00586735)
(006435A1)
(0064364D)
(00084BC4)
(007AA431)
(003C1EEC)
(003C1DAB)
(002225D1)
(0018A804)
(00222737)
(002225D1)
(00221C18)
(003464F4)
(000152F7) USER32.dll
(00015D35) USER32.dll
(00018659) USER32.dll
(000186C0) USER32.dll.SendMessageW
(000A359B) COMCTL32.DLL
(000A35FE) COMCTL32.DLL
(000A3488) COMCTL32.DLL
(000152F7) USER32.dll
(00015D35) USER32.dll
(0001FD22) USER32.dll
(0001FD48) USER32.dll.CallWindowProcW
(002226E2)
(002225D1)
(0018A804)
(003464F4)
(000152F7) USER32.dll
(00015D35) USER32.dll
(000167BF) USER32.dll
(00016885) USER32.dll.DispatchMessageW

Status: unknown_rel_addr

---

Precise Steps:
I tried to use certificate file *.cer instead of *.p12
Dialog box allows to show "*.* any file" and use any file as certificate.
Yes, it's dumb. However:
Never underestimate the power of stupid people in large groups. © G. Carlin

Version 5.8 (Dev build 5624 2015-07-21)

Thanks for your report. I cannot reproduce the problem.
I have sent you an email with a debug version of WinSCP to address you have used to register on this forum.