Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

Pesquisar no apoio

Evite burlas no apoio. Nunca iremos solicitar que telefone ou envie uma mensagem de texto para um número de telefone ou que partilhe informações pessoais. Por favor, reporte atividades suspeitas utilizando a opção "Reportar abuso".

Learn More

Firefox clearkey addon crash when Applocker is in use drm content does not work.

  • 1 resposta
  • 0 têm este problema
  • 36 visualizações
  • Última resposta por Mike Kaply

more options

We have Firefox-ESR in use and we are using Applocker.

When we enable applocker dll Rule policys and start https://shaka-player-demo.appspot.com page clearkey addon crashes.

We have allowed widevinedrm.dll in applocker rule policys, and we have used Process Monitor to track which dll file / files are being "locked" but we cant seem to pinpoint it.

Where does Firefox-ESR run DRM content and which dll files are needed to run ?

What we know that it is caused by applocker DLL rule policys, when disabling it clearkey addon does not crash and drm content can be played.

Also Applocker eventlogs does not show anything related to this.

br Ben

We have Firefox-ESR in use and we are using Applocker. When we enable applocker dll Rule policys and start https://shaka-player-demo.appspot.com page clearkey addon crashes. We have allowed widevinedrm.dll in applocker rule policys, and we have used Process Monitor to track which dll file / files are being "locked" but we cant seem to pinpoint it. Where does Firefox-ESR run DRM content and which dll files are needed to run ? What we know that it is caused by applocker DLL rule policys, when disabling it clearkey addon does not crash and drm content can be played. Also Applocker eventlogs does not show anything related to this. br Ben

Modificado por chef a

Todas as respostas (1)

more options

I would recommend opening up a bug in bugzilla for this.