Windows Server Core LTSC 2022 container – Unable to install Media Foundation (Server-Media-Foundation)

Hi everyone,

I’m using the mcr.microsoft.com/windows/servercore:ltsc2022 Docker image and trying to install Media Foundation inside the container.

When I run:

Install-WindowsFeature Server-Media-Foundation
I get the following error:

Install-WindowsFeature : The request to add or remove features on the specified server failed.
Installation of one or more roles, role services, or features failed.
The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see https://go.microsoft.com/fwlink/?LinkId=243077. Error: 0x800f081f
At line:1 char:1
+ Install-WindowsFeature Server-Media-Foundation
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (@{Vhd=; Credent...Name=localhost}:PSObject) [Install-WindowsFeature], Exception
    + FullyQualifiedErrorId : DISMAPI_Error__Failed_To_Enable_Updates,Microsoft.Windows.ServerManager.Commands.AddWindowsFeatureCommand

Success Restart Needed Exit Code      Feature Result
------- -------------- ---------      --------------
False   No             Failed         {}
This works fine on a full Windows Server 2022 VM, but consistently fails inside the container.

Questions:

• Is Media Foundation supported at all in Windows Server Core containers?
• If not, is there any supported workaround (base image change, feature layering, or host dependency)?
• Has anyone successfully enabled Media Foundation (or components like mfplat.dll) inside a Windows container?

Any guidance from folks who’ve hit this limitation before would be appreciated.

Thanks!

Start by reproducing Install-WindowsFeature Server-Media-Foundation in mcr.microsoft.com/windows/servercore:ltsc2022 and compare the result with a full Windows Server 2022 VM. Investigate whether the reported 0x800f081f failure is a container limitation or missing source, then document supported behavior and any confirmed workaround.