Version 2.0.0 won't open the disk structure (bug?)

[dom61]

Good morning.
The new 2.0.0 release can't open the disk structure; it freezes, and I don't know why.
I had to revert to release 1.18.4, which works perfectly.
Thank you.

Version 2.0.0


Version 1.18.4

[cassiusdrow]

I'm having the same issue. MakeMKV gives the message "AACS directory not present, assuming unencrypted disc", then hangs for several seconds, then gives a popup with message "Fatal error occurred, program will now exit." I assume these are the same messages as above.

These items failed with the error, all with no AACS folder:

1. Bluray iso disc images (never encrypted)
2. Bluray BDMV folders (never encrypted)
3. Bluray iso disc images (unencrypted by AnyDVDHD)
4. Bluray iso disc images (unencrypted by Xreveal)

These items succeeded:

1. Physical Bluray discs (encrypted, has AACS folder)
2. DVD iso images (unencrypted by AnyDVDHD and Xreveal)

All of the items work fine in 1.18.4.

[Het Beest]

These items failed with the error, all with no AACS folder:

3. Bluray iso disc images (unencrypted by AnyDVDHD)
4. Bluray iso disc images (unencrypted by Xreveal)

These items succeeded:

1. Physical Bluray discs (encrypted, has AACS folder)

I can confirm these three, same here. Working with Windows 11.

[dom61]

I'm wondering if this is the right place to open a ticket, or if there's a specific section for that.
Thank you

[Nucleus]

Exact same issue here with multiple discs in v2.0.0, discs are clean. Is this fixed yet or does anyone know a workaround?

Edit: Exact same discs rip perfectly in older v1.1.8.4

Code: Select all

https://makemkv.com/download/old/

[Sayaka]

2.0.0 appears to be very buggy, the only known workaround for these bugs at the moment is to downgrade to 1.18.4 or an even earlier version (and to use either the current beta key or a previously purchased permanent key).

[cbusillo]

Same crash here with 2.0.0 on macOS. makemkvcon segfaults on any Blu-ray image or folder that has no AACS directory. It logs "AACS directory not present, assuming unencrypted disc" and then crashes (exit 139).

What I tested:
- Four decrypted Blu-ray images: two 3D, one UHD, and a backup MakeMKV made itself.
- Both iso: and file: sources.
- macOS 26.7.1 and 27.2, with both the arm64 and x86_64 builds.
- With and without a registration key.

All of them crash in 2.0.0. The same images read fine in 1.18.4 with a key.

The crash log shows a null pointer read inside makemkvcon. I can send it, or test a fix build, if that helps.

[Caffeine]

Perhaps interesting here is that the v2.0.0 file size was lower than all previous versions, bucking the trend of gradually increasing file sizes. My thought is that it's a bad build, missing something. Perhaps a "clean-up" was done for 2.0.0 and something was inadvertently removed. All on Windows 11:

v2.0.0: 14,781 KB

v1.18.4: 16,048KB
v1.18.3: 15,965KB
V1.18.2: 15,220KB
v1.17.9: 15,081KB
V1.17.2: 14,784KB

[rfmacdon]

Hello,

I love your product! I had the same issue when trying to rip Slow Horses Blue-ray disc using v2.0.0. I followed the advise from one of the members on this thread by reinstalling version 1.18.4 for macOS and it works perfectly.

[j-h-s]

Same here, 2.0.0 on cachyos linux was not opening a backup created with the same edition just minutes earlier.

Tried 1.18.3 on windows with the same backup, it opened fine.

Updated windows to 2.0.0 and it threw the same issue as linux

[GravuTrad]

Hello to all.

I confirm the problem. new version 2.0.0 crashes when it tries to analyse titles. Back to 1.18.4 and a key was the temporary solution. I hope it will be solved soon before to not have any key available, for this great unique tool.

[lukecro]

I've been hitting the same problem since upgrading. MakeMKV version 2.0.0 on MacOS. Every time I try to open a BDMV file, I get a fatal error crash.

Reverted to v1.18.4 for now.

[gwhitcombe71]

I can send it, or test a fix build, if that helps.

cbusillo mine doesnt segfault like yours, but thats on Windows 10... i get the "assuming unencrypted disc" line, it hangs for a good 10 seconds (thought it had died) and then the fatal error popup. Tried a couple of BDMV folders I ripped last year and same result, all fine again after going back to 1.18.4 with the beta key. definately sounds like the same bug though, just a different way of falling over

[Jacksoft]

Same problem here with 2.0.0. Rolled back to 1.18.4 worked fine (Windows 10 LTSC).

[Kupori]

Had the same Issue on 2.0.0, rolled back to 1.18.4 and error still occur (windows explorer still can read the disc) any suggestions?