Bug #349

Windows update causes moscore_qm crash at startup

Added by Jamie Pate almost 5 years ago. Updated about 4 years ago.

Status:FeedbackStart date:07/09/2017
Priority:NormalDue date:
Assignee:Jamie Pate% Done:


Category:Start UpSpent time:3.00 h
Target version:Customer needs to fix


After a windows update (we suspect the windows 10 anniversary update 1703) the behavior of the windows 'default printer' setting causes moscore_qm to crash on startup.

A workaround to prevent this issue is to disable the "Let Windows manage my default printer" setting in the "Printers & scanners" section of windows 10 settings. (see attached screenshot)

defaultprinter_annotated.png (131 KB) Jamie Pate, 07/09/2017 09:00 PM


#1 Updated by Jamie Pate almost 5 years ago

The startup error is similar to "Access violation at address 00787B76 in module 'moscore_qm.exe'."

#2 Updated by Walter Pate almost 5 years ago

  • Status changed from Resolved to Feedback

this issue was repaired for version release 1.3.48. awaiting feedback from users regarding update crash issues

#3 Updated by Walter Pate about 4 years ago

  • Priority changed from Urgent to Normal
  • Target version changed from 1.3.48 to Customer needs to fix

A customer just experienced this issue with windows 8. Her reports to us indicated that the Moscore-QM Splash screen was indicating that the Printer location was changed. She then removed the printer from windows control and her Moscore-QM worked fine

Also available in: Atom PDF