How should I handle a Windows Media Feature Pack dependency from an installer?

Question

I've recently updated a Windows desktop application from having a dependency on OpenCV 3 to OpenCV 4, and have discovered that OpenCV versions 3.4 and above, on Windows, have a dependency on Microsoft's "Windows Media Feature Pack". This feature is not installed by default on distributions Windows 10N, Windows 10KN, Windows 11N, and Windows 11KN.

Common advice is to install the Media Feature Pack manually via the control panel, Apps > Apps and Features > Optional Features > Add a Feature. This works for end users but what is the best practice when implementing an installer with this dependency? Should the installer just detect that Media Feature Pack is not available via the registry and error out or is there a way to install it programmatically?

On N versions, you have to install the MSU file available at microsoft.com/en-us/software-download/mediafeaturepack — Christophe
– Christophe, Commented Nov 9, 2023 at 14:54

Hara Abdul · Accepted Answer · 2024-10-25 06:47:35Z

2

I had the same problem with running cv2.

Don't know about you, but I couldn't simply add Media Feature Pack through the windows update interface. Rather, I was forced to manually add/install Media Feature Pack, which I did through CMD.

I used these commands:

dism /online /remove-capability /capabilityname:Media.MediaFeaturePack~~~~0.0.1.0

dism /online /add-capability /capabilityname:Media.MediaFeaturePack~~~~0.0.1.0

Hope this helps!

answered Oct 25, 2024 at 6:47

Hara Abdul

212 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

How should I handle a Windows Media Feature Pack dependency from an installer?

1 Answer 1

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related