www.makemkv.com

I have a set of the World At War DVDs Each disc so far has take a long time to open (over an hour) but one particular disc will not open MakeMKV works for over two hours and the error log eventually just said "Failed to open disc". Here is the log. How can I get this to work?

MakeMKV v1.9.8 win(x64-release) started
The new version 1.9.9 is available for download at /download/
Drive BD-ROM ATAPI iHOS104 WL0D has RPC protection that can not be bypassed. Change drive region or update drive firmware from http://tdb.rpc1.org. Errors likely to follow.
Using direct disc access mode
Title #1 has length of 43 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Complex multiplex encountered - 6 cells and 3619 VOBUs have to be scanned. This may take some time, please be patient - it can't be avoided.
Title #2 was added (6 cell(s), 0:52:11)
Complex multiplex encountered - 6 cells and 3554 VOBUs have to be scanned. This may take some time, please be patient - it can't be avoided.
Title #3 was added (6 cell(s), 0:51:15)
Complex multiplex encountered - 6 cells and 3447 VOBUs have to be scanned. This may take some time, please be patient - it can't be avoided.
Title #4 was added (6 cell(s), 0:49:44)
Title #5 has length of 10 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Failed to open disc

Do you have debug logging turned on? The log seems a bit lacking on some details that should be shown in cases like this. Doing the version update probably won't change anything, but it is recommended.

Here is the output again with debug turned on.

MakeMKV v1.9.8 win(x64-release) started
Debug logging enabled, log will be saved as C:\Users\EynonsAdmin/MakeMKV_log.txt
The new version 1.9.9 is available for download at /download/
DEBUG: Code 134219780 at RNslRB(01z1q2/lUw:29393769
DEBUG: Code 0 at RNslRB(01z1q2/lUw:213131916
Drive BD-ROM ATAPI iHOS104 WL0D has RPC protection that can not be bypassed. Change drive region or update drive firmware from http://tdb.rpc1.org. Errors likely to follow.
Using direct disc access mode
Title #1 has length of 43 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Complex multiplex encountered - 6 cells and 3619 VOBUs have to be scanned. This may take some time, please be patient - it can't be avoided.
Title #2 was added (6 cell(s), 0:52:11)
Complex multiplex encountered - 6 cells and 3554 VOBUs have to be scanned. This may take some time, please be patient - it can't be avoided.
Title #3 was added (6 cell(s), 0:51:15)
Complex multiplex encountered - 6 cells and 3447 VOBUs have to be scanned. This may take some time, please be patient - it can't be avoided.
Title #4 was added (6 cell(s), 0:49:44)
Title #5 has length of 10 seconds which is less than minimum title length of 120 seconds and was therefore skipped
DEBUG: Code 1 at Re5~1PJy2|l1>:213132422
DEBUG: Code 0 at 6S%3qNgI&ip1j$=a5;:213140633
DEBUG: Code 0 at |6`6$-*z{W9T[8tE:121271548
DEBUG: Code 0 at |6`6$-*z{W9T[8tE:121265798
DEBUG: Code 0 at 6S%3qNgI&ip1j$=a5;:213140633
DEBUG: Code 0 at |6`6$-*z{W9T[8tE:29403866
DEBUG: Code 0 at |6`6$-*z{W9T[8tE:121265798
DEBUG: Code 0 at 6S%3qNgI&ip1j$=a5;:213140633
DEBUG: Code 0 at 6S%3qNgI&ip1j$=a5;:121276999
DEBUG: Code 1 at FA!H.ER3Zbsbl:`e:213130789
DEBUG: Code 0 at 1!XX3b|IeUg6cLv:121270927
DEBUG: Code 0 at LGB`okG!m*?dEN:29398530
DEBUG: Code 0 at 6S%3qNgI&ip1j$=a5;:213140633
DEBUG: Code 0 at |6`6$-*z{W9T[8tE:29403866
DEBUG: Code 0 at |6`6$-*z{W9T[8tE:121265798
DEBUG: Code 0 at 6S%3qNgI&ip1j$=a5;:213140633
DEBUG: Code 0 at 6S%3qNgI&ip1j$=a5;:121276999
DEBUG: Code 1 at FA!H.ER3Zbsbl:`e:213130789
DEBUG: Code 0 at 1!XX3b|IeUg6cLv:121270927
DEBUG: Code 0 at LGB`okG!m*?dEN:121266580
DEBUG: Code 0 at 6S%3qNgI&ip1j$=a5;:213140633
DEBUG: Code 0 at |6`6$-*z{W9T[8tE:29403866
DEBUG: Code 0 at |6`6$-*z{W9T[8tE:121265798
DEBUG: Code 0 at 6S%3qNgI&ip1j$=a5;:213140633
DEBUG: Code 0 at 6S%3qNgI&ip1j$=a5;:121276999
DEBUG: Code 1 at FA!H.ER3Zbsbl:`e:213130789
DEBUG: Code 0 at 1!XX3b|IeUg6cLv:121270927
DEBUG: Code 0 at LGB`okG!m*?dEN:121266580
Failed to open disc

The debug codes given will have to be interpreted by Mike, but hopefully they'll provide some insight into why the disk was failing to open.

At a guess, based upon similar messages in the past, you MAY have one of those drives that doesn't like to say "failed read", and instead returns something almost, but not quite, entirely unlike valid data. Mike has mentioned them in the past - a sector isn't completely readable, but they try to construct something from what was readable, rather than report the error.

In the best case, the data was valid but the "check bits" were faulty. But that's kind of like the "best case" of driving off a cliff and encountering such an incredible updraft that your car makes it to the other side of the valley and lands gently on the road on the other side.... It could happen, but....