FindVUK tool - get VUK of all Blurays supported by DVDfab applications

[nalor]

Any chance you have done or could do a bit of digging into my aacskeys issue from earlier? Like I said, I'm reasonably confident that this method won't actually work for getting keys in my case, but a bit of output actually saying what went wrong would clarify that.

It only crashes? And no helpful details in the logfile?
You can try to add this to your config file:


[LogLevel]
Default=4


This logs on "trace" level, so "maybe" I've added more logoutput in the past the can help here :)

Please send me your logfile to check what's really going - thanks!

[magician]

It only crashes? And no helpful details in the logfile?

aacskeys 0.4.0f and earlier will simply hang when it encounters a UHD in the drive. I don't believe it crashes per se.

Maybe an option can be added so that in the AACSkeys mode, FindVUK will by default first check whether the disc in the drive is a UHD and if so, it emits an error or warning before delegating to the aacskeys binary. (But this will slow down the program for regular usage so that's why I'd want it to be configurable if you already know it won't work for UHD.)

Some time ago, in the Xreveal support page, a user reported that aacskeys has been privately updated to work correctly with AACS 2.x, but they didn't believe the code would be released publicly. Ultimately it may be useless unless you have access to a AACS2 HC and DK/PK.

[metalsonic88]

I think that actually I've been barking up the wrong tree. For starters, apparently the aacskey command fails on every disc I try to use. And in fact, it seems to actually be due to an issue with handling paths. I suspect that there are 2 bugs here:

1. I think the code handling the file path doesn't like spaces in it. Below is a small excerpt from my log right before the crash.


2026-04-25 23:07:57 # 3114 # [E] bluray_keydb / BRKDB_GetProcessingKeys / ERROR! File >c:\users\{user name with a space in it}\appdata\roaming\aacs\keydb.cfg< has never been opened!
2026-04-25 23:07:57 # 3114 # [E] bluray_aacskeys / BRAKEYS_CreateProcDevFile / Couldn't read ProcessingKeys from keydb.cfg file >#BRKDB_ERR_NOTOPEN<


That file certainly does exist at this location and has been opened. However...

2. The path used here does not respect what is assigned as the Main_Path for FindVUK. I have it set to use %ProgramData%\aacs and indeed, earlier in the log you can see it using this value


2026-04-26 02:45:17 # 665 # [I] FindVUK_Main / / Open Main-KEYDB file: >C:\ProgramData\aacs\KEYDB.cfg<
2026-04-26 02:45:17 # 666 # [I] bluray_keydb / _OpenFile_CFG / KeyDB file >c:\programdata\aacs\keydb.cfg< opened!


But obviously, as you can see above, it is instead trying to open the file at the default location associated with my user. The files at the user location are untouched from several years ago that I simply forgot to delete when I changed that setting. While the files do exist and aacskey should be able to use them, it's not the place where I want the files to live and I will be deleting them soon.

---

Anyways, I think that may solve some mysteries about this particular aspect of the program. But if I'm wrong and you want a full log file, let me know and I'll post it.

[magician]

aacskeys 0.4.0f and earlier will simply hang when it encounters a UHD in the drive. I don't believe it crashes per se.

Just to clarify my post was about a separate issue. Didn't mean to hijack the discussion. metalsonic88 was working with a regular BD.

[Warbington]

Just wanted to mention that the latest DVDfab release 13.0.6.0 (supports Pioneer drives) is NOT compatible with FindVUK.

[Toad King]

A small bug: If you add a disc using the aacskeys command any future sync has to do a full sync again instead of an update one. With the new server update the actual sync only takes a second or two but I figure I'd report it still.

Attached logs of the aacskeys command and subsequent sync one.

EDIT: The issue also seems to appear if you validate a disc and convert it from a legacy entry so maybe it's just something that happens whenever the local KEYDB file is updated? Attached that log as well.

[ZA0kFF4mIG0oC1]

Just wanted to mention that the latest DVDfab release 13.0.6.0 (supports Pioneer drives) is NOT compatible with FindVUK.

Tested 13.0.6.2 today and FindVUK works OK.