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

[candela]

In all versions except the current version,
Does it mean that the feature is always disabled?
Does Other than the latest version, 11.0.8.6,
that mean the feature is disabled?

It started when DVDFab added UHD support in Passkey v9.3.0.2 early 2018. So anything newer only uses UK so FindVUK can only get UK. Maybe you can still get other keys with FindVUK using older DVDFab versions for discs with lower MKB versions (like < 60). But for those discs that maybe will work you can get all keys yourself with aacskeys using public PK and HC

[Bomum]

It started when DVDFab added UHD support in Passkey v9.3.0.2 early 2018. So anything newer only uses UK so FindVUK can only get UK. Maybe you can still get other keys with FindVUK using older DVDFab versions for discs with lower MKB versions (like < 60). But for those discs that maybe will work you can get all keys yourself with aacskeys using public PK and HC

Is there any problem if you have the latest Fab, FindVUK, aacskeys?

[Losko]

Of course I could add some kind of incremental download specifically for the synchronisation - but honestly this would be a huge rework of the current setup and I cannot afford the time for this.
Hey, this is exactly what git was designed for!
git is great when managing text files with incremental modifications, and it's very, very efficient when synchronizing local and remote copies.
What if FindVUK did:

first launch? then do 'git clone', else 'git pull'
do your usual stuff
exiting: new entries? then do 'git push'

If I think at the keys database as a repository, then the whole scenario seems so simplified!
(and, btw, there are plenty of git hosting sites out there)

[nalor]

I'm not sure that GIT is really an option - because the problem is that not all changes of every user are relevant for all the other users...
Usually GIT is used in case each change is relevant for everyone else .. but in our case there might be manual changes to the file that might remove data from the repository.
And as always with systems like GIT theres always the option that merge conflicts might occur - and the only way to handle them easily would be to perform a hard-reset to the current repository.

Finally I just want to tell that the only reason for me to start the online database has been the strange disappearance of Starbuck ...

But in case someone else wants to create a better solution I've absolutely no problem to stop my current implementation or add support for the new approach to FindVUK.

[richy]

Hi nalor!

The upload part when submitting new keys always seems to work fine and obviously it's just the download part of a sync where the free hosting problems kick in. I was going to suggest some sort of stop-gap measure like a monthly keydb.cfg update via tinyupload.com (or similar) so people could keep relatively up to date without needing to hammer the free host so much.

However, out of curiosity I just tried a sync for the first time in ages and the speed seemed to be a lot better and I noticed that it downloaded about 11mb instead of the full 31mb and then proceeded to unpack it. Basically, I was able to do a full sync with no problems. I'm guessing you've made a few changes somewhere so a sync doesn't require so much data to be downloaded? If so, it certainly seems to be working ok at the moment.

Just thought I'd mention it in case you wanted any feedback(!?) and also thought I'd just say a quick thanks for all the work you've put in to FindVUK :)

[nalor]

I've changed only something really small - but maybe this did the trick.
In the beginning the file to download has been <10MB and everything has been fine.
Than at some point in time the file got bigger than 10MB and personally I think it still worked, but later on it started to get really slow.
In parallel I noticed that when downloading the file with a browser I don't get a progress information and started to analyze why this isn't working and finally got the info from the bplaced-support that each php-interpreter is limited to 10MB of memory and as the file is transmitted by a php-file and does exceed the assigned memory size, the filesize is not available in advance any longer and therefore it's not available to the browser.
So finally I've changed the behaviour so that the php-file just takes care the file is updated in case it's necessary and afterwards there's a redirect to the file in the filesystem.
So the data is now delivered directly by the webserver and a few days after this change the download problems disappeared...

Don't know if it's really related or if it's just a coincidence - but finally everything back to 'useable' :)

[nalor]

Just want to tell that I'm working on a better synchronization feature - I think it will speed up the sync dramatically.
Basically FindVUK will store a hash of the file after a full-sync and the date of the sync and as long as the file is not modified externally it will just request delta-files for synchronisation (such a file is around 200kb for the last 60 days).
The server part is already done - see here:
Delta File since 2020.05.04 23:00:00 (fvonline-db.bplaced.net/fv_download.php?lang=deu&deltadate=20200504t230000)

In case the requested date is older than 60 days or in the future or cannot be parsed at all, the full file is offered instead. The delta file includes all entries that got either created or modified in this time area.

Next I'll implement the required changes in FindVUK - but this will take a few days.

