www.makemkv.com

Disc type: UHD
Disc dump filename: MKB20_v77_Fast_and_Furious_6_3A77
Drive: BDR-XD07U
Drive firmware: 1.03
LibreDrive status: Enabled
Did you sync the public keydb within the last 15 minutes? Yes
Have you verified that all submission links are accessible in incognito/private browsing? Yes
MKB_RO.inf link (Do not just extract the MKB_RO.inf file from the disc dump file - copy it from the disc): https://drive.google.com/drive/u/0/fold ... 8fGY-7r5j_
Disc dump link: https://drive.google.com/drive/u/0/fold ... 8fGY-7r5j_

Hello. So I have an old title (regular / non-UHD BD) with MKBv37 and this drive that hasn't been inserted with disc with a newer MKB. With the host cert/key provided in KeyDB I've managed to obtain the VUK through libaacs, and I would like to have it added to the KeyDB (if key for such older title are still being accepted).

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 content with an encrypted backup made with MakeMKV, and as per the result they are identical. However I haven't exactly "validated" the VUK by decrypting it with libaacs (and compare the result with the decrypted backup from MakeMKV).

Deathstalker 1983

https://drive.google.com/drive/folders/ ... 1iJW1Oplp5

DeathStalker II Arrow Video US

https://drive.google.com/drive/folders/ ... fM_unQXwqt

Deathstalker 2025 Arrow Video US Version

https://drive.google.com/drive/folders/ ... yrvdPoJ9rm

Disc type:UHD
Disc ID:B3BCCC71180573C3E75634A78043466957B043A1
Disc dump filename:MKB20_v82_LA_COLLINE_A_DES_YEUX_-_4K_UHD_7CC6
Drive:BW-16D1H-U
Drive firmware:A204
LibreDrive status:Enabled
Did you sync the public keydb within the last 15 minutes? YES
Have you verified that all submission links are accessible in incognito/private browsing? YES
MKB_RO.inf link :https://drive.google.com/file/d/1fVsk44 ... VMi9CgaawT
Disc dump link:https://drive.google.com/file/d/1Zqx7U7 ... V3ish7Ema8

tomty89 wrote: Wed Jun 24, 2026 9:34 pm 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 content with an encrypted backup made with MakeMKV, and as per the result they are identical. However I haven't exactly "validated" the VUK by decrypting it with libaacs (and compare the result with the decrypted backup from MakeMKV).

FindVUK works fine inside a wineconsole on Linux. You would need to add an entry for your disk to your KEYDB.cfg file, and then execute "findvuk validateDisc" to have FindVUK prove that your entry is correct, and then upload it into the database. For example: where your UHD drive would be identified by letter E.

You calculate the disk's ID like this: If your disk did use BEE then either libaacs would need to know the correct RDK to use, or you'd need to use MakeMKV to disable bus encryption before invoking FindVUK. Note also that FindVUK.ini has a "Disable_Bus_Encryption_Cmd" option:

If you know the RDK then you don't need to disable bus encryption: Or if you need a "dummy" command for FindVUK to execute so that it knows you have already disabled BE yourself: Remember that FindVUK's libaacs will have a totally different KEYDB.cfg file to $HOME/.config/aacs/KEYDB.cfg, and cache to $HOME/.cache/aacs