Error Message

[forceawakens]

I have a LG “UHD Friendly” drive.

I assume I tried a 4k title that MakeMKV didn’t have the key for and now anytime I put a Blu-ray or 4K title in my drive & try to open it with MakeMKV I get this error message:

Error: Scsi Error - ILLEGAL REQUEST COPY PROTECTION KEY - EXCHANGE FARILURE - KEY NOT ESTABLISHED - occurred while issuing SCSI command AD.....

Can’t read AACS VID from disc - most likely current AACS host certificate is revoked by your drive

After I got this message with the 4K disc I get it for any disc - Blu-ray or 4K I put in.

I’m new to MakeMKV so I’m not sure what caused this & if I will be able to use my drive any longer to make MKVs.

Can anyone tell me what caused this & if my drive is unusable now for making MKVs for 4k or Blu-rays.

Thanks for your help.

[Woodstock]

What version of MakeMKV are you using? Did you also get a message about a file being created for the AACS version, and to forward that to svq@makemkv.com? This is all in the information window (and debug log, if you have it enabled).

If your drive did receive and process a revocation table entry, then yes, your drive will refuse to let MakeMKV talk to it until a version that supersedes the AACS version revocation is released.

Check your MakeMKV directory (the one pointed to by Preferences->General) to see what MKB*.tgz files exist there. Files that start with "MKB_vNN" are for Bluray, "MKV20_vNN" are for UHD. The "NN" is the version of AACS found on the disk; version 1.12.2 of MakeMKV works with up to v65.

[forceawakens]

Make MKV Version 1.12.0

The Blu-ray I was trying to make a MKV of has AACS v31 AACS

The MakeMKV 1.12.0 has AACS version 61

I can’t remember which 4k UHD disc started the problem. Do I have to know that? I think it was Gladiator 4k.

I see several tgz files in my directory. There’s also a private_data.tar file there. And there are 3 dump files there.

I have another LG “UHD Friendly” drive & that one will allow me to make a MKV of the Blu-ray Disc. Again any Blu-ray I put in the drive gives me the error message.

How do I get the one that had the AACS revoked to be able to make MKVs again or is that drive bricked with MakeMKV? And how do I prevent that from happening again?

[Woodstock]

We're not 100% certain there was a revocation, just highly likely.

The number after the MKB_v or MKB20_v is the highest version MakeMKV has seen on your system. That is not necessarily the highest version that has been in the drive, though - the revocation process doesn't require that you actually try to read the disk with a program, just that the drive itself reads the disk. There is more information about that one the SVQ page, /svq/

Version 1.12.0 handles AACS to v64, 1.12.2 does v65. If you find a MKB_v65 file in your MakeMKV directory, then you need to update to version 1.12.2. I'd recommend it in any case, because 1.12.0 had a bug with working with UHD disks.

[forceawakens]

Thanks. I upgraded to 1.12.2 and it started working correctly again.

In the future if there is a title that the keys are not there for is there a possibility it could do a revocation of my drive again?

If so how do I stop that from happening?

Thanks for taking the time to help me understand this since I’m new to MakeMKV.

[Woodstock]

Revocations take place at the hardware level - just inserting a disk that contains a revocation entry for MakeMKV's "current" key (the one in use for the version you have) will make the drive refuse any Bluray actions by MakeMKV until a new key is in place.

Not all drives respect revocation keys, but most do. I've had it happen to me once - I got a new disk that revoked one of the drives. In that case, switching to a different drive was enough, but I usually won't let it get that far.

[xvf17]

MacOS 10.12.14
MakeMKV 1.12.2

I'm having the same problem. It's happening on every BluRay I try. The highest AAV version for which there is an MKB file is _v64_.

Thanks for any suggestions.

[Woodstock]

Do you have any Blurays that are newer than the one listing in the MKB file? MakeMKV will only create an MKB file if it reads the disk, but it doesn't take a program loading the disk for a drive to read the revocation table.

If you have a newer one, it would be best to try ripping that disk to get the MKB file created and sent to Mike.

Also, make sure that it's actually 1.12.2 that is running - it is possible for an install to "complete", but not actually replace the version, if the uninstall portion had a problem. The version number will show up in the INFO window when MakeMKV loads.

[xvf17]

I'm getting the version number from the "About" dialog, so I'm pretty sure I'm running the version I claim. I dug through some old log files and found a magic URL for the first failed disk. I pasted that into my browser; I presume that's what you meant by "sending it to Mike."

So now I must wait. Patiently.