@Cats4U Not just on your end, it updated here as well. Not finding it in the AS install directory so they're using a different method?
I didn't see Amazon Prime in the list of supported sites so I'm not sure updating is going to help me there.
Ok NewMelle peace. We can agree on "one problem".
125 is still in beta. From version 127 onwards, ancient CPUs will be removed (without SSE3), I don't know if that will cause problems too.
I don't know exactly which version is packaged in Streamfab, but if they say 102 is included and Windows 7 goes up to 109, then the situation is even sadder than it already is.
Sebastian001
Don't get me wrong, I'm not pissed. I don't mind if SF abandons Win7. It is the way of the world according to Microsoft and everyone sooner or later kisses their ass, some out of necessity, others out of naivety. The point I was trying to make is upgrading to Win10/11 has zero impact on the issues we're seeing with SF.
TPM should be an option, not a requirement. If the TPM fails you're done. Toast. It is fairly easy to get around the TPM 2.0 requirement for Win11 but can't go into that here. The Win7 system I am using right now also has a Win11 boot drive and no TPM module. Slowly but surely I am TRYING to migrate everything over to 11 but that is a long ways off.
I have not tried SF with Paramount+ recently (I don't want my account locked out again) and I'll be darned if I'm buying the Disney+ plugin just to test (and most likely be disappointed or worse).
6.1.7.7 does "
work" with Amazon but I use that term loosely as I don't consider re-encoding an acceptable solution to the DRM issue. I simply won't accept the long processing times that I experience with
my system configuration. In the recent past something I did not experience.
I still think it a bit odd there are 5 versions of Widevine CDM installed (this is a fresh install of 6.1.6.7). I'm curios if the browser errors above are due to the wrong version of Widevine being used for those providers.