Small note:
It's also possible to use relative deltadate attributes - e.g. this here will always return a file with all entries changed during the last 24h:
Changed entries in last 1 day (http://fvonline-db.bplaced.net/fv_download.php?lang=eng&deltadate=-1%20days)

[nalor]

Released FindVUK 1.34 - it includes the delta-synchronization and in my small tests it's working fine.

As long as the keydb.cfg isn't modified manually the delta sync is active. To check for modifications a hash is stored in a keydb_hash.ini file together with a timestamp used for the delta-sync. The timestamp is the time of the last change in the online database - it has nothing to do with the time of the last synchronisation.

The easiest way to trigger a full-sync again is to delete this ini file.

[Roof Tile]

Wanted to say thanks for your efforts to help expand the control people have over their material. You, candela, mick0, and many more have allowed me and others to overcome some of the key issues with owning Blu-rays and you all have my gratitude for that.

Beyond the simple thanks, I believe I have something that might be of interest to you. I've been using your program to get the various codes and keys and whatnot from my own Blu-rays uploaded to the main database you have. However, a strange error occurred when I used it on my copy of "The Usual Suspects". It was the first movie I had to enter the name for manually and it seemingly didn't like that. However, I then had to do the same for "Total Recall" and that went just fine without any weird error.
Don't really know what the issue is but I thought you'd maybe find it helpful. Just in advance, I hope I got the right parts for this for you to look at and sorry if I didn't.
*Wanted to use the scrolling CODE phrasing to put it up here and have a nicer flow, but it would have taken multiple posts so I just put it on TinyUpload instead as a RAR.*

Tiny Upload Link: http://s000.tinyupload.com/?file_id=00047336899647016775

PS. I replaced my account name with *Account Name* in the logs. Hope that's ok.

[nalor]

This problem is one I already know -but I still don't know how to solve it properly. The uploads from findvuk are directly processed and written to the database, this is working fine as long as everything is in perfect condition.
But with discs that require a manual title input there might be the chance that it already got uploaded previously with a different title. In the current example the disc got uploaded the first time at 23.03.2019 with a title 'THEUSUALSUSPECTS' and now you're entering another title 'The Usual Suspects' and finally my script only knows that those are not equal - but cannot decide which title is better and therefore the 'manual processing required' result is returned.

All those uploads are now flagged with 'manual processing required' and from time to time I'll check them manually and decide what to do.

But I think it might be an improvement to still report it as success instead of showing an error....

[Roof Tile]

Ah got it. Thanks for looking into it and for the succinct explanation!

-----Didn't want to make two posts one after another so I'm just editing this one-----
Encountered a new error. I used the program on my Guardians of the Galaxy and Star Trek The Motion Picture Blu-rays (the Star Trek one is from that big 50th Anniversary collection in case that matters) but it spit out an error at the end about something involving a "hash file". I think the uploads for both of the discs to the database went fine, as the log says that they did. However, I wanted to let you know before I continued doing any more discs just in case it was something important that could corrupt the data or something.

Just in case these details matter, I updated Passkey from 9388 to 9389 (the logs say that's ok but I just wanted to let you quickly know), I got a new version of the KeyDB (6-14-20) before I used the program with my discs to make sure it was as up to date as possible before adding new entries, and updated my VUK program to the new 1.34 version by extracting everything in the folder and letting it overwrite everything it wanted.

Here's a link to the Tiny Upload of the Logs: http://s000.tinyupload.com/?file_id=77372597325744329857

[nalor]

Thanks for reporting!
Just checked my code and I think it's a stupid error from my side. At the end of each scan it tries to update the stored hash of the keydb.cfg file so that it's still detected as 'unchanged' - but this is only possible in case the hash-file is really available.
I never tried it without this file ... and I guess this is the situation in your case.

Please either:

execute a synchronization - this should create the file automatically
or create an empty textfile named 'keydb_fvhash.ini' next to the keydb.cfg file


I think both options should help.

I'll fix the bug with the next release.

[Roof Tile]

Glad to help and will do! Just to ask though, what does the hash-file do exactly? Do I need to redo my previous disc reads to make sure they have everything correct, or is it an "extra" sort of thing to make things easier for collecting info or uploading things?

[nalor]

Glad to help and will do! Just to ask though, what does the hash-file do exactly? Do I need to redo my previous disc reads to make sure they have everything correct, or is it an "extra" sort of thing to make things easier for collecting info or uploading things?Hash file is a new thing that is only used for the improved synchronisation, it has nothing to do with the result of a disc read.

So there is really no need to redo your reads.

Gesendet von meinem H8324 mit Tapatalk

[Roof Tile]

Ah got it. Thank you for the explanation.

[Buck]

I came across a bug in the new version. Apparently, when writing to the "keydb" file, FindVUK 1.34 was looking for uppercase letters "KEYDB". I had lowercase letters "keydb" and it failed that operation with:

13:11:55 - Successful upload to OnlineDB
13:11:56 - ERROR! Couldn't open hash-file >C:\Users\***\AppData\Roaming\aacs\keydb_fvhash.ini<
13:11:56 - ERROR! Couldn't update hash file >C:\Users\***\AppData\Roaming\aacs\KEYDB.cfg<
13:11:56 - Eject the disc now from drive >E:\<


When I changed my keydb.cfg to uppercase "KEYDB.cfg", it completed that operation with:

13:19:38 - Successful upload to OnlineDB
13:19:38 - Eject the disc now from drive >E:\<

Also, I don't see a "keydb_fvhash.ini" file in my directory. So it doesn't create one when there is none. That's a problem, too.

[nalor]

I came across a bug in the new version. Apparently, when writing to the "keydb" file, FindVUK 1.34 was looking for uppercase letters "KEYDB". I had lowercase letters "keydb" and it failed that operation with:

13:11:55 - Successful upload to OnlineDB
13:11:56 - ERROR! Couldn't open hash-file >C:\Users\***\AppData\Roaming\aacs\keydb_fvhash.ini<
13:11:56 - ERROR! Couldn't update hash file >C:\Users\***\AppData\Roaming\aacs\KEYDB.cfg<
13:11:56 - Eject the disc now from drive >E:\<


When I changed my keydb.cfg to uppercase "KEYDB.cfg", it completed that operation with:

13:19:38 - Successful upload to OnlineDB
13:19:38 - Eject the disc now from drive >E:\<

Also, I don't see a "keydb_fvhash.ini" file in my directory. So it doesn't create one when there is none. That's a problem, too.

Hi! I think it's not related to the case of the filename - the uppercase 'KEYDB.cfg' in the error message is just because the filename is created internally and I wrote it uppercase there ;)

So I guess when you rename back to 'keydb.cfg' it's also working - very likely it's been a problem with the first run.

[nalor]

Uploaded a new release 1.35

It includes 2 changes:
-> FIX for the error message when using without synchronization
-> an auto-update function ;) I know it's not really required because I don't update that often - but I wanted to try and I think it's working well, at least in my tests.

It can be disabled in the ini-file.

Additionally I've linked to the website of the online-database for download instead of using tinyupload.

[ZampNoxis]

This is my first time using this forum, so I apologize if this isn't the proper thread to post this. I have some VUKs that aren't in the online database and would like to add them to my local keydb.cfg file and upload those changes to the online database for others to use. I obtained these VUKs by adding the DKs, PKs, and HCs from this post to my local keydb.cfg file and playing the Blu-rays in VLC: https://forum.doom9.org/showthread.php?p=1883655#post1883655

The VUKs for each disk showed up in AppData\Roaming\aacs\vuk. However, I don't know how to go about doing the proper formatting for the disk title, the VUK, and all the other necessary entries to match the existing entries in keydb.cfg. Do I have to manually input everything in my local keydb.cfg file or is this formatting usually done automatically by FindVUK when using it with a DVDfab program?

[qyot27]

This is the per-disc key backup script I use. Grew out of a solution I used prior to switching to FindVUK, but then repurposed to pretty-print things and continue to make sure that I have backups of the keys for the discs I actually own.
#!/bin/bash

VOLUMEDRIVE="$(ddwin64 --list 2>&1 > /dev/null | grep -A1 CD-ROM | grep Mounted | tail -c4)"
VOLUMENAME="$(cmd //c "vol $VOLUMEDRIVE" | grep "Volume in drive" | sed 's/is/\t/' | cut -f2 | sed 's/^ //')"
echo "$VOLUMENAME" > "$VOLUMENAME.aacsinfo.txt"
aacs_info "$VOLUMEDRIVE" >> "$VOLUMENAME.aacsinfo.txt"
DISCID="$(aacs_info "$VOLUMEDRIVE" | grep "Disc ID" | cut -f2 -d : | sed 's/ //g')"
VID="$(aacs_info "$VOLUMEDRIVE" | grep "VID" | cut -f2 -d : | sed 's/ //g')"
#VUK="$(cat $(echo $APPDATA\\aacs\\vuk\\$DISCID) | tr '[:lower:]' '[:upper:]')"
MEDK="$(aacs_info "$VOLUMEDRIVE" | grep -w "MK" | cut -f2 -d : | sed 's/ //g')"
FULLKEYS="$(cd "/e/Programs/aacskeys/bin/win64/" && aacskeys.exe "$VOLUMEDRIVE" v "$VID")"
VUK="$(cd "/e/Programs/aacskeys/bin/win64/" && aacskeys.exe "$VOLUMEDRIVE" "$VID" | grep "Volume Unique Key" | cut -f2 -d : | sed 's/ //g')"
MKB="$(grep MKB "$VOLUMENAME.aacsinfo.txt" | cut -f2 -d : | sed 's/ //g')"
fromdos "$VOLUMENAME.aacsinfo.txt"
sed -i '/VID/aVUK : '"$VUK"'' "$VOLUMENAME.aacsinfo.txt"
todos "$VOLUMENAME.aacsinfo.txt"

grep $DISCID "$APPDATA\\aacs\\KEYDB.cfg" > "$VOLUMENAME.keydb.txt"

mkdir -p aacsbk/vuk
echo "$VUK" > aacsbk/vuk/"$DISCID"

echo "$FULLKEYS" > "$VOLUMENAME.fullkeys.txt"

echo "0x$DISCID = $VOLUMENAME | V | 0x$VUK | M | 0x$MEDK | I | 0x$VID ; MKBv$MKB" > "$VOLUMENAME.keydb_forinsert.txt"

Requires ddwin, aacs_info (with working PK/DK/Cert in KEYDB.cfg), aacskeys (with working keys/cert in the right files), and standard GNU userland on Windows (MSys2, or maybe Cygwin if you change the paths to account for Windows drives being under /cygdrive there).

Note: it does use the old key order, but FindVUK adjusts it when it verifies the info. It also assumes aacskeys resides in E:\Programs\, so adjust that accordingly, especially if on something other than Windows.

Run the script first, see what differs between the *.keydb.txt and *.keydb_forinsert.txt. If the plain keydb output either lacks some keys or has NOTVALIDATED / LEGACY, then copy the line (or just the missing parts of the line) from _forinsert.txt into the main keydb.cfg.

Then optionally run FindVUK to let it fix things up (maybe just Synchronize if you don't care about some of the meta stuff), and then to re-verify, run the above script again and compare the *keydb/*forinsert files again to ensure things look okay.

The script is a little older, obviously; with libaacs allowing the MK cache and such now, those values could probably be read out a lot easier than they had to be at the time (although since the VUK isn't printed by aacs_info, that still needs aacskeys).

[ZampNoxis]

If I was to use FindVUK in conjunction with a DVDfab product, would it automatically output a properly-formatted entry for keydb.cfg? If not, I'll use the script. Concerning aacs_info and aacskeys, where can I access those? Are they bundled in libaacs.dll or are they separate programs?

[qyot27]

aacs_info is the CLI tool that should come with libaacs, although I know many packagers probably don't bother (read: if you build libaacs, aacs_info gets built at the same time). aacskeys is a separate project, it's in the third stickied post at the top of this subforum.

The difference between what FindVUK and the script above do is that if the disc is not already in keydb.cfg, FindVUK gives you this:
0x$DISCID = Gatchaman Crowds 18 BD-1 | D | 2018-08-24 | U | 1-0x$UNITKEY ; MKBv65/FindVUK 1.35
where $DISCID and $UNITKEY are those actual values. It adds this directly into keydb.cfg. This works with any disc DVDFab works with (including those that cannot have their keys generated by aacskeys or libaacs because the MKB revision is too high).

The script gives you this (in *.keydb_forinsert.txt):
0x$DISCID = Gatchaman Crowds 18 BD-1 | V | 0x$VUK | M | 0x$MEDIAKEY | I | 0x$VOLUMEID ; MKBv65
It does not add it into keydb.cfg (but it does generate files in aacs/vuk/ like VLC does). Copy it over manually. This option only works with discs that libaacs and aacskeys work with. If your host certificate gets revoked, you have to rely on FindVUK if the keys aren't in keydb.cfg.

Merging the two is what I was describing earlier.

[ZampNoxis]

Hmm...I've looked around the different forum posts and it looks like any download link for aacs_info or aacskeys have been dead for some time. I'd build libaacs and just grab aacs_info, but I can't find any build instructions. I'll look into getting a DVDfab product and using FindVUK with it to get the formatted entry for keydb.cfg.

EDIT: I downloaded the evaluation version of DVDfab PassKey for Blu-ray and FindVUK is grabbing and uploading the data without a hitch!

[s3phy]

Hi,

I used FindVUK a few years ago (2017) and it worked great. Trying to use it again these days and it can't seem to find DVDfab. Here's what I'm getting:

-----------------------------------------------------------
00:51:35 - ----------- FindVUK 1.35 -----------
-----------------------------------------------------------
To close FindVUK simply press the ESC key
-----------------------------------------------------------
00:51:35 - SettingsFile: >C:\Users\s3phy\Downloads\FindVUK_1.35\config\FindVUK.ini<
00:51:35 - Update enabled - check for update
00:51:35 - Open Main-KEYDB file: >C:\Users\s3phy\AppData\Roaming\aacs\KEYDB.cfg<
00:51:41 - Open Backup-KEYDB file: >C:\Users\s3phy\Downloads\FindVUK_1.35\VUKbackup\KEYDB.cfg<
00:51:51 - ERROR! Cannot find (supported) DVDfab Passkey, DVDfab Mediaplayer or DVDfab!
00:51:51 - No supported DVDfab application discovered!
00:51:51 - Couldn't get settings for DVDfab applications - end now

Please press ENTER or ESC to exit

FindVUK logs:

2020-07-03 00:51:35 # 0 # [I] main / (legacy) / #############################################################################
2020-07-03 00:51:35 # 2 # [I] main / (legacy) / ----------- FindVUK 1.35 -----------
2020-07-03 00:51:35 # 3 # [I] main / (legacy) / Operating System: Windows 10
2020-07-03 00:51:35 # 5 # [I] main / Settings_GetFilename(legacy) / SettingsFile: >C:\Users\s3phy\Downloads\FindVUK_1.35\config\FindVUK.ini<
2020-07-03 00:51:35 # 17 # [I] main / (legacy) / Update enabled - check for update
2020-07-03 00:51:35 # 175 # [I] update / UPD_CheckUpdateAndDownload / Update - ReleaseOnline >1.35< CurrentRelease >1.35< Hash >743EDECE8F5E3762307056A89E5F6B8DD20D4E88<
2020-07-03 00:51:35 # 177 # [I] update / UPD_CheckUpdateAndDownload / No update required
2020-07-03 00:51:35 # 177 # [I] main / ConsoleBufferSize(legacy) / Current BufferSize 120 x 9001 - ScreenSize 120 x 30
2020-07-03 00:51:35 # 177 # [I] main / ConsoleBufferSize(legacy) / Requested BufferSize 120 x 300 - ScreenSize 120 x 50
2020-07-03 00:51:35 # 177 # [I] main / ConsoleBufferSize(legacy) / Max. ScreenSize 240 x 71
2020-07-03 00:51:35 # 177 # [I] main / ConsoleBufferSize(legacy) / Final New Values - BufferSize 120 x 9001 - ScreenSize 120 x 50 - Resize >1<
2020-07-03 00:51:35 # 177 # [I] main / ConsoleBufferSize(legacy) / M1 - New BufferSize 120 x 9001
2020-07-03 00:51:35 # 177 # [I] main / ConsoleBufferSize(legacy) / Mx2 - New ScreenSize 120 x 50
2020-07-03 00:51:35 # 191 # [I] main / (legacy) / Open Main-KEYDB file: >C:\Users\s3phy\AppData\Roaming\aacs\KEYDB.cfg<
2020-07-03 00:51:35 # 191 # [I] bluray_keydb / BRKDB_OpenFile / KeyDB file >C:\Users\s3phy\AppData\Roaming\aacs\KEYDB.cfg< opened!
2020-07-03 00:51:51 # 16679 # [I] main / (legacy) / Open Backup-KEYDB file: >C:\Users\s3phy\Downloads\FindVUK_1.35\VUKbackup\KEYDB.cfg<
2020-07-03 00:51:51 # 16679 # [I] bluray_keydb / BRKDB_OpenFile / KeyDB file >C:\Users\s3phy\Downloads\FindVUK_1.35\VUKbackup\KEYDB.cfg< opened!
2020-07-03 00:51:51 # 16679 # [I] bluray_keydb / BRKDB_OpenFile / INFO! Empty file! >C:\Users\s3phy\Downloads\FindVUK_1.35\VUKbackup\KEYDB.cfg<
2020-07-03 00:51:51 # 16680 # [I] main / Settings_ReadDVDfabSettings(legacy) / Information! No Passkey detected!
2020-07-03 00:51:51 # 16681 # [I] main / Settings_ReadDVDfabSettings(legacy) / Information! No MediaPlayer detected!
2020-07-03 00:51:51 # 16681 # [I] main / Settings_ReadDVDfabSettings(legacy) / Information! No DVDfab detected!
2020-07-03 00:51:51 # 16682 # [I] main / Settings_ReadDVDfabSettings(legacy) / ERROR! Cannot find (supported) DVDfab Passkey, DVDfab Mediaplayer or DVDfab!
2020-07-03 00:51:51 # 16682 # [I] main / FVMAIN_Mode_FindVUK_GetSettings(legacy) / No supported DVDfab application discovered!
2020-07-03 00:51:51 # 16682 # [I] main / (legacy) / Couldn't get settings for DVDfab applications - end now
2020-07-03 00:52:16 # 40952 # [I] main / FindVUK_SaveWindowPos(legacy) / Current position identical to last position - no need to save it

DVDfab (v11.0.8.0) is installed in "C:\Program Files\DVDFab 11". Its logs are in "C:\Users\s3phy\Documents\DVDFab11\Log".
My Windows is in French, if that changes anything.

[candela]

Hi,

I used FindVUK a few years ago (2017) and it worked great. Trying to use it again these days and it can't seem to find DVDfab. Here's what I'm getting:


did you install it over the old version so it's using the old ini file? try deleting the ini or a new directory, or edit the settings in the ini

[nalor]

Hi,

I used FindVUK a few years ago (2017) and it worked great. Trying to use it again these days and it can't seem to find DVDfab.

DVDfab (v11.0.8.0) is installed in "C:\Program Files\DVDFab 11". Its logs are in "C:\Users\s3phy\Documents\DVDFab11\Log".
My Windows is in French, if that changes anything.

FindVUK tries to find dvdfab in 2 steps:
1st it reads the entry from the inifile: section 'DVDfab' entry 'MainFile' - in case something is defined here it is always the most important source. So to solve your problem simply insert "C:\Program Files\DVDFab 11\DVDFab.exe" as 'mainfile' and it should work.

In case you want to dig a little bit deeper: in case this entry is not set FindVUK tries to get this filename from the registry.

check if entry 'HKEY_CURRENT_USER\Software\DVDFab' is available
read command from HKEY_CLASSES_ROOT\DVDFab 11\Shell\Open\Command 'default'


So you can check if both keys are available in your registry and if they are please tell me the exact value of the 2nd entry - maybe there's something specific on a french windows that I have to take into account.

[Aperson]

Hi,

I haven't tried this since QEMU support got merged, but it still doesn't seem to be working out of the box for me as of 1.35. Same drive details as posted here: https://forum.doom9.org/showpost.php?p=1862608&postcount=386

It would appear your "IsDriveQemu" function (or whatever it is that takes "QEMU" as an argument) is trying to compare "QEMU" to a null string, sees the string is null, and returns false. For now I've patched FindVUK.exe to believe that the "IsDriveQemu" function returned true, and it seems to be working fine.

[Dark Morford]

First time using FindVUK, trying to play a disc that came out earlier this year. I'm on Windows 10, and the aacs_info program indicates my drive has MKB v76.

FindVUK couldn't locate my installation of DVDFab 12 at first, so I had to manually put the executable and log locations into FindVUK.ini. Once I did that, I was able to get as far as finding the encrypted unit key, but the program is failing on the next step. Full FindVUK log is attached, but here's (I think) the relevant part; the memory dump is over 600 MB but if there's a specific portion that would be useful I can chop out part of it.

2020-10-10 14:29:30 # 57241 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >480< Content >2020.10.10-14:29:30: MD5 BBC21117B2D5D75190289BBE21C6B2B5 <
2020-10-10 14:29:30 # 57241 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >481< Content >2020.10.10-14:29:30: got vuk<
2020-10-10 14:29:30 # 57241 # [I] main / DVDfab_WatchLog_Standard(legacy) / DVDfab got VUK - create memdump now!
2020-10-10 14:29:30 # 57344 # [I] main / DumpProcessToFile(legacy) / DUMP >>>
2020-10-10 14:29:30 # 57344 # [I] main / DumpProcessToFile(legacy) / DUMP >>> ProcDump v10.0 - Sysinternals process dump utility
2020-10-10 14:29:30 # 57344 # [I] main / DumpProcessToFile(legacy) / DUMP >>> Copyright (C) 2009-2020 Mark Russinovich and Andrew Richards
2020-10-10 14:29:30 # 57344 # [I] main / DumpProcessToFile(legacy) / DUMP >>> Sysinternals - www.sysinternals.com
2020-10-10 14:29:30 # 57344 # [I] main / DumpProcessToFile(legacy) / DUMP >>>
2020-10-10 14:29:30 # 57344 # [I] main / DumpProcessToFile(legacy) / DUMP >>> [14:29:30] Dump 1 initiated: C:\Sandbox\FindVUK_1.35\dump\3DE26D88523ADD6B69B53AD42A228F8677663ADE_BRMM_10266BD1.dmp
2020-10-10 14:29:30 # 57445 # [I] main / DumpProcessToFile(legacy) / DUMP >>> [14:29:30] Dump 1 writing: Estimated dump file size is 654 MB.
2020-10-10 14:29:31 # 57950 # [I] main / DumpProcessToFile(legacy) / DUMP >>> [14:29:31] Dump 1 complete: 654 MB written in 0.6 seconds
2020-10-10 14:29:31 # 58151 # [I] main / DumpProcessToFile(legacy) / DUMP >>> [14:29:31] Dump count reached.
2020-10-10 14:29:31 # 58151 # [I] main / DumpProcessToFile(legacy) / DUMP >>>
2020-10-10 14:29:31 # 58151 # [I] main / DumpProcessToFile(legacy) / Dump successful! >1<
2020-10-10 14:29:31 # 58151 # [I] main / DumpProcessToFile(legacy) / DumpProcessToFile - Program >C:\Sandbox\FindVUK_1.35\tool\procdump64.exe< Parameter > -ma -o "DVDFab64.exe" "C:\Sandbox\FindVUK_1.35\dump\3DE26D88523ADD6B69B53AD42A228F8677663ADE_BRMM_10266BD1.dmp"<
2020-10-10 14:29:31 # 58151 # [I] main / DVDfab_DumpFile(legacy) / MemDump successfully finished!
2020-10-10 14:29:31 # 58151 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >482< Content >2020.10.10-14:29:30: drive info: BD-RE WH16NS40 | 1.03! <
2020-10-10 14:29:31 # 58151 # [I] main / DVDfab_WatchLog_Standard(legacy) / Cancel DVDfab decryption now!
2020-10-10 14:29:31 # 58159 # [I] main / (legacy) / Get basic AACS data
2020-10-10 14:29:31 # 58160 # [I] main / FVMAIN_Mode_FindVUK_WaitForAACS(legacy) / AACS folder on disc is reachable - ValidateVUK is possible
2020-10-10 14:29:32 # 58740 # [I] main / FVMAIN_Mode_FindVUK_GetMetaInfo_AACS(legacy) / Got DiscID from disc >3DE26D88523ADD6B69B53AD42A228F8677663ADE<
2020-10-10 14:29:32 # 58741 # [I] main / FVMAIN_Mode_FindVUK_GetMetaInfo_AACS(legacy) / Got DateDiscId from disc >2020-06-15<
2020-10-10 14:29:32 # 59047 # [I] main / FVMAIN_Mode_FindVUK_GetMetaInfo_AACS(legacy) / Get encrypted UnitKeys
2020-10-10 14:29:32 # 59047 # [I] main / FVMAIN_Mode_FindVUK_GetMetaInfo_AACS(legacy) / UnitKey-Count: 1
2020-10-10 14:29:32 # 59047 # [I] main / FVMAIN_Mode_FindVUK_GetMetaInfo_AACS(legacy) / UnitKeys ENC : >1< Key >4F609DAB1C455833F2208BA472B0F0D6<
2020-10-10 14:29:32 # 59048 # [I] main / (legacy) / VolumeName >BRMM_10266BD1<
2020-10-10 14:29:32 # 59048 # [I] main / (legacy) / DiscId >3DE26D88523ADD6B69B53AD42A228F8677663ADE< (2020-06-15)
2020-10-10 14:29:32 # 59048 # [I] main / (legacy) / DiscType >BD<
2020-10-10 14:29:32 # 59048 # [I] main / (legacy) / MKB Revision >76<
2020-10-10 14:29:32 # 59048 # [I] main / (legacy) / BusEncEnabl. >0<
2020-10-10 14:29:32 # 59049 # [I] main / (legacy) / UnitKeyCount >1<
2020-10-10 14:29:32 # 59049 # [I] main / (legacy) / >>> UnitKeyENC (1) >4F609DAB1C455833F2208BA472B0F0D6<
2020-10-10 14:29:32 # 59052 # [I] main / (legacy) / Analyze dump
2020-10-10 14:29:32 # 59053 # [I] main / DVDfab_AnalyzeDump_2018(legacy) / Start to analyze '2018' MemDump now!
2020-10-10 14:29:32 # 59053 # [I] main / DVDfab_GetUnitKeysFromDump(legacy) / DVDfab_GetUnitKeysFromDump - File >C:\Sandbox\FindVUK_1.35\dump\3DE26D88523ADD6B69B53AD42A228F8677663ADE_BRMM_10266BD1.dmp< DiscID >3DE26D88523ADD6B69B53AD42A228F8677663ADE< UnitKeyCnt >1<
2020-10-10 14:29:32 # 59172 # [I] main / DVDfab_Dump_GetDraftUnitKeys(legacy) / StartAddress of last UnitKey >2184FCA<
2020-10-10 14:29:33 # 60474 # [I] main / DVDfab_GetUnitKeysFromDump(legacy) / ERROR! Couldn't find real unit keys in json from file >C:\Sandbox\FindVUK_1.35\dump\3DE26D88523ADD6B69B53AD42A228F8677663ADE_BRMM_10266BD1.dmp<
2020-10-10 14:29:33 # 60474 # [I] main / DVDfab_AnalyzeDump_2018(legacy) / Error analyzing memory dump - please report in the doom9 forum!
2020-10-10 14:29:33 # 60475 # [I] main / (legacy) / ERROR! Analyze 2018 failed!
2020-10-10 14:29:33 # 60481 # [I] main / (legacy) / CloseAtTheEnd is active, close DVDfab now
2020-10-10 14:29:33 # 60487 # [I] main / DVDfab_CloseApplication(legacy) / There are >1< DVDfab processes running
2020-10-10 14:29:44 # 71117 # [I] main / DVDfab_CloseApplication(legacy) / Friendly closing of C:\Program Files\DVDFab\DVDFab 12\DVDFab64.exe< didn't succeed - kill it unfriendly now

[candela]

First time using FindVUK, trying to play a disc that came out earlier this year. I'm on Windows 10, and the aacs_info program indicates my drive has MKB v76.

FindVUK couldn't locate my installation of DVDFab 12 at first, so I had to manually put the executable and log locations into FindVUK.ini. Once I did that, I was able to get as far as finding the encrypted unit key, but the program is failing on the next step. Full FindVUK log is attached, but here's (I think) the relevant part; the memory dump is over 600 MB but if there's a specific portion that would be useful I can chop out part of it.


It's possible DVDFab has made changes in v12 that stops FindVUK from working. i suggest to try with version 11

[Dark Morford]

I'll give it a shot, but according to the changelog in the first post of this thread, support for DVDFab 12 was added in FindVUK 1.30; I'm using v1.35. (Though the log file warns that DVDFab 12.0 is "untested," which seems a bit contradictory to me...)

[nalor]

I'll give it a shot, but according to the changelog in the first post of this thread, support for DVDFab 12 was added in FindVUK 1.30; I'm using v1.35. (Though the log file warns that DVDFab 12.0 is "untested," which seems a bit contradictory to me...)I noticed that the official dvdfab q2 changed the position of the logfile and it's config file a little bit.
Will release a new findvuk today to handle this.
But when specifying both mainfile and logfile correctly in the ini file, it's already working with the current findvuk for me.

Gesendet von meinem H8324 mit Tapatalk

[nalor]

Released FindVUK 1.37 - it should properly find and use DVDfab 12.

[nalor]

First time using FindVUK, trying to play a disc that came out earlier this year. I'm on Windows 10, and the aacs_info program indicates my drive has MKB v76.

FindVUK couldn't locate my installation of DVDFab 12 at first, so I had to manually put the executable and log locations into FindVUK.ini. Once I did that, I was able to get as far as finding the encrypted unit key, but the program is failing on the next step. Full FindVUK log is attached, but here's (I think) the relevant part; the memory dump is over 600 MB but if there's a specific portion that would be useful I can chop out part of it.


Is it reproduceable ?

Basically it's a 2 step process that is executed here:


DVDfab_Dump_GetDraftUnitKeys - search for partial unit keys in the dump -> this succeeded in your case and returned 1 unit-key
DVDfab_GetUnitKeysFromDump - try to find the missing parts of the 'partial unit keys' in the dump


In case it fails please first check if it's working the next time - and else upload the dump somewhere and send me the link.

[Dark Morford]

Updated to FindVUK 1.37 (and DVDFab 12.0.0.1) and it's working like a charm. Thanks!

Also, here's my drive info for inclusion in the database:
2020.10.13 08:23:51 - Please post the following information into the doom9 forum thread: http://forum.doom9.org/showthread.php?t=172914
+ VENDOR # PRODUCT-IDENTIF. # REV. # FIRMWARE CR. # INTERFACE # DRIVETYPE # BusEncryptionCapable # BindingNonceGeneration # VENDOR SPECIFIC # FEATURE DESCRIPTOR # COMMENT
| HL-DT-ST | BD-RE WH16NS40 | 1.03 | 211711211653 | Serial ATAPI | BLURAY/DVD/CD-WRITER | 1 | 1 | NM00600SIK9CH158462 | 01 0D 09 04 17 01 02 01 |

[Roof Tile]

Hey nalor, cool to see FindVUK get another update! However, I'm wondering about something. Since updating, I get these strange excel files in the "accs" folder in APPDATA. They have weird names like "KEYDB_Diff_BRKDB_20201015_051659" and "KEYDB_Diff1_20201015_051659". I assume it's some sort of log or check that the program does since it has things like "TITLE" and "MEDIAKEY" as column names, but I just wanted to ask about them since I don't really know what they are and if I should keep them or if I can simply delete them if I want (or if there is an option to make the program delete them automatically after it is done with them).

Also, since I'm making this post anyway, I noticed that the FindVUK.ini file has the version set to 1.35 ("IniVersion = 1.35" in the file itself). Is that normal or do I need to do some sort of full reinstall by getting rid of certain files or the like? Probably not an issue I would imagine, but just wanted to mention it just in case it's related in some way.

PS. If you need me to upload the files I can certainly do that with TinyUpload, just didn't know if that was necessary in this case.

[nalor]

Those files can be deleted, I missed to disable the creation before creating the release.
They include debug information about the synchronisation process. In the next release it wil be possible to enable them with a ini parameter.
The version in the ini file depends on the latest release with changes in the ini file, so in your case I haven't made changes since release 1.35
But it's a good idea to change this behaviour [emoji2]

Gesendet von meinem H8324 mit Tapatalk

[Roof Tile]

Thanks for the explanations! Good to know everything is working correctly, keep up the great work.

[nalor]

Released 1.38 - fixes the bug with the strange files ;)

[nuraman00]

The tool asked me to post this:

++++++++++

17:35:06 - --- PART 2 --- VALIDATE VUK/UNITKEYS ---
-------------------------------------------------------------------------------
17:35:06 - Drive is detected as 'REAL BLURAY' drive
17:35:06 - Drive is NOT in the KnownDrivesList!

17:35:06 - Please post the following information in the Doom9 forum to create a comprehensive list of drives:
17:35:06 - (you'll find this information + additional details also in the file >C:\Unzipped\FindVUK_1.38\PleasePostInDoom9Forum.txt<
17:35:06 - + VENDOR # PRODUCT-IDENTIF. # REV. # FIRMWARE CR. # INTERFACE # DRIVETYPE # BusEncryptionCapable # BindingNonceGeneration # VENDOR SPECIFIC # FEATURE DESCRIPTOR # COMMENT
17:35:06 - | ASUS | BW-16D1HT | 3.03 | 211801191558 | Serial ATAPI | BLURAY/DVD/CD-WRITER | 1 | 1 | W000000KEII6190829 | 01 0D 09 04 1F 01 02 01 |

17:35:07 - Added this entry to the list of known drives so the request to post the details of this drive will not be shown again

[nuraman00]

-------------------------------------------------------------------------------
17:38:08 - Validation successful! UnitKeys are valid!!
-------------------------------------------------------------------------------

17:38:08 - -------------------------------------------------------
17:38:08 - MetaTitle : Metallica- SM2
17:38:08 - VolumeName : Metallica - SM2
17:38:08 - DiscID : BA4590CA75E050E4760DBA62404EBCB9A6749235
17:38:08 - DateDiscID : 2020-02-10
17:38:08 - DiscType : BD
17:38:08 - VUK :
17:38:08 - MEDIAKEY :
17:38:08 - VOLUMEID :
17:38:08 - >>> UnitKeyDEC (1) >0A34A4EC251DA52D7273B2D8B398ABBF< (Valid)
17:38:08 - MKBrev : 72
17:38:08 - BusEncrEn : 0
17:38:08 - AACS : 1
17:38:08 - BD+ : 0
17:38:08 - -------------------------------------------------------


-------------------------------------------------------------------------------
17:38:08 - --- Write entry in main-keydb file ---
-------------------------------------------------------------------------------

17:38:08 - Keys in Keyfile: 108887 keys - KeyFile: C:\Users\nuram\AppData\Roaming\aacs\KEYDB.cfg
17:38:08 - KEYDB: no entry found for discid >BA4590CA75E050E4760DBA62404EBCB9A6749235< ==>> write new entry in keydb-file

17:38:09 - Added line with VUK/UnitKeys to file >C:\Users\nuram\AppData\Roaming\aacs\KEYDB.cfg<

17:38:09 - -------------------------------------------------------
17:38:09 - --- Write entry in backup-keydb file ---
17:38:09 - -------------------------------------------------------
17:38:09 - KEYDB: file >C:\Unzipped\FindVUK_1.38\VUKbackup\KEYDB.cfg< does not exist ==>> write new entry in keydb-file

17:38:09 - Added line with VUK/UnitKeys to backup-file >C:\Unzipped\FindVUK_1.38\VUKbackup\KEYDB.cfg<

17:38:09 - -------------------------------------------------------
17:38:09 - --- Upload MetaXML to OnlineDB file ---
17:38:09 - -------------------------------------------------------
Establishing connection
Establishing connection
HTTP-POST success
17:38:10 - Successfully posted to the OnlineDB! >
Preconditions fulfilled - process upload now
Detected BlurayMetaXML - DiscId >BA4590CA75E050E4760DBA62404EBCB9A6749235<
Upload written to database!
Upload successfully processed!
<
17:38:10 - Successful upload to OnlineDB
17:38:10 - Hash file not available - nothing to update
17:38:10 - Eject the disc now from drive >D:\<

[nuraman00]

Now the Blu Ray plays, but I'm getting this error:

This Blu-ray disc requires Java for menus support.Java was not found on your system.
The disc will be played without menus.

I have java installed here:

C:\Program Files\Java\jdk-12.0.1

[Emulgator]

You may try to uninstall Java from its preferred location and reinstall Java in an unprotected folder.
Works nicely here:
C:\_PROG\Java\

[DanTheMann15]

Now the Blu Ray plays, but I'm getting this error:

This Blu-ray disc requires Java for menus support.Java was not found on your system.
The disc will be played without menus.

I have java installed here:

C:\Program Files\Java\jdk-12.0.1

You may try to uninstall Jave from its preferred location and reinstall Java in an unprotected folder.
Works nicely here:
C:\_PROG\Java\

That's not really the solution, you need to set your JAVA_HOME Environment variable to your java install path
which as you said, appears to be "C:\Program Files\Java\jdk-12.0.1".

Before i begin, you should really consider getting OpenJDK 11 (LTS) (https://adoptopenjdk.net/releases.html), and downloading just the JRE.
Java 12 is obsolete now and newer java versions add changes that might break libbluray.

and most importantly, you should update your installation of VLC (https://www.videolan.org/vlc/index.html) to the latest version.

you can set your JAVA_HOME variable by:

1. Right-click the My Computer icon on your desktop and select Properties.
2. Click the Advanced tab, then click the Environment Variables button.
3. Under System Variables, click New.
4. Enter the variable name as JAVA_HOME.
5. Enter the variable value as the installation path of Java.
6. Click "OK" and then click "Apply Changes"

after that i recommend restarting the PC (you don't have to though), and you should be good to go! ;)

[haruo]

Hey there! Many thanks for this tool, it helped me very much :D

But I'm getting a VUKNOTVAL! error, can you help me to make the movie run?


2020-10-29 18:24:03 # 0 # [I] main / (legacy) / #############################################################################
2020-10-29 18:24:03 # 2 # [I] main / (legacy) / ----------- FindVUK 1.38 -----------
2020-10-29 18:24:03 # 2 # [I] main / (legacy) / Operating System: Windows 10
2020-10-29 18:24:03 # 3 # [I] main / Settings_GetFilename(legacy) / SettingsFile: >C:\Users\haruo_000\Desktop\FindVUK_1.38\config\FindVUK.ini<
2020-10-29 18:24:03 # 11 # [I] main / (legacy) / Update enabled - check for update
2020-10-29 18:24:04 # 746 # [I] update / UPD_CheckUpdateAndDownload / Update - ReleaseOnline >1.38< CurrentRelease >1.38< Hash >24011EA98216F890749E1A3BD767F90ABC4C8432<
2020-10-29 18:24:04 # 746 # [I] update / UPD_CheckUpdateAndDownload / No update required
2020-10-29 18:24:04 # 748 # [I] main / GenericCallback(legacy) / No update required
2020-10-29 18:24:04 # 748 # [I] main / ConsoleBufferSize(legacy) / Current BufferSize 80 x 300 - ScreenSize 80 x 25
2020-10-29 18:24:04 # 748 # [I] main / ConsoleBufferSize(legacy) / Requested BufferSize 120 x 300 - ScreenSize 120 x 50
2020-10-29 18:24:04 # 748 # [I] main / ConsoleBufferSize(legacy) / Max. ScreenSize 227 x 62
2020-10-29 18:24:04 # 748 # [I] main / ConsoleBufferSize(legacy) / Final New Values - BufferSize 120 x 300 - ScreenSize 120 x 50 - Resize >1<
2020-10-29 18:24:04 # 749 # [I] main / ConsoleBufferSize(legacy) / M1 - New BufferSize 120 x 300
2020-10-29 18:24:04 # 751 # [I] main / ConsoleBufferSize(legacy) / Mx2 - New ScreenSize 120 x 50
2020-10-29 18:24:04 # 766 # [I] main / (legacy) / Open Main-KEYDB file: >C:\Users\haruo_000\AppData\Roaming\aacs\KEYDB.cfg<
2020-10-29 18:24:04 # 767 # [I] bluray_keydb / BRKDB_OpenFile / KeyDB file >C:\Users\haruo_000\AppData\Roaming\aacs\KEYDB.cfg< opened!
2020-10-29 18:24:04 # 773 # [I] main / (legacy) / Open Backup-KEYDB file: >C:\Users\haruo_000\Desktop\FindVUK_1.38\VUKbackup\KEYDB.cfg<
2020-10-29 18:24:04 # 773 # [I] bluray_keydb / BRKDB_OpenFile / KeyDB file >C:\Users\haruo_000\Desktop\FindVUK_1.38\VUKbackup\KEYDB.cfg< opened!
2020-10-29 18:24:04 # 774 # [I] main / Settings_ReadDVDfabSettings(legacy) / Information! Passkey detected >D:\Programas\DVDFab\Passkey\DVDFabPasskey.exe<
2020-10-29 18:24:04 # 775 # [I] main / Settings_ReadDVDfabSettings(legacy) / Tested Passkey Version >9.4.0.2< found
2020-10-29 18:24:04 # 776 # [I] main / Settings_ReadDVDfabSettings(legacy) / >>> everything should work as expected!
2020-10-29 18:24:04 # 777 # [I] main / Settings_ReadDVDfabSettings(legacy) / Information! No MediaPlayer detected!
2020-10-29 18:24:04 # 778 # [I] main / Settings_ReadDVDfabSettings(legacy) / Information! No DVDfab detected!
2020-10-29 18:24:04 # 779 # [I] main / FVMAIN_Mode_FindVUK_GetSettings(legacy) / Passkey is preferred and available!
2020-10-29 18:24:04 # 779 # [I] main / FVMAIN_Mode_FindVUK_GetSettings(legacy) / Passkey-MainFile: >D:\Programas\DVDFab\Passkey\DVDFabPasskey.exe<
2020-10-29 18:24:04 # 779 # [I] main / FVMAIN_Mode_FindVUK_GetSettings(legacy) / Passkey-LogFile: >C:\Users\haruo_000\Documents\\DVDFab\Passkey\Log\passkey_internal.log<
2020-10-29 18:24:04 # 780 # [I] main / FVMAIN_Mode_FindVUK_GetSettings(legacy) / KEYDB-Path: >C:\Users\haruo_000\AppData\Roaming\aacs\<
2020-10-29 18:24:04 # 780 # [I] main / FVMAIN_Mode_FindVUK_GetSettings(legacy) / KEYDB-Backup-Path: >C:\Users\haruo_000\Desktop\FindVUK_1.38\VUKbackup\<
2020-10-29 18:24:04 # 781 # [I] main / FVMAIN_Mode_FindVUK_GetSettings(legacy) / ProcDumpFile: >C:\Users\haruo_000\Desktop\FindVUK_1.38\tool\procdump64.exe<
2020-10-29 18:24:04 # 781 # [I] main / FVMAIN_Mode_FindVUK_GetDump(legacy) / --- PART 1 --- GET DUMP ---
2020-10-29 18:24:04 # 790 # [I] main / FVMAIN_Mode_FindVUK_GetDump(legacy) / No running application process discovered
2020-10-29 18:24:04 # 791 # [I] main / FVMAIN_Mode_FindVUK_GetDump(legacy) / >> Start it now >D:\Programas\DVDFab\Passkey\DVDFabPasskey.exe<
2020-10-29 18:24:12 # 8594 # [I] main / DVDfab_WatchLog_Standard(legacy) / Filechange detected! OldLineCnt >189< NewLineCnt >193<
2020-10-29 18:24:12 # 8594 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >189< Content ><
2020-10-29 18:24:12 # 8594 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >190< Content ><
2020-10-29 18:24:12 # 8596 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >191< Content >DVDFabPasskey 9.4.0.2 (2020/10/29 18:24:12)<
2020-10-29 18:24:12 # 8596 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >192< Content ><
2020-10-29 18:24:12 # 8596 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >193< Content >(empty)<
2020-10-29 18:24:22 # 18979 # [I] main / DVDfab_WatchLog_Standard(legacy) / Filechange detected! OldLineCnt >193< NewLineCnt >202<
2020-10-29 18:24:22 # 18979 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >193< Content >2020.10.29-18:24:22: Drive E add. <
2020-10-29 18:24:22 # 18979 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >194< Content >2020.10.29-18:24:22: got firmware HL-DT-ST BDDVDRW CT40N 1.00.<
2020-10-29 18:24:22 # 18979 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >195< Content >2020.10.29-18:24:22: Drive E media add. <
2020-10-29 18:24:22 # 18980 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >196< Content >2020.10.29-18:24:22: opened i/o type 1 <
2020-10-29 18:24:22 # 18980 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >197< Content >2020.10.29-18:24:22: opening drive E<
2020-10-29 18:24:22 # 18980 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >198< Content >2020.10.29-18:24:22: opened i/o<
2020-10-29 18:24:22 # 18980 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >199< Content >2020.10.29-18:24:22: currentProfile: 64<
2020-10-29 18:24:22 # 18980 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >200< Content >2020.10.29-18:24:22: got media type 15<
2020-10-29 18:24:22 # 18980 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >201< Content >2020.10.29-18:24:22: got max lba 23542271<
2020-10-29 18:24:22 # 18980 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >202< Content >(empty)<
2020-10-29 18:24:23 # 19987 # [I] main / DVDfab_WatchLog_Standard(legacy) / Filechange detected! OldLineCnt >202< NewLineCnt >206<
2020-10-29 18:24:23 # 19988 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >202< Content >2020.10.29-18:24:23: got disc type 20<
2020-10-29 18:24:23 # 19988 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >203< Content >2020.10.29-18:24:23: type Blu-ray BDMV<
2020-10-29 18:24:23 # 19989 # [I] main / DVDfab_WatchLog_Standard(legacy) / Drive opened
2020-10-29 18:24:23 # 19990 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >204< Content >2020.10.29-18:24:23: volume label ALITA_BATTLE_ANGEL<
2020-10-29 18:24:23 # 19990 # [I] main / DVDfab_WatchLog_Standard(legacy) / Volume Label detected >ALITA_BATTLE_ANGEL<
2020-10-29 18:24:23 # 19990 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >205< Content >2020.10.29-18:24:23: Is Encryption 1 <
2020-10-29 18:24:23 # 19990 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >206< Content >(empty)<
2020-10-29 18:24:34 # 30672 # [I] main / DVDfab_WatchLog_Standard(legacy) / Filechange detected! OldLineCnt >206< NewLineCnt >212<
2020-10-29 18:24:34 # 30672 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >206< Content >2020.10.29-18:24:34: bd set region ?<
2020-10-29 18:24:34 # 30672 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >207< Content >2020.10.29-18:24:34: opened i/o type 1 <
2020-10-29 18:24:34 # 30672 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >208< Content >2020.10.29-18:24:34: opening drive E<
2020-10-29 18:24:34 # 30672 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >209< Content >2020.10.29-18:24:34: opened i/o<
2020-10-29 18:24:34 # 30672 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >210< Content >2020.10.29-18:24:34: currentProfile: 64<
2020-10-29 18:24:34 # 30673 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >211< Content >2020.10.29-18:24:34: got max lba 23542271<
2020-10-29 18:24:34 # 30673 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >212< Content >(empty)<
2020-10-29 18:24:35 # 31682 # [I] main / DVDfab_WatchLog_Standard(legacy) / Filechange detected! OldLineCnt >212< NewLineCnt >215<
2020-10-29 18:24:35 # 31682 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >212< Content >2020.10.29-18:24:35: got disc type 20<
2020-10-29 18:24:35 # 31682 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >213< Content >2020.10.29-18:24:35: Is Encryption 1 <
2020-10-29 18:24:35 # 31683 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >214< Content >2020.10.29-18:24:35: internal path E:/BDMV/<
2020-10-29 18:24:35 # 31683 # [I] main / DVDfab_WatchLog_Standard(legacy) / DriveLetter detected >E<
2020-10-29 18:24:35 # 31683 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >215< Content >(empty)<
2020-10-29 18:24:36 # 32691 # [I] main / DVDfab_WatchLog_Standard(legacy) / Filechange detected! OldLineCnt >215< NewLineCnt >217<
2020-10-29 18:24:36 # 32691 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >215< Content >2020.10.29-18:24:36: aacs 1 bd+ 0<
2020-10-29 18:24:36 # 32692 # [I] main / DVDfab_WatchLog_Standard(legacy) / Detected CopyProtections AACS >1< BD+ >0<
2020-10-29 18:24:36 # 32693 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >216< Content >2020.10.29-18:24:36: read index.bdmv begin<
2020-10-29 18:24:36 # 32693 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >217< Content >(empty)<
2020-10-29 18:24:36 # 33096 # [I] main / DVDfab_WatchLog_Standard(legacy) / Filechange detected! OldLineCnt >217< NewLineCnt >218<
2020-10-29 18:24:36 # 33096 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >217< Content >2020.10.29-18:24:36: got bdmv<
2020-10-29 18:24:36 # 33096 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >218< Content >(empty)<
2020-10-29 18:24:36 # 33298 # [I] main / DVDfab_WatchLog_Standard(legacy) / Filechange detected! OldLineCnt >218< NewLineCnt >219<
2020-10-29 18:24:36 # 33299 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >218< Content >2020.10.29-18:24:36: blu-ray EB0720555ACDBDC8D429C94BF7D644138AEA97D7<
2020-10-29 18:24:36 # 33299 # [I] main / DVDfab_WatchLog_Standard(legacy) / DiscID found >EB0720555ACDBDC8D429C94BF7D644138AEA97D7<
2020-10-29 18:24:36 # 33300 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >219< Content >(empty)<
2020-10-29 18:24:37 # 33905 # [I] main / DVDfab_WatchLog_Standard(legacy) / Filechange detected! OldLineCnt >219< NewLineCnt >221<
2020-10-29 18:24:37 # 33906 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >219< Content >2020.10.29-18:24:37: cert BEE=0x80 same<
2020-10-29 18:24:37 # 33906 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >220< Content >2020.10.29-18:24:37: server id 0 <
2020-10-29 18:24:37 # 33906 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >221< Content >(empty)<
2020-10-29 18:24:39 # 35822 # [I] main / DVDfab_WatchLog_Standard(legacy) / Filechange detected! OldLineCnt >221< NewLineCnt >224<
2020-10-29 18:24:39 # 35823 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >221< Content >2020.10.29-18:24:39: MD5 BA6E031D728B211425218175FC0426C7 <
2020-10-29 18:24:39 # 35823 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >222< Content >2020.10.29-18:24:39: got vuk<
2020-10-29 18:24:39 # 35824 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >223< Content >2020.10.29-18:24:39: drive info: BDDVDRW CT40N | 1.00! <
2020-10-29 18:24:39 # 35824 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >224< Content >(empty)<
2020-10-29 18:24:39 # 35926 # [I] main / DVDfab_WatchLog_Standard(legacy) / Filechange detected! OldLineCnt >224< NewLineCnt >225<
2020-10-29 18:24:39 # 35926 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >224< Content >2020.10.29-18:24:39: got agid 0<
2020-10-29 18:24:39 # 35926 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >225< Content >(empty)<
2020-10-29 18:24:39 # 36029 # [I] main / DVDfab_WatchLog_Standard(legacy) / Filechange detected! OldLineCnt >225< NewLineCnt >226<
2020-10-29 18:24:39 # 36029 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >225< Content >2020.10.29-18:24:39: sent host cert chal<
2020-10-29 18:24:39 # 36029 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >226< Content >(empty)<
2020-10-29 18:24:39 # 36131 # [I] main / DVDfab_WatchLog_Standard(legacy) / Filechange detected! OldLineCnt >226< NewLineCnt >227<
2020-10-29 18:24:39 # 36131 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >226< Content >2020.10.29-18:24:39: got drive cert chal<
2020-10-29 18:24:39 # 36131 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >227< Content >(empty)<
2020-10-29 18:24:39 # 36234 # [I] main / DVDfab_WatchLog_Standard(legacy) / Filechange detected! OldLineCnt >227< NewLineCnt >231<
2020-10-29 18:24:39 # 36235 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >227< Content >2020.10.29-18:24:39: BEC 1<
2020-10-29 18:24:39 # 36235 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >228< Content >2020.10.29-18:24:39: DRIVE_VENDOR 0x0074<
2020-10-29 18:24:39 # 36236 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >229< Content >2020.10.29-18:24:39: AACS bus encryption is enabled<
2020-10-29 18:24:39 # 36236 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >230< Content >2020.10.29-18:24:39: got drive key<
2020-10-29 18:24:39 # 36236 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >231< Content >(empty)<
2020-10-29 18:24:39 # 36338 # [I] main / DVDfab_WatchLog_Standard(legacy) / Filechange detected! OldLineCnt >231< NewLineCnt >234<
2020-10-29 18:24:39 # 36339 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >231< Content >2020.10.29-18:24:39: got host key signature<
2020-10-29 18:24:39 # 36339 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >232< Content >2020.10.29-18:24:39: verified drive signature<
2020-10-29 18:24:39 # 36340 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >233< Content >2020.10.29-18:24:39: verified host signature<
2020-10-29 18:24:39 # 36340 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >234< Content >(empty)<
2020-10-29 18:24:40 # 36442 # [I] main / DVDfab_WatchLog_Standard(legacy) / Filechange detected! OldLineCnt >234< NewLineCnt >238<
2020-10-29 18:24:40 # 36442 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >234< Content >2020.10.29-18:24:39: sent host signature and key point<
2020-10-29 18:24:40 # 36442 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >235< Content >2020.10.29-18:24:39: got bus key<
2020-10-29 18:24:40 # 36443 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >236< Content >2020.10.29-18:24:39: start got bus key! <
2020-10-29 18:24:40 # 36443 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >237< Content >2020.10.29-18:24:40: got data key!<
2020-10-29 18:24:40 # 36443 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >238< Content >(empty)<
2020-10-29 18:24:40 # 36746 # [I] main / DVDfab_WatchLog_Standard(legacy) / Filechange detected! OldLineCnt >238< NewLineCnt >241<
2020-10-29 18:24:40 # 36746 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >238< Content >2020.10.29-18:24:40: got unit key 1<
2020-10-29 18:24:40 # 36747 # [I] main / DVDfab_WatchLog_Standard(legacy) / Passkey got Unit Keys - create memdump now!

[haruo]

Hey there! Many thanks for this tool, it helped me very much :D

But I'm getting a VUKNOTVAL! error, can you help me to make the movie run?

[candela]

Hey there! Many thanks for this tool, it helped me very much :D

But I'm getting a VUKNOTVAL! error, can you help me to make the movie run?

It takes long time before the attachments get approved, upload elsewhere

VUKNOTVAL! probably indicates a disc that enables bus encryption (every UHD disc) so you need a unrevoked host cert to play it. Try these https://forum.doom9.org/showthread.php?p=1883655#post1883655

If you have inserted a disc >= MKBv72 in your drive you are out of luck at the moment

[DanTheMann15]

Hey there! Many thanks for this tool, it helped me very much :D

But I'm getting a VUKNOTVAL! error, can you help me to make the movie run?

right here: MKBv71 host certificate and processing keys up to MKBv68. https://forum.doom9.org/showthread.php?p=1888086

but like what candela said, if you've inserted a disc that's MKBv72 and newer, you are out of luck with BEE discs until the next host certificate shows up.

[haruo]

Thanks for the answers guys!

It takes long time before the attachments get approved, upload elsewhere

Uploaded here: https://justpaste.it/9kxe9

I don't think it has to do with MKB since both discs inserted return MKBv68 in KEYDB.cfg

The disc that do not work returns: 0xEB0720555ACDBDC8D429C94BF7D644138AEA97D7 = ALITA_BATTLE_ANGEL (Alita: Battle Angel) | D | 2019-05-17 | U | 1-0x807053790039AB3C5168BE14FD730D16 ; MKBv68/BEE/VUKNOTVAL!/FindVUK 1.38


What I should do with those host certificate and processing keys? Copy and paste in KEYDB.cfg?

[mick0]

The disc that do not work returns: 0xEB0720555ACDBDC8D429C94BF7D644138AEA97D7 = ALITA_BATTLE_ANGEL (Alita: Battle Angel) | D | 2019-05-17 | U | 1-0x807053790039AB3C5168BE14FD730D16 ; MKBv68/BEE/VUKNOTVAL!/FindVUK 1.38

VUKNOTVAL is not an error, it just indicates that FindVUK was unable to verify that VUK/UK because 1) the disc uses bus encryption ("BEE" tag) and 2) your drive is bus encryption capable.

Valid host certificate is needed for fetching data keys from the drive for BEE discs (when libaacs cache doesn't have cached RDK for this drive/disc combination), otherwise playback won't work.

If you have inserted any MKB72+ disc in your drive, your drive have already self-updated and it's already too late as it won't accept any of those host certificates anymore. In this case you're out of luck until you have a new host certificate which isn't revoked.

What I should do with those host certificate and processing keys? Copy and paste in KEYDB.cfg?

Yes.

[haruo]

Great news
Pasting PK and HC in the keydb manage to work!

Thank you very much for the help guys! :D