www.makemkv.com

Dump file attached to this topic as well.

brardith wrote: Mon Apr 14, 2025 1:54 pm Dump file attached to this topic as well.

Have you tried downloading the latest KEYDB.cfg file, copying it into MakeMKV's data directory (i.e. where MakeMKV also writes its TGZ dump files) and restarting MakeMKV?

MrPenguin wrote: Mon Apr 14, 2025 2:13 pm

brardith wrote: Mon Apr 14, 2025 1:54 pm Dump file attached to this topic as well.

Have you tried downloading the latest KEYDB.cfg file, copying it into MakeMKV's data directory (i.e. where MakeMKV also writes its TGZ dump files) and restarting MakeMKV?

Yeeeeup, I tried it with the keydb dated for today (04/14/2025). Apologies for not including this in the original post.

brardith wrote: Mon Apr 14, 2025 2:52 pm Yeeeeup, I tried it with the keydb dated for today (04/14/2025). Apologies for not including this in the original post.

OK, but AFAICT your disk ID is 0xC528510317D147DCA9F229449732770214D4786A, and the latest KEYDB.cfg has a matching entry.

MrPenguin wrote: Mon Apr 14, 2025 3:22 pm

brardith wrote: Mon Apr 14, 2025 2:52 pm Yeeeeup, I tried it with the keydb dated for today (04/14/2025). Apologies for not including this in the original post.

OK, but AFAICT your disk ID is 0xC528510317D147DCA9F229449732770214D4786A, and the latest KEYDB.cfg has a matching entry.

Let's troubleshoot my process here since I'm the most likely failure point:

Process should be:
1. unzip keydb.cfg to C:\Users\<username>\.MakeMKV
2. Close MakeMKV (if it wasn't already)
3. Open MakeMKV
4. Attempt to open disc

Yes? That's the process I took. I suppose I can do a full reboot to be sure, but I downloaded a super-fresh copy at 0750 my time (about an hour ago), and couldn't open the disc. I will download an EVEN FRESHER copy, swap em out, and do a full reboot.

MrPenguin wrote: Mon Apr 14, 2025 3:22 pm

brardith wrote: Mon Apr 14, 2025 2:52 pm Yeeeeup, I tried it with the keydb dated for today (04/14/2025). Apologies for not including this in the original post.

OK, but AFAICT your disk ID is 0xC528510317D147DCA9F229449732770214D4786A, and the latest KEYDB.cfg has a matching entry.

I downloaded a copy 4 minutes ago and can confirm it has the disk ID you copied above, so I imagine when I put that one in there it'll work just fine.

brardith wrote: Mon Apr 14, 2025 3:52 pm I downloaded a copy 4 minutes ago and can confirm it has the disk ID you copied above, so I imagine when I put that one in there it'll work just fine.

Yes, I would expect it to...