www.makemkv.com

HSamwel wrote: Sat Oct 18, 2025 11:28 am How about now? Anything changed with regarding to free time?

I would like to add to my previous request.
Could you add a configurable list of paths to do this copy to? I have seen other apps that put the kayDB.cfg file
at different paths.

Wish....granted.

New and improved! KeyDB Helper 1.0.2.0 has been released

* Removed fix button as it was no longer needed
* Added settings button that'll allow you to configure additional directories to copy the keydb.cfg file to after synchronization (see, wish granted lol)
* Added experimental feature to detect discs with an AACS directory that are not actually encrypted

That last one may or may not work. I have no way of testing it as I have no discs like that in my collection. But it'll give you a message during the Disc Info feature if it detects that situation. In which case you can do a disc folder backup in MakeMKV and then delete the AACS directory, then open the folder with MakeMKV and it should in theory work.

Enjoy!

P.S. Free time is still limited but wanted to at least get this done for everyone.

Hello, I appreciate the KeyDB_Helper app since it makes getting updated keys a lot easier . I originally unzipped and ran the installer executable in my Downloads directory and now no matter what I try, I cannot have KeyDB in another location.

So for example, it's in my F:\Downloads\KeyDB_Helper_1.0.2.0\ directory. I first tried moving the KeyDB_Helper_1.0.2.0\ folder to another location. When I ran the program and hit Synchronize, it threw up an error about not finding the backup keydb file even though it's located in the location it says it can't find it (in both the Downloads and new locations the file is 0 kb and empty):

"00:25:08 - Open Backup-KEYDB file: >C:\Program Files (x86)\KeyDB_Helper_1.0.2.0\FindVUK\VUKbackup\KEYDB.cfg<
00:25:08 - ERROR! Couldn't open backup keydb file!"

So then I attempted to run the installer executable from a different location thinking that it configures something during the installation process. That too, resulted in the error message above. The only way I've been able to continue using the app is by keeping the installer in the Downloads directory.

You moved it to a directory it doesn't have access to write to. You can't do that.

Sent from my SM-S938U1 using Tapatalk

SamuriHL wrote: Fri Jan 09, 2026 12:15 am * Added experimental feature to detect discs with an AACS directory that are not actually encrypted

That last one may or may not work. I have no way of testing it as I have no discs like that in my collection. But it'll give you a message during the Disc Info feature if it detects that situation. In which case you can do a disc folder backup in MakeMKV and then delete the AACS directory, then open the folder with MakeMKV and it should in theory work.

The detection works on Arrow Video's City on Fire UHD.

Scavenger wrote: Fri Jan 09, 2026 2:44 pm

SamuriHL wrote: Fri Jan 09, 2026 12:15 am * Added experimental feature to detect discs with an AACS directory that are not actually encrypted

That last one may or may not work. I have no way of testing it as I have no discs like that in my collection. But it'll give you a message during the Disc Info feature if it detects that situation. In which case you can do a disc folder backup in MakeMKV and then delete the AACS directory, then open the folder with MakeMKV and it should in theory work.

The detection works on Arrow Video's City on Fire UHD.

Sweet! Thanks for the report. I appreciate it.

I just released a new KeyDB Helper 1.0.2.1.

Nothing earth shattering it's just a few bug fixes and some formatting changes. When FindVUK encounters a new drive during validate, it can hang and it'll never recover. That's been fixed.

When keydb.cfg is locked by a running findvuk process, it'll now kill the running findvuk process to release the keydb.cfg file. This can happen periodically if findvuk doesn't exit gracefully. Sometimes when findvuk updates itself this can happen.

The formatting changes simply add a bit of color and alignment to make it easier to read the reports. The status will be green if it's complete, yellow if it's incomplete (which means MakeMKV can't use that keydb entry as it contains no VUK), and red for incomplete...That means post yourself a dump file so they can add it to the keydb for you.

Enjoy!

I am just here to say thank you for building this.

I had issues with backing up my copy of Pee-Wee's Big Adventure and this tool worked like a charm. I also validated it as well to pay it forward and help out.

I will be doing this with all of my new discs moving forward.

Thank you, again!

Awesome!

Sent from my SM-S938U1 using Tapatalk

Thank you SamuriHL for this too[*]l! Using a newly released disc, MakeMKV was unable to get the Volume Key. That is, until I looked through the forum, found KeyDB_Helper and put it to work on my Win11 PC.

One tip for newbies like me:
If KeyDB_Helper quits after running its initial download -
Open it again,
'cancel' download,
tap 'settings',
add a folder (e.g. MakeMKV) location,
then tap 'Synchronize'

That fixed my runtime issue and I now have the volume key to copy the newly released Ben Hur.
Thanks again

Hey. Does KeyDB Helper sync the entire file from scratch every time for you too? It used to only sync fragments of the file, but now it syncs the entire file at a very slow speed.

boguslecina wrote: Sat Mar 07, 2026 11:59 am Hey. Does KeyDB Helper sync the entire file from scratch every time for you too? It used to only sync fragments of the file, but now it syncs the entire file at a very slow speed.

Check this:

https://forum.doom9.org/showthread.php?t=172472&page=53

boguslecina wrote: Sat Mar 07, 2026 11:59 am Hey. Does KeyDB Helper sync the entire file from scratch every time for you too? It used to only sync fragments of the file, but now it syncs the entire file at a very slow speed.

FindVUK and their server problem, not a KeyDB Helper issue.

SamuriHL wrote: Sat Mar 07, 2026 4:07 pm

boguslecina wrote: Sat Mar 07, 2026 11:59 am Hey. Does KeyDB Helper sync the entire file from scratch every time for you too? It used to only sync fragments of the file, but now it syncs the entire file at a very slow speed.

FindVUK and their server problem, not a KeyDB Helper issue.

Couldn't you add that when starting synchronization, before starting the synchronization itself, it strictly changes the timestamp format in the keydb_fvhash.ini file?

I suspect that you will change it faster than they will fix it.

For now, I've worked around this by writing a script that I've attached to the existing my shortcut to the KeyDB Helper app, and it first changes the format and then launches your KeyDB Helper app.

I don't have time right now. It's really not my problem to fix as Nalor really needs to deal with it either on his server or in FindVUK.

https://forum.doom9.org/showthread.php? ... ost2029127

And he's on top of it already.