Bitmovin defaults to playready (Chrome on Win)

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.

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.