Windows appliation crashes on startup

• Jul 4, 2022 - 17:32
Reported version
S3 - Major

Steps to replicate:
- Using the updated version of MuseScore.
- Open the application from the .exe (the start menu or pinned shortcut)

Expected results:
The application will open as the previous versions and allow user to edit and save files as normal.

Actual Results:
The Application will open with an empty score template for a few seconds and then crash. Subsequent application starts recognized that it crashed previously.

If I open a project that had been created prior the update, I am able to edit that projects, open other projects and even create new projects.

Error from Event Viewer:
Faulting application name: MuseScore3.exe, version:, time stamp: 0x6021394c
Faulting module name: Qt5WebEngineCore.dll, version:, time stamp: 0x5ded28b8
Exception code: 0x80000003
Fault offset: 0x0000000000900ee9
Faulting process id: 0x3a4
Faulting application start time: 0x01d88fc1b817004b
Faulting application path: C:\Program Files\MuseScore 3\bin\MuseScore3.exe
Faulting module path: C:\Program Files\MuseScore 3\bin\Qt5WebEngineCore.dll
Report Id: 9e3f1a55-aed6-4199-af61-a1aebd3ccfdd
Faulting package full name:
Faulting package-relative application ID:

Attachment Size
Report.7z 3.88 KB


Status active needs info

Try starting MuseScore by double clicking a score file, or use the -w command line option, if that works, disable the start center in preferences.

In reply to by Jojo-Schmitz

I am able to keep Musescore running if I open a previously created score. From there I'm able to edit, save, and even create new scores. Disabling the Start Center in preferences was effective at keeping the program open. Is this a known issue/fix? In perusing the issues list, I didn't see anything that would have led me to try this.

Hopefully this issue is fixed soon, but meanwhile, I'm glad for these workarounds and I thank you for your input.

Status needs info duplicate
Workaround No Yes

So you have a workaround. And As far as I remember this issue had been reported already, so this issue here is a duplicate, I'm just too lazy to search for the other one