FreeCAD crashes on startup on Windows 7

[krater]

Hello,

I have a fresh installed VM with Windows 7 x64 with all mandatory updates installed. I working in the Aero Windows 7 theme.
Everytime I start FreeCAD it dies after the splash screen with the following message:

Problemsignatur:
Problemereignisname: APPCRASH
Anwendungsname: FreeCAD.exe
Anwendungsversion: 0.19.0.16100
Anwendungszeitstempel: 608218f4
Fehlermodulname: Qt5WebEngineCore.dll
Fehlermodulversion: 5.15.2.0
Fehlermodulzeitstempel: 5fad38ab
Ausnahmecode: 80000003
Ausnahmeoffset: 000000000014baff
Betriebsystemversion: 6.1.7601.2.1.0.256.48
Gebietsschema-ID: 1031
Zusatzinformation 1: 50db
Zusatzinformation 2: 50db7e5a809d367c4f592c967def835e
Zusatzinformation 3: 4a52
Zusatzinformation 4: 4a521b168a3a7350caedb72aac1c7260

Lesen Sie unsere Datenschutzbestimmungen online:
http://go.microsoft.com/fwlink/?linkid= ... cid=0x0407

Wenn die Onlinedatenschutzbestimmungen nicht verfügbar sind, lesen Sie unsere Datenschutzbestimmungen offline:
C:\Windows\system32\de-DE\erofflps.txt

Used FreeCAD version:
FreeCAD-0.19.2.7b5e18a-WIN-x64-installer1


What I have tested and how I came to this point:

I installed FreeCAD on my own native sparely updated Windows 7 x64 system. There I use the classic theme. After first install it started but missing some files. As I found in a forum I need to install a specific update, I installed that and after that I got the upper error.
I though, ok, can happen, my system is sparely updated and used since some years. So I installed a Win7 x64 VM on VirtualBox where I installed all updates, Classic Shell and switched to Classic mode.

Then I installed FreeCAD and had the same issue.
After reading here, I found out that switching to Aero should make it possible to start FreeCAD. I done that, but no change.

So I think this could be another bug.

Any help?

Thanks
krater

[chrisb]

Please look at the Known OS specific issues.

Can you retry with 0.20? It uses some different libraries.
Can you start from console? Then the output may be more interesting than the system report.
You can also use the additional commandline paameter --write-log to create a log file