Vanwege onderhoudswerkzaamheden die uw ervaring zouden moeten verbeteren, heeft deze website beperkte functionaliteit. Als een artikel uw probleem niet verhelpt en u een vraag wilt stellen, kan onze ondersteuningsgemeenschap u helpen in @FirefoxSupport op Twitter en /r/firefox op Reddit.

Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Meer info

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

H.264 (MP4) doesn't work after Windows 10 update to build 10586

  • 4 antwoorden
  • 1 heeft dit probleem
  • 1 weergave
  • Laatste antwoord van akkenoth

more options

After updating Windows 10 (64-bit) to build 10586, H.246/MP4 decoding doesn't work.

Youtube ( https://www.youtube.com/html5 )displays red !-s in both 'H.264' and 'MSE & H.264' fields, and HTML5 test video displays 'Video in supported format and MIME type not found' ( http://www.quirksmode.org/html5/tests/video.html ).

Everything was working just few hours ago (before update).

edit: as it's quite important, the problem (and solution) applies to Windows 10 Home/Pro/* N and KN editions (without Media Feature Pack installed by default).

After updating Windows 10 (64-bit) to build 10586, H.246/MP4 decoding doesn't work. Youtube ( https://www.youtube.com/html5 )displays red !-s in both 'H.264' and 'MSE & H.264' fields, and HTML5 test video displays 'Video in supported format and MIME type not found' ( http://www.quirksmode.org/html5/tests/video.html ). Everything was working just few hours ago (before update). edit: as it's quite important, the problem (and solution) applies to Windows 10 Home/Pro/* N and KN editions (without Media Feature Pack installed by default).

Bewerkt door akkenoth op

Gekozen oplossing

I have found the source of the problem and a solution.

The real problem was that my version of Windows was a N one (without media features, including codecs) and updating it to version 1511 (build 10586) silently removed/disabled a previously installed Media Feature Pack and reinstalling the old update file is not reenabling it.

Solution: install KB3099229, the new 'release' of Media Feature Pack.

Another thing is that Firefox silently depends on the MFP without notifying user that it might be missing...

Dit antwoord in context lezen 👍 0

Alle antwoorden (4)

more options

Are there any warning messages in the graphics section on the "Help > Troubleshooting Information page"?

You can also check media prefs (search media.*enabled) on the about:config page. You can open the about:config page via the location/address bar. You can accept the warning and click "I'll be careful" to continue.

more options

No warning messages on that page, though 'hardware H264 decoding' reports 'false' (if that is anyhow relevant).

The only settings modified in about:config page are:

  • media.gmp-gmpopenh264.enabled
  • media.mediasource.webm.enabled
  • media.peerconnection.video.h264_enabled

I've tried resetting them to default settings and also enabling the options that are disabled by default but to no avail.

The playback worked fine before, the only thing that has changed was the mentioned windows update.

more options

I have installed a fresh copy of Firefox Developer Edition to have a fresh&clean environment and H.264 didn't work there either, so the issue is somehow related to what has changed in the newest build of Windows and not to Firefox itself.

If I'll manage to find a fix for that I'll report back with the solution.

more options

Gekozen oplossing

I have found the source of the problem and a solution.

The real problem was that my version of Windows was a N one (without media features, including codecs) and updating it to version 1511 (build 10586) silently removed/disabled a previously installed Media Feature Pack and reinstalling the old update file is not reenabling it.

Solution: install KB3099229, the new 'release' of Media Feature Pack.

Another thing is that Firefox silently depends on the MFP without notifying user that it might be missing...