musescore / musescore/MuseScore

Windows 10/11 N(/KN) Edition Unsupported

Open
#27,119 1 comment 0 reactions 2 assignees View on GitHub

Nobody has claimed this yet.

crash needs review
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

Crash or freeze

Description with steps to reproduce
  1. Create a Windows 10 N Virtual Machine
  2. Try install MuseScore Studio, error on startup.
  3. Installing Media Feature Pack for Windows N and restarting the VM now allows MuseScore Studio to launch.
Supporting files, videos and screenshots

Image

What is the latest version of MuseScore Studio where this issue is present?

4.5.0

Regression

No.

Operating system

Windows 10 Home N (19045.2803)

Additional context

I investigated this issue for a user who was also hitting a related bug on the MuseHub side of things. It's incredibly rare for users to hit this (I've got about 200 recorded in sentry - now that I know what's causing it). I don't think the N edition is super popular these days, but it's still confusing for a user to hit this.

Essentially as MuseScore Studio (and MuseHub + others) make use of the Windows media APIs, these are not present on Windows N Edition, instead you must install the Media Feature Pack for Windows N and restart your device.

I've patched this in the next version of the MuseHub installer by dynamically checking the media APIs to see if they are available and erroring out if they are not (directing users to the Microsoft support article). I can provide this code in Slack if required.

This should handle users downloading MuseScore Studio via MuseHub (assuming they follow the steps), but it's still not super clear if you download and install MuseScore Studio by itself. And there's alot of bad advice online.

I'm unsure what the best path forward is, maybe something mentioned in the system requirements? Or using similar code to MuseHub and presenting a friendly error message to users who encounter this?

Checklist
  • This report follows the guidelines for reporting bugs and issues
  • I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
  • I have attached all requested files and information to this report
  • I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.