The volume key is unknown for this disc - video can't be decrypted
Failed to open disc
Using the latest MakeMKV, what can I do? If I missed something in the FAQs, I apologize.
Extracting the error file gives me this:
Debug log started at Thu Dec 18 19:56:37 2025 , written by MakeMKV v1.18.2 win(x64-release)
001005:0000 MakeMKV v1.18.2 win(x64-release) started
Using 262272KB for read cache.
Network access is ENABLED, CURL version 7.72.0/Schannel/1.41.0 (x86_64-pc-win32) , proxy server not set.
WinCdArb=v1.2.0_tiny win(x64-release)
DEBUG: Code 3 at R/Ru3B(Mxaw 4&z'5FC}$>4::29395310
SDF v0a3: HL-DT-ST_BD-RE__WH16NS40_1.00_211304041441_K9LF22G5602
DEBUG: Code 3 at R/Ru3B(Mxaw 4&z'5FC}$>4::29395310
SDF v0a3: HL-DT-ST_BD-RE__WH16NS40_1.00_211304041441_K9LF22G5602
001011:0000 Using LibreDrive mode (v06.3 id=7973CDD17D88)
003007:0000 Using direct disc access mode
005085:0000 Loaded content hash table, will verify integrity of M2TS files.
DEBUG: Code 2147483648 at 3}LEXDFfdV,&S#:f:121265499
003310:0000 This disc uses newer version of AACS protection. Please let us know about it by visiting http://www.makemkv.com/a/?12BzUQyCLTkGv ... mrTm0LiQ==
DEBUG: Code 0 at 3}LEXDFfdV,&S#:f:29398070
Thanks!
The Cure - Troxy Live 2024 Blu-Ray error
Re: The Cure - Troxy Live 2024 Blu-Ray error
Regular blu-rays that use the latest version of encryption, AACS v82, have to handled slightly differently than regular blu-rays with older versions of encryption.
MakeMKV supports two different disc decryption mechanisms. The built-in mechanism is called hashed keys and it works with all dumps from MakeMKV regardless of the brand of drive. When there is not a key for you disc and MakeMKV produces a dump, email that dump to svq@makemkv.com. Eventually a hashed key will be produced and MakeMKV will automatically download it as needed.
The other source for decryption keys is the public keyDB. The first post in the Public KeyDB Disc Submissions thread includes a template and instructions on how to submit dumps for inclusion in the keyDB. It also has links to where the keyDB can be downloaded, utilities to help keep it updated, and where to put the file so MakeMKV can use it. Dumps from Pioneer drives can't generally be used for keyDB submissions. However, MakeMKV can use the keys provided by the public keyDB with any brand of optical drive.
These two ways to decrypt discs can be used together. If you can submit a dump to the keyDB you can also email it to svq@makemkv.com. Accidental duplicates emailed to MakeMKV aren't a big deal but duplicates submitted to the keyDB should be avoided if possible.
MakeMKV supports two different disc decryption mechanisms. The built-in mechanism is called hashed keys and it works with all dumps from MakeMKV regardless of the brand of drive. When there is not a key for you disc and MakeMKV produces a dump, email that dump to svq@makemkv.com. Eventually a hashed key will be produced and MakeMKV will automatically download it as needed.
The other source for decryption keys is the public keyDB. The first post in the Public KeyDB Disc Submissions thread includes a template and instructions on how to submit dumps for inclusion in the keyDB. It also has links to where the keyDB can be downloaded, utilities to help keep it updated, and where to put the file so MakeMKV can use it. Dumps from Pioneer drives can't generally be used for keyDB submissions. However, MakeMKV can use the keys provided by the public keyDB with any brand of optical drive.
These two ways to decrypt discs can be used together. If you can submit a dump to the keyDB you can also email it to svq@makemkv.com. Accidental duplicates emailed to MakeMKV aren't a big deal but duplicates submitted to the keyDB should be avoided if possible.