This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(220.8, 54%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Our app uses third party library that is referencing mfplat.dll (and mfreadwrite.dll) of Media Foundation. MF dlls are usually present in the OS, except apparently on Windows N where media component is not installed by default. When launched on Windows N, our app closes instantly. Digging into the problem reveals a system error
The code execution cannot proceed because MFPlat.DLL was not found. Reinstalling the program may fix this problem.
As far as I can tell, the launch is being aborted at very early stages without giving any of our or the librarys code a chance to handle the error. Can't quite find a desription of initial dependency resolution process for UWP, but logically shouldn't absent-by-design system dependency turn into a runtime error to a LoadPackagedLibrary() call, where we could at least handle it gracefully?
If you detect that MFPlat.dll is not present, you can launch the installation of the Media Feature Pack
App would first have to run for that. It appears the system aborts the launch, none of our code is executed.
Hello,
Welcome to Microsoft Q&A.
Currently, UWP does not provide related events or entrances for intervening when the application resolves dependencies.
You can choose to include the DLL in the package and add the corresponding reference. or you can ask the user to install the required DLL in the application description.
Thanks.
So is this a know issue, someone looking into this?
Neither of those sound like a permanent solution really. A note in the description along with an apology could work for a while, but is there a proper industry-level fix coming?
Hello, Windows N system does not include Media Feature Pack. This is the configuration of the system. As a supplement, users can install Media Feature Pack, which is a design. If you need feedback this problem, you can report it in the Feedback Hub app.
Surely, apps crashing cold are not in the design? Not sure I understand what point you are trying to make.
I came here hoping someone would point out a mistake on our part, that we could then try and fix. You making it sound like a known and intended UWP thing. You tell me - do I need to feedback about it? It can't be by-design and needing to be reported at the same time.
I'm sorry for the misunderstanding. Windows N system does not contain the DLL file you need, this is by design. UWP applications cannot run when lack related dependencies, which is also the default behavior. At present, UWP does not provide an interface that can intervene in the dependency analysis phase. If you want UWP to provide related functions, you can report this problem.
Hello, do you have any other questions? If so, please feel free to ask.