AACS MKB updates to drives

Firefall · 29th December 2025, 17:26

Hi! I have a question concerning AACS MKB updates. I used to have 2 internal BD drives in my PC. I've ripped various Blu-rays with them. MakeMKV told me that the "Highest AACS version" was 77 for both of them. I was deliberately waiting to rip a more recent disc to avoid updating the AACS version of my drives. I then bought an external drive, connected it to the same PC, and inserted one such disc to validate its MKB version. It ended up being MKBv81. Next thing I know, MakeMKV is now telling me that all three drives' "Highest AACS version" is now 81, even though that disc was only in the external drive.

- Why did this happen? Do the drives spread MKBs amongst them?
- Do I risk updating all my drives' MKB whenever I connect a drive with a newer MKB to the same PC?

All of this happened under Windows 10 Pro in case it matters. I guess I'm still OK with v81, but AFAIK the current public device keys and certificates are invalidated in v82, so I'm hesitant to touch more recent discs at this point.

spotter · 31st December 2025, 10:20

I'd hazard to say its just an makemkv thing, not a drive thing. MakeMKV caches the highest mkb it has processed and show that for all drives.

lamp · 31st December 2025, 19:20

I have seen this behavior as well, as mentioned above I believe it is just a MakeMKV thing, only 1 of my drives was "poisoned" with the newer MKB version and all the rest still work correctly, even though MakeMKV says they are all MKB v82

Dennis98 · 10th January 2026, 23:59

I noticed the same in October when I connected a second drive and was surprised it apparently had the same "AACS"/MKB version.
But I already thought it might not actually be the case and MakeMKV just had that cached for example.
Today I got curious and checked the registry for that value and it's not there, but I found this thread:
https://forum.makemkv.com/forum/viewtopic.php?t=18908

So basically MakeMKV stores it in its data directory when it encounters a higher MKB than it has seen before. I can confirm I see a file matching the shown version on my machine. And this is not per drive.

29th December 2025, 17:26	#1 \| Link
Firefall Registered User Join Date: Nov 2025 Posts: 3	AACS MKB updates to drives Hi! I have a question concerning AACS MKB updates. I used to have 2 internal BD drives in my PC. I've ripped various Blu-rays with them. MakeMKV told me that the "Highest AACS version" was 77 for both of them. I was deliberately waiting to rip a more recent disc to avoid updating the AACS version of my drives. I then bought an external drive, connected it to the same PC, and inserted one such disc to validate its MKB version. It ended up being MKBv81. Next thing I know, MakeMKV is now telling me that all three drives' "Highest AACS version" is now 81, even though that disc was only in the external drive. - Why did this happen? Do the drives spread MKBs amongst them? - Do I risk updating all my drives' MKB whenever I connect a drive with a newer MKB to the same PC? All of this happened under Windows 10 Pro in case it matters. I guess I'm still OK with v81, but AFAIK the current public device keys and certificates are invalidated in v82, so I'm hesitant to touch more recent discs at this point.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

31st December 2025, 10:20	#2 \| Link
spotter Registered User Join Date: Jan 2002 Posts: 290	I'd hazard to say its just an makemkv thing, not a drive thing. MakeMKV caches the highest mkb it has processed and show that for all drives.

31st December 2025, 19:20	#3 \| Link
lamp Registered User Join Date: Nov 2024 Location: USA Posts: 9	I have seen this behavior as well, as mentioned above I believe it is just a MakeMKV thing, only 1 of my drives was "poisoned" with the newer MKB version and all the rest still work correctly, even though MakeMKV says they are all MKB v82

10th January 2026, 23:59	#4 \| Link
Dennis98 Registered User Join Date: Jan 2026 Posts: 3	I noticed the same in October when I connected a second drive and was surprised it apparently had the same "AACS"/MKB version. But I already thought it might not actually be the case and MakeMKV just had that cached for example. Today I got curious and checked the registry for that value and it's not there, but I found this thread: https://forum.makemkv.com/forum/viewtopic.php?t=18908 So basically MakeMKV stores it in its data directory when it encounters a higher MKB than it has seen before. I can confirm I see a file matching the shown version on my machine. And this is not per drive.