Thanks Gummigutta , The thread in the link is 2011. You would think in four years there would have been a solution .
These are quotes from the link . The first one doesn't seem like any effort to fix this is going to be done. Four years later the same proves that is the case.
I don't see myself putting several hours of my time into making (my edit: )Other decrypter "compatible" with a competing product that is completely superfluous to start with, when (my edit: )Other decrypter is installed.... (?)
This quote says the problem is the "Passkey" driver being loaded in the filter chain .
That is apparently even if Passkey has not been started .
I did find the "Passkey" driver in the DVD drive Properties/Drivers/Driver Details as dvdfab.sys .
It is also in the Windows registry as a string value Name "LowerFilters" data dvdfab .
The simple core of it: the passkey driver is running - and that, in the end, is the component doing the job. If that is what you mean with "actively running", the loaded driver in the filter chain is enough.
The question about the quotes below is sort of asked below.
Is the Passkey driver (dvdfab.sys) loaded & running even when Passkey isn't "Started" or active ?
With passkey on, the disc is (at least partially) decrypted and that causes a mess - especially because passkey doesn't do the job to the end, it leaves some sort of "hybrid" protected/unprotected disc behind.
as long as the passkey driver is running, I risk invalid hashes to be transmitted to our protection database, because passkey doesn't work correctly.
Do the DVD/BD drives use dvdfab.sys even when Passkey hasn't been started ?
I don't know . If there is a method to check this maybe someone can post it.
If the DVD/BD drives use dvdfab.sys even when Passkey isn't started maybe that is the problem . I doubt that is what's happening .
Since I don't have both Passkey & the Other decrypter installed on the same OS I can't check to see which driver loads or which loads first . Even if I knew how.
@ signals since you have both installed . Is there a way to detect this ?
Does the Passkey driver get loaded & used by the DVD/BD drives first ?
Even when Passkey isn't started ?
From the "Filter Driver Load Order" you posted it would seem the dvdfab driver loads first.
Of course I don't know if this was with both decrypters started . Or if either or both were off.
Right now it seems to me just the presence of the Passkey driver is enough to get the warning . If it is inactive when Passkey is off then it shouldn't cause the problem that the Other decrypter claims it does .