Dump Submitted: MKB20_v77_28_Years_Later_63FC.tgz

[csbond2]

MKB20_v77_28_Years_Later_63FC.tgz
It was submitted to support. I'm not sure if that's where it was supposed to go or not but what I read that was my guess. And it has a different key from the other submission.

[BizzyB]

MKB20_v77_28_Years_Later_63FC.tgz
It was submitted to support. I'm not sure if that's where it was supposed to go or not but what I read that was my guess. And it has a different key from the other submission.

Did you submit to svq@makemkv.com?

[hanakuin]

I submitted MKB20_v77_28_Years_Later_13A6.tgz to svq@makemkv.com

[csbond2]

MKB20_v77_28_Years_Later_63FC.tgz
It was submitted to support. I'm not sure if that's where it was supposed to go or not but what I read that was my guess. And it has a different key from the other submission.

Did you submit to svq@makemkv.com?

Yes i sent it there.

[oatmeal769]

How do we check if it works, or has been validated (not sure the terminology)? I have the exact same dump.

[MartyMcNuts]

How do we check if it works, or has been validated (not sure the terminology)? I have the exact same dump.

For MakeMKV:

Simply try to rip the disc again. You may also notice in the log window when MakeMKV downloads the latest HK.

For KeyDB:

You can download the latest KeyDB file and search for you discID (SHA-1 of the Unit_Key_RO.inf file on the disc or in the dump). If a record exists and it contains the VUK (| V |) then you are good to go!

[oatmeal769]

Simply try to rip the disc again. You may also notice in the log window when MakeMKV downloads the latest HK.

This led me to realize there's a new update to the MakeMKV software. Downloaded, and good to go! THANKS!