# Bitmovin defaults to playready (Chrome on Win)

**URL:** <https://community.bitmovin.com/t/bitmovin-defaults-to-playready-chrome-on-win/3833>\
**Category:** Discussion\
**Tags:** drm, bitmovin\
**Created:** [December 3, 2025, 1:25pm UTC](https://community.bitmovin.com/t/bitmovin-defaults-to-playready-chrome-on-win/3833 "2025-12-03T13:25:33Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dario.Fiore](https://sea1.discourse-cdn.com/flex015/user_avatar/community.bitmovin.com/dario.fiore/32/1036_2.png) [@Dario.Fiore](https://community.bitmovin.com/u/Dario.Fiore)\
**Post date:** [December 3, 2025, 1:25pm UTC](https://community.bitmovin.com/t/bitmovin-defaults-to-playready-chrome-on-win/3833/1 "2025-12-03T13:25:33Z")

</div>

Hello everyone, for the past few weeks (possibly after a recent chrome update), when passing multiple DRM systems to Bitmovin it defaults to playready. A few weeks ago it was correctly picking widevine, which makes sense. Do you have any idea why this changed? Is anyone else experiencing the same issue? I don’t want to introduce `preferredKeySystems` because I don’t want to break other devices, but it would still be great to understand why chrome broke the compatibility.

---

<div class="post-metadata">

**Author:** ![Dario.Fiore](https://sea1.discourse-cdn.com/flex015/user_avatar/community.bitmovin.com/dario.fiore/32/1036_2.png) [@Dario.Fiore](https://community.bitmovin.com/u/Dario.Fiore)\
**Post date:** [December 9, 2025, 7:07pm UTC](https://community.bitmovin.com/t/bitmovin-defaults-to-playready-chrome-on-win/3833/2 "2025-12-09T19:07:25Z")

</div>

It seems that Chrome is experimenting with PlayReady support on Windows 11. The feature is behind an experimental flag called **HardwareSecureDecryption** , so disabling it solves the issue.

 ![image](https://us1.discourse-cdn.com/flex015/uploads/bitmovin/original/2X/7/7a813fa2a461e5f1b6f78de969786e319e878483.png)