Trying to convert the Transporter Series BD Season 2

[boe_d]

Hello,

I'm lost on what to do when a disc doesn't just convert. I'm running the latest Makemkv for windows 10. I just download it.

When I attempt to conver the disk, it says:
opening it,
downloading the latest HK to C:/temp
Saved AACS dump file as C:/temp/MKB_v61_Transporter_-_Staffel_2_-_Disc1_E482.tgz
The volume key is unknown for this disc - video can't be decrypted
Failed to open disc

I get the same issue for the second disk.

The are original legit disks bought on Amazon

I tried copying the files to the hard disk just in case - same error when opening from my hard drive.

I've also cleaned the disks and

[Grauhaar]

Please provide the full debug log.

To enable it go to: "Preferences -> General -> Log Debug Messages" and restart MakeMKV

[Woodstock]

When you post the log, make sure you include the part that lists the version of MakeMKV you're running - AACS v61 is rather old (66 is the latest), and there are probably other issues involved to get that error message.

[boe_d]

Thanks for spoon feeding me the instructions - it really makes it easy to follow - I appreciate it and your help!

Debug log started at Sun Nov 11 21:03:58 2018 , written by MakeMKV v1.14.1 win(x64-release)
Using 262272KB for read cache.
001005:0000 MakeMKV v1.14.1 win(x64-release) started
001004:0000 Debug logging enabled, log will be saved as C:\Users\boe/MakeMKV_log.txt
005042:0000 The program can't find any usable optical drives.
003006:0000 Opening files on harddrive at G:/temp/TRANSPORTER_02_D1
DEBUG: Code 2147483648 at q'(*`fMQ6kt8Paz::29397104
003332:0000 Saved AACS dump file as C:/temp/MKB_v61_Transporter_-_Staffel_2_-_Disc1_E482.tgz
003303:0000 The volume key is unknown for this disc - video can't be decrypted
001003:0020 DEBUG: Code 0 at w[oqc<L063>sMM^e:29396138
001003:0020 DEBUG: Code 0 at w[oqc<L063>sMM^e:213134377
005010:0000 Failed to open disc
Application exited at Sun Nov 11 21:07:49 2018

[Grauhaar]

Please open the Blu-ray and not your copied files from Harddrive

[boe_d]

Debug log started at Mon Nov 12 01:11:35 2018 , written by MakeMKV v1.14.1 win(x64-release)
Using 262272KB for read cache.
001005:0000 MakeMKV v1.14.1 win(x64-release) started
001004:0000 Debug logging enabled, log will be saved as C:\Users\boe/MakeMKV_log.txt
001003:0020 DEBUG: Code 3221225506 at D@ytnTd,%E%heCghB3$P:29394390
005042:0000 The program can't find any usable optical drives.
005041:0404 The folder "D:" appears to be a root folder on optical drive, however drive can't be accessed by the program. The operation will most likely fail.
003006:0000 Opening files on harddrive at D:
DEBUG: Code 2147483648 at q'(*`fMQ6kt8Paz::29397104
003332:0000 Saved AACS dump file as C:/temp/MKB_v61_Transporter_-_Staffel_2_-_Disc1_E482.tgz
003303:0000 The volume key is unknown for this disc - video can't be decrypted
001003:0020 DEBUG: Code 0 at w[oqc<L063>sMM^e:29396138
001003:0020 DEBUG: Code 0 at w[oqc<L063>sMM^e:213134377
005010:0000 Failed to open disc
Application exited at Mon Nov 12 01:11:58 2018

[Woodstock]

Two things going on here, I think.

#1 - did you start MakeMKV as an administrator? The inability to access D: directly is a problem with getting the key information.

#2 - the copy that was done to disk did not contain the information necessary to find the key. When MakeMKV makes a backup (encrypted or unencrypted), it stores information in a file that accompanies the backup. If it isn't there, the key cannot be found.... but there is a way to get it after the fact, if MakeMKV is allowed to access the original disk, using the same drive that the files on the hard drive were copied from. That means fixing #1, at least. This link may help: https://makemkv.com/forum/viewtopic.php ... att#p61115

[Grauhaar]

005042:0000 The program can't find any usable optical drives.
005041:0404 The folder "D:" appears to be a root folder on optical drive, however drive can't be accessed by the program. The operation will most likely fail.
003006:0000 Opening files on harddrive at D:

Could you please explain what you are doing? Any special other software running in the background that blocks the access? You are not opening the original Bu-ray to access the data on it. Looks like that you are still using a copy or whatever of it, which is not working due to missing important encryption data.

[boe_d]

Hello,

Yes, I've tried running it administrator.

MakeMKV doesn't seem to recognize these discs as discs - this is why I copied the files from the discs to the hard drive.

I'm not running any other disc decoding software.

It might be because this disc is german in origin and I'm in the US - not sure if I need to make my disc player region free or anything like that.

[Grauhaar]

MakeMKV doesn't seem to recognize these discs as discs - this is why I copied the files from the discs to the hard drive.

Windows must recognize the disc. If Windows has detected it, MakeMKV see's the disc. Your copy to harddisc is not working, because some important encryption thinks are not copied during a normal copy operation.

By the way, Blu-ray's have no region code, so this is not the problem.

[boe_d]

Thanks - I don' t know what you mean by recognizing the disc.

I was asked about this "the inability to access D: directly is a problem with getting the key information." I'm not sure what to say other than I can get to files on that disk.

[Woodstock]

Did Windows acknowledge the disk as an optical disk?

If Windows treats it as a hard drive (rather than an optical disk) some information necessary to decrypt the video is not available. That is why MakeMKV must be run as an administrator.

Now, if you are remotely accessing the Windows machine, OTHER security features kick in to make life difficult...

[boe_d]

Here is what windows sees


Thanks! That was the issue - when I used remote desktop - makemkv had an issue but when I used VNC, makemkv worked fine.

I appreciate your patience in walking me through the issue. I switched PCs and didn't have space for an optical drive in my new PC.

[Woodstock]

You can fix the permissions issue for RDP access in the Windows Local Security Policy, but VNC is probably a better solution in any case.