www.makemkv.com

New UHD Dis Operation Fortune will not open. Log has been sent.

Danke

metoo

Thank you very much in advance
Harri

I have the same problem

Same here

Has anyone gotten this to work?

I submitted Walmart non-steel book two days ago.

Thank you, Mike.

I'm also having the problem. I sent in a dump file and log file.

Thanks, will submit the file. Reboot didn't work after all for this disc.

Email the dump to svq@makemkv.com

Same issue here. I submitted the dump a bit over a month ago, tried it again today, still can't open the disc.

What's the typical timeline to get the disc added? The first log was sent in April, so we're on month five. Is that normal, or is there perhaps something wrong, like not enough data to open the disc?

So it's been seven months since this thread was opened and someone submitted the first dump file.

I bought this disc three months ago and still can't watch it. I've emailed svq@ three times without any reply. I tried ripping it again today, same error as always.

Is there anything we can do? Does anyone know someone on the MakeMKV team that might be able to help?

No one has posted what the name of their dump file is, so we can't know if you're all submitting the same dump or not. Also, no one has posted if they've had any success.

In your case, KENSAI, none of that should matter. Assuming you've emailed the .tgz dump file to svq@makemkv.com and that your emails haven't bounced or failed for some reason, then the giant key generating machine in the sky should have your dump file.

Are you sure your system is able to download keys? Are you getting the "Automatic HK downloading is disabled or failed." message?

Indeed, it turned out the problem was on my side: earlier this year I'd used my Firewalla (a hardware firewall) to block all incoming/outgoing IP traffic to China. When I tried ripping two more 4K discs today, they failed, so I put my machine into a state where the Firewalla wouldn't block anything. And, of course, it worked. I can now rip Operation Fortune, and the problem was on my side all along.

While I do wish there was a more clear "Can't reach server" type message, ultimately this is all on me.