Windows 10 Pro 10122 Fatal Error

[richci]

Hi,

My PC just got the latest Windows 10 preview update. Now all disks fail with 'Fatal error occurred, program will now exit'. It happens after clicking the disk, when makeMkv is finding the titles. Windows 10 was working fine with all previous previews.

Is this a known issue? Is there some way I can get logs for investigation?

Thanks
Rich

[Woodstock]

If you have debug logging enabled, you'll have everything that MakeMKV saw, but... it might not help.

Searching Google for build 10122 of Win10 might net you some information, but I doubt Mike has had any chance to test MakeMKV on it.

[richci]

Right - unfortunately there is nothing useful in the log.
I couldn't find anything with a web search.
The crash happens when its parsing /AACS/Content000.cer btw.
Thanks

[aquabeef]

I am seeing similar behavior. It has locked up at various screens. It was working earlier in the week before the 10122 update for Windows 10. It doesn't always lock at the same place but a frequent log is:

Code: Select all

MakeMKV v1.9.2 win(x64-release) started
Using direct disc access mode
Error 'Scsi error - ILLEGAL REQUEST:COPY PROTECTION KEY EXCHANGE FAILURE - AUTHENTICATION FAILURE' occurred while issuing SCSI command A30..00200740100720..09D07459823A75661129206D503ECBB9D42 to device 'SPTI:\Device\CdRom0'

Uploaded the full log here:
https://drive.google.com/file/d/0ByFo8D ... YzZ2M/view

[aquabeef]

I am also seeing this error. I uploaded a log here:

https://drive.google.com/file/d/0ByFo8D ... YzZ2M/view

I think the first error is this:

Code: Select all

002004:0000 Error 'Scsi error - ILLEGAL REQUEST:COPY PROTECTION KEY EXCHANGE FAILURE - AUTHENTICATION FAILURE' occurred while issuing SCSI command A30..00200740100720..08B38919C7369AC786E8CA1C01C69DC196B to device 'SPTI:\Device\CdRom0'

I can sometimes get past the scanning phase but it still locks a few minutes into the process of making the mkv.

[rjw2558]

I just started getting an RPC Protection error on all previously burned discs, also, as of this Windows 10 build. Have resorted to using a Windows 7 laptop with the current MakeMKV version running on it to avoid the issue.

[richci]

I found that reverting Windows 10 to 10074 (from the Settings->Windows Update->Recovery menu) resolved the issue.

[Woodstock]

Hopefully, you reported this to Microsoft... Not sure if they hear much from the ripping community during the beta tests...

[richci]

I did.

[aquabeef]

How would you phrase the reporting to Microsoft? Is there a specific error or message in the log you would use when reporting it to them?

[Woodstock]

I'd give them a link to the makemkv download, and describe how it works with build XXXXXX, but build YYYYYY reports this error, using same hardware and software. Short of debugging experience and resources, that's about all you CAN report.

[rjw2558]

Isn't it possible this change to Windows 10 was intentional and likely to be permanent (to enforce some sort of DRM thing)? If that's the case, then the MakeMKV software will need to hack around it in a later version, right?