www.makemkv.com

eNoize wrote: Tue Jun 30, 2026 10:07 pm Disc type: 4K UHD
Disc dump filename: MKB20_v82_Click_25F1
..
Did you sync the public keydb within the last 15 minutes? NO

This disk was already added to the public KEYDB.cfg file on June 20th.

How is it possible that the drive's power supply isn't sufficient? I don't get the logic behind that. The computer's USB port can output 180 watts, and the cable can theoretically handle up to 240 watts. Plus, the drive just draws the power it needs. I still can't figure out which spec you're ...

I watched the reading process: it ran smoothly up to about 5,500 MB, then performance dropped again. As I’m writing this, the estimated time remaining has gone from 1:50 to 9:50.

And what makes you suspect the drive isn't getting enough power?

Your drive is struggling to read this particular ...

Sorry, wenn ich diesen "alten" Beitrag nochmal anstubbse. Ich hab die The Amateur BluRay hier und hab massiv Probleme beim Einlesen.

Hallo,

erstens hat Google Translate ein Limit von 3000 Zeichen ;).

Zweitens klingt es so, als verfüge MakeMKV bereits über alle erforderlichen Schlüssel zur ...

And the question is, what should I do? Should I just post the VUK et al. here? Or do I have to run FindVUK anyway? (I'm on Linux but probably it works through wine?)

P.S. AFAIK both the drive and the disc is non-BEE, if that matters. I mounted the filesystem and used rsync -rvc to compare its ...

Disc ID:d66aae87ee51eec72cec9997a30662fd5b6ac227
Disc dump filename:MKB20_v82_UPHE_UPK1-1135760R0_8700

This dump doesn't contain the metadata needed to calculate a full KEYDB entry, because you seem to have copied the files directly to your hard-drive and then used MakeMKV to open them from ...

Hi, thanks for your reply! I have MakeMKV 1.18.4 and downloaded the latest KEYDB.cfg today, but it still doesn't work.

You need to copy the latest KEYDB.cfg file into MakeMKV's data directory (i.e. where MakeMKV also writes its TGZ dump files) and then restart MakeMKV. Your disk has a fully ...

Hi, I have the German 4K Steelbook of Avatar: Fire and Ash. My disc variant is D5BC, which seems to be different from the BB78 variant already posted here. Volume key is still unknown.

The latest KEYDB.cfg file already has an entry for this disk. Have you also emailed your TGZ dump file to svq ...

Does that mean any time I run into a newly released disc that can't be read, I should re-download the keydb.cfg file from that link and copy that into the data folder again? Then, if that doesn't work, submit the dump files here?

The public KEYDB.cfg file is an optional extra database of keys ...

The .tgz dump file was emailed just now: MKB20_v82_HAMILTON_1604.tgz

Have you tried downloading the latest KEYDB.cfg file, copying it into MakeMKV's data directory (i.e. where MakeMKV also writes its TGZ dump files) and restarting MakeMKV?

If this doesn't work, could you upload your TGZ dump ...

I have another 4K UHD disc that is unreadable. MakerMKV displays the following information: "The volume key for the DVD/Blu-ray is unknown - the video cannot be decrypted. Opening the disc failed." Please decrypt it once, or do I need to add another file to the folder?

I believe this disk was ...

awshucks wrote: Thu Jun 18, 2026 3:25 pm Corrected it in my post, should have a link to the MKB20_v76_Akira_D33B.tgz now.

Thanks. BTW which UHD disk was that other MKB_RO.inf file from please? It doesn't correspond to any existing entry in the public KEYDB.cfg file, so maybe we could add that one too?

noonespecific wrote: Thu Jun 18, 2026 3:02 pm Sorry, I had meant to send this yesterday but the site seemed to be down. Here is the link to the dump

Could you adjust the "Share" option for that file please, so that people can access it?

awshucks wrote: Wed Jun 17, 2026 10:57 pm Disc ID: 914a94732597a494e088cb31479d86dd86addf0d
Disc dump filename: MKB20_v76_Akira_D33B

You have provided two different MKB_RO.inf files, but no file called MKB20_v76_Akira_D33B.tgz. Does either MKB_RO.inf file even belong to your "Avira" disk?

FWIW, my 1B1A version of Hoppers is also not able to be decrypted. I updated my KEYDB.cfg file right before this post with no luck. On MacOS with Pioneer drive.

I'm sure that KEYDB.cfg already has the 1B1A variant of "Hoppers". Have you installed the latest KEYDB.cfg file into the same directory ...