Faulting application name: pulseview.exe, version: 0.0.0.0, time stamp: 0x00000000 Faulting module name: MSVCR100.dll, version: 10.0.40219.325, time stamp: 0x4df2bcac Exception code: 0x40000015 Fault offset: 0x00000000000761c9 Faulting process id: 0x4780 Faulting application start time: 0x01d5e3c5d5c5b0fa Faulting application path: C:\Program Files (x86)\sigrok\PulseView\pulseview.exe Faulting module path: C:\WINDOWS\SYSTEM32\MSVCR100.dll Report Id: a6e3ab7f-9706-4579-9552-205b0a019245 Faulting package full name: Faulting package-relative application ID: no change was made to the visual c++ redistributable 2010 I removed and reinstalled i, just in case. No change. In the task manager the process appears for a second, shows "suspended" and dies. Started on 2/13/2020 - may be related to the Windows updates from that date.
You can try starting pulseview with the parameter -D to see if that changes anything. Other than that, this appears to be the general DLL hell bullshit that Windows has always been plagued with. Unless other people step forward with the same problem, I have to assume that it's a problem with your Windows installation in particular and PulseView is having problems running because of that circumstance. Googling for "MSVCR100.dll 0x40000015" suggests the same. Nonetheless, trying -D could be worthwhile.
It was an Environment Variable that caused the issue. Surprisingly only with this MS C++ distributable dll... Once I removed the Variable PulseView started working like charm...
I'm glad it works for you now! Just so that others can have the solution if they run into the same issue: what was the name of the environment variable?
I used PYTHONPATH on Windows 10 (and added it to the system path). I replaced it with a random name (PPath) and deleted it and that's it. I guess Windows doesn't like that variable... I spent a few hours hacking it with Process Monitor and WinDbg... Anyway - thank you for your help!!