When a Blu-ray drive "sees" an MKBv82 disc, it may update its internal revocation list, effectively blocking previously working certificates from being used with any disc moving forward. This is often the cause behind the common MakeMKV error: "Can't read AACS VID from disc - most likely current AACS host certificate is revoked by your drive" . Challenges for Decryption and Ripping
Right, once your drive sees v82, the MKB revocation list gets updated and the cert that used to work is now revoked. So until (if? Doom9's Forum View Single Post - Up to MKB v68 KEYDB.cfg file mkbv82
Additionally, is "mkbv82" a specific prompt, title, or theme that I should be working with? Please provide more information so I can better understand and assist you. When a Blu-ray drive "sees" an MKBv82 disc,
AACS protection relies on a , a data structure on the disc that allows authorized players to calculate a "Media Key". Each new version of MKB can contain a Revocation List , which "kills" compromised host certificates or device keys used by unauthorized software. So until (if
Native support for MKBv82 in tools like MakeMKV often lags behind the commercial release of these discs.
Media Key Block version 82 (MKBv82) is an Advanced Access Content System (AACS) update for Blu-ray discs designed to revoke compromised player keys and prevent unauthorized decryption. The release of this version often causes decryption failures in ripping software like MakeMKV, necessitating community-shared updates to restore functionality. For more information, you can visit the MakeMKV Forum.