Enabling Media Features (Windows 11 N)

autotalon

New Member
Messages
13
Reaction score
1
Hello, I have a Windows 11 N image where I have downloaded the FOD ISO and installed the Media features into the image, but it is checked and says "Disabled" in bold. How do I get it to install?
 
I don't believe you can use the older W10 FOD to install Media Feature Pack on W11 N. They're not compatible builds.

For releases after W10 1903, you have to perform online installs with:
Code:
DISM /Online /Add-Capability /CapabilityName:Media.MediaFeaturePack~~~~0.0.1.0
 
That was my original answer, until I realized the N license key doesn't work for non-N images.
 

Is this what was installed?
I use the Win 11 FOD ISO here: https://github.com/MicrosoftDocs/az.../virtual-desktop/windows-11-language-packs.md

It does seem to be installing it properly, just not enabling it. If the tool is not supposed to enable it, that's fine and I can run the command to do so but wanted to make sure that this was intended behavior.

The reason we use N images is that the time to fix my debloat scripting after every feature update is not worth the time and effort to me. Other than enabling media features so webcams work, I havent ran into any other issue with N at all. It activates using existing hardware licensing in the machines. Not sure what licensing you would have that wouldnt work; unless it was Enterprise or N for Workstations which do use different licenses. As far as I've seen, Pro seems to be Pro no matter if it's N or not.
 
I'm familiar with the FOD ISO, which exact package are you integrating? abbodi86 can correct me, but Pro can downgrade to N but not in the other direction, and you didn't originally state which license you had.
 
I'm familiar with the FOD ISO, which exact package are you integrating? abbodi86 can correct me, but Pro can downgrade to N but not in the other direction, and you didn't originally state which license you had.
Oh, yes what I am doing is integrating/enabling the Media Feature pack into the base Pro N wim. In my 22H2 ISO I did it manually with DISM but since I have switched back to NTlite for update slipstreaming as of 23H2, I set it up with the FOD ISO so I can re enable it on any edits going forward. I was just unsure why it did not allow me to enable it.
 
NTLite will allow you to add FOD feature packages, if added as Updates. My question is the 21/22H2 FOD's don't have Media Feature bundled in them, but I believe they were included in older ISO's. So there might be compatibility issues.
 
I tried restoring Microsoft-Windows-Media-Features package to 23H2 Pro N (22631.2428).

1. Searched UUP dump for the right CAB files:
Microsoft-Windows-Media-Features-Package-amd64.cab
Microsoft-Windows-Media-Features-Package-amd64-en-us.cab

2. Integrated CAB files as Updates.
3. Loaded image. Unchecked WMP, since it's not required. Applied changes.

Windows 10 x64-2023-11-20-20-50-09.png

4. Rechecked if Media Feature was really enabled:
Code:
Get-WindowsOptionalFeature -Path 'C:\Users\GARLIN\AppData\Local\Temp\NLTmpMnt\' -FeatureName *Media*

FeatureName      : MediaPlayback
DisplayName      : Media Features
Description      : Controls media features such as Windows Media Player.
RestartRequired  : Possible
State            : Enabled
CustomProperties :

FeatureName      : WindowsMediaPlayer
DisplayName      : Windows Media Player
Description      : Windows Media Player
RestartRequired  : Possible
State            : Disabled
CustomProperties :
                   \SoftBlockLink : http://go.microsoft.com/fwlink?LinkID=140092
 
Installing it as CAB appears to have worked, there must be something mismatched in the FOD ISO then. No worries, appreciate the help!
 
I tried restoring Microsoft-Windows-Media-Features package to 23H2 Pro N (22631.2428).

1. Searched UUP dump for the right CAB files:
Microsoft-Windows-Media-Features-Package-amd64.cab
Microsoft-Windows-Media-Features-Package-amd64-en-us.cab

2. Integrated CAB files as Updates.
3. Loaded image. Unchecked WMP, since it's not required. Applied changes.

View attachment 10746

4. Rechecked if Media Feature was really enabled:
Code:
Get-WindowsOptionalFeature -Path 'C:\Users\GARLIN\AppData\Local\Temp\NLTmpMnt\' -FeatureName *Media*

FeatureName      : MediaPlayback
DisplayName      : Media Features
Description      : Controls media features such as Windows Media Player.
RestartRequired  : Possible
State            : Enabled
CustomProperties :

FeatureName      : WindowsMediaPlayer
DisplayName      : Windows Media Player
Description      : Windows Media Player
RestartRequired  : Possible
State            : Disabled
CustomProperties :
                   \SoftBlockLink : http://go.microsoft.com/fwlink?LinkID=140092
Hi, I wanted to know, how did you get the media feature pack .cab files? I was not able do download them in UUP dump website. I was searching for W10 22H2 edition. Do you have kind of instructions on how to proceed? Thanks!
 
1. Find the current supported version of W10 22H2.

2. Search UUP dump for that build (19045.3803), and select amd64 or x86.

3. Enter Microsoft-Windows-Media-Features-Package-amd64.cab (or x86) in the Search files form.
Click the link to download.​
Rename file to Microsoft-Windows-Media-Features-Package-amd64.cab

4. Enter Microsoft-Windows-Media-Features-Package-amd64-en-US.cab (or x86) in Search files. Replace en-US with your language.
Click the link to download.​
Rename file to Microsoft-Windows-Media-Features-Package-amd64-en-us.cab
 
Hi garlin,

Thanks for you reply. I did your steps and worked. I was able to download the packages. I included the cabs as updates and enabled the media feature pack and windows media player on the optional feature components. However, when I try to stage a device, I have the following message when I try to start windows media player.

1704705388894.png
Sounds the integration worked, but not in a good manner. Sounds I have the same issue with .netframework 3.5

Any suggestions?

Thanks!

KR
 
I believe your WMP version isn't the right one, and it's expecting a different set of registered DLL's.

After installing a few Windows N images (23H2 Pro N), I found you should also include the MediaPlayer packages:
Code:
Microsoft-Windows-MediaPlayer-Package-amd64.cab
Microsoft-Windows-MediaPlayer-Package-amd64-en-us.cab

While WMP does appear to work, the "Windows Media Player Legacy" icon is blank because it's a shortcut to a non-existent "Program Files (x86)" file which doesn't exist in this image (maybe it's part of the normal Windows). You can repair the shortcut's broken properties.

MS has always wanted you to use Optional Features or the DISM /Add-Capability command, to officially restore Media Features. The last official download package was for Windows 1903, and it hasn't been re-released for later Windows.
 
Hi Garlin,

Hope you're well. I included both Windows Media Feature Pack and Windows Media Player into my wim file with NTLite and worked. I solved the shortcut issue with your solution. The shortcut was pointing to C:\Program Files (x86)\Windows Media Player\wmplayer.exe. By switching it to C:\Program Files\Windows Media Player\wmplayer.exe then this issue was solved.

Then, the problem is that some people are using FastStone Capture to record screen. The tool is pointing to Windows Media Player (x86) and needs it to run FSRecorder.exe. As sounds that Windows Media Player has an issue and not installed correctly, how can I correct it?
I tried the following stuff:

  • Run dism /add-capability and try to remove / add windows media player -> didn't work
  • Run sfc /scannow and restart -> didn't work
  • Tried to copy mfplat.dll and mfplay.dll from C:\Windows\SysWOW64 (from home computer) to C:\Windows\SySWOW64 -> didn't work
  • Tried to find files in that you mentioned in your last post, but I didn't find this one -> Microsoft-Windows-MediaPlayer-Package-amd64-en-us.cab
FastStone Capture - Screen Recorder error.PNG

Windows features - WMP installed.PNG
 
Last month, NTLite finally added the ability to integrate Wow64 packages into a 64-bit release (v2024.4.9880).

I've been wondering since then (but haven't tested), if adding the missing Wow64 packages would fix some of these problems. Search UUP dump for "Microsoft-Windows-Media-Features-Package" to find the other wow64 packages.
 
Hi,

Thanks for your reply. I just tested it few minutes ago and it's still not working, even with the latest version of NTLite.

1716538327443.png

Thanks!
KR
 
I know 24H2 is new.., but is there an updated version of Media Features Pack for build 21600?

The packs from UUP dump links provided in this thread can be integrated into 22631 and CU for 22631 updates it to 22631.3520.

Integrating Media Features Pack from same UUP dump links into 21600.560 and updating to 21600.712 does NOT update Media Features Pack files to 22631.3520. They are left outdated.
 
I know 24H2 is new.., but is there an updated version of Media Features Pack for build 21600?

The packs from UUP dump links provided in this thread can be integrated into 22631 and CU for 22631 updates it to 22631.3520.

Integrating Media Features Pack from same UUP dump links into 21600.560 and updating to 21600.712 does NOT update Media Features Pack files to 22631.3520. They are left outdated.
Why wouldn't you use the 21600 version of the same packages? I'm sure the actual program files aren't really changed, but they have different manifests.

22631.3668:
FileSHA-1Size
Microsoft-Windows-Media-Features-Package-amd64-en-us.cab0bce5c4d47917ef89acdc50e0d36938be8407ef5302.08 KiB
Microsoft-Windows-Media-Features-Package-amd64-en-us_c9edd5bf.cabc9edd5bfbc2b110473f3250d3d437dd27d3bc45032.1 KiB

26100.712:
FileSHA-1Size
Microsoft-Windows-Media-Features-Package-amd64-en-us.cabbc36dd75e7e53560572a2b8a042ae6b56745c9fc307.73 KiB
Microsoft-Windows-Media-Features-Package-amd64-en-us_0011607a.cab0011607a2c32b52f9910d7f5774ca19acafd0b0032.07 KiB
 
Back
Top