Dump Submitted - Lifeforce - tgz

Please post here for issues related to UHD discs
Post Reply
VideoNerd
Posts: 4
Joined: Sun Jan 04, 2026 6:00 pm

Dump Submitted - Lifeforce - tgz

Post by VideoNerd »

Providing a tgz for UHD 4k release of Lifeforce to assist with updating the KEYDB file.

I received a "The volume key is unknown for this disc - video can't be decrypted Failed to open disc" error using the latest version of MakeMV and KEYDB.

MKB20_v76_Lifeforce_DE63.tgz

Link to the tgz file:
https://drive.google.com/file/d/1ra1g3n ... drive_link
MrPenguin
Posts: 1593
Joined: Thu Oct 19, 2023 11:31 pm

Re: Dump Submitted - Lifeforce - tgz

Post by MrPenguin »

VideoNerd wrote:
Sun Jan 04, 2026 6:27 pm
Providing a tgz for UHD 4k release of Lifeforce to assist with updating the KEYDB file.
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?
VideoNerd
Posts: 4
Joined: Sun Jan 04, 2026 6:00 pm

Re: Dump Submitted - Lifeforce - tgz

Post by VideoNerd »

FYI - Yes, I've downloaded the latest KEYDB file and restarted MakeMKV. Same results.
MrPenguin
Posts: 1593
Joined: Thu Oct 19, 2023 11:31 pm

Re: Dump Submitted - Lifeforce - tgz

Post by MrPenguin »

VideoNerd wrote:
Sun Jan 04, 2026 7:03 pm
FYI - Yes, I've downloaded the latest KEYDB file and restarted MakeMKV. Same results.
And yet KEYDB.cfg has contained your disk since at least 18th December 2025?
Coopervid
Posts: 4087
Joined: Tue Feb 19, 2019 10:32 pm

Re: Dump Submitted - Lifeforce - tgz

Post by Coopervid »

VideoNerd wrote:
Sun Jan 04, 2026 7:03 pm
FYI - Yes, I've downloaded the latest KEYDB file and restarted MakeMKV. Same results.
You must check your setup of the .makemkv directory. Guys like you are really frustrating the people who support KEYDB.cfg. If you are on Windows use SamuriHL's tool.
VideoNerd
Posts: 4
Joined: Sun Jan 04, 2026 6:00 pm

Re: Dump Submitted - Lifeforce - tgz

Post by VideoNerd »

Thank you to everyone who responded to this post. I've updated the KEYDB file again this morning (Just a few days newer that the last one I had downloaded) and the issue seems to be resolved. The process that I used to update the file locally was the same process that I've used prior - not sure what the hiccup was but I will be much more diligent going forward. Thank you as well for mentioning the SamuriHL tool. This is looks to be incredibly useful and I'll be using it to check every disc going forward.
Post Reply