AACS host certificate errors

Please post here for issues related to Blu-ray discs
Post Reply
SCoallier
Posts: 2
Joined: Wed Mar 13, 2013 10:24 pm

AACS host certificate errors

Post by SCoallier »

So (of course) I just paid for this software, and it's not working on some discs.

I have a Samsung SE-506 Blu-ray portable writer and I am running MakeMKV on a Mac using OSX 10.8.

So far two blu-ray discs, 2001 A Space Odyssey and Gone with the Wind are giving me an error saying that my drive has probably revoked my AACS host certificate. It has worked fine for a few other Blu-ray discs so far.

How can this be fixed? Any help would be much appreciated.
Woodstock
Posts: 10412
Joined: Sun Jul 24, 2011 11:21 pm

Re: AACS host certificate errors

Post by Woodstock »

What version of MakeMKV?

Version 1.7.8 and earlier (and 1.7.71 is earlier!) have AACS access information that was revoked by several recent BDs, including Total Recall. You have to use a newer version once you've tried ripping one of the "problem" disks, because of this. NO protected BD will work after loading one of these disks, until you update your copy of MakeMKV.

Also, it would be a good idea to enable debugging (instructions in the link below) all the time. When/if there is a problem, you will have a log file that can be used to figure out what is actually going on.
SCoallier
Posts: 2
Joined: Wed Mar 13, 2013 10:24 pm

Re: AACS host certificate errors

Post by SCoallier »

Thanks - I should have noted, though, that I am using version 1.80.

There isn't a newer one yet. I will take a look at turning debugging on - is that a step beyond the log I already see?

Also: I did successfully rip Sex and the City last night (after I ripped Julie and Julia, which is apparently the Blu-Ray that set the AACS version to 16).
Woodstock
Posts: 10412
Joined: Sun Jul 24, 2011 11:21 pm

Re: AACS host certificate errors

Post by Woodstock »

AACS version 16 is pretty old... even my drives are at 23, and I think it was v37 that triggered the problems people were having.

Turning on debugging and posting the logs from the failed rips is definitely in order!
Post Reply