May I ask a personal question? I'll ask it anyway. Do you know how to read?
I wrote in the message right above yours...
Do NOT try to replace the WidevineCDM yourself. It will not work!!
I went through this back in early November and the experiment was a failure. In the message above, I gave a link to the message thread that covered the TEMPORARY fix. The last message says...
Please, everybody, do not try replacing the WidevineCDM yourself. It will not work and could potentially interfere with any fix that StreamFab makes in the future. CDMCats.zip was an attempt to temporarily solve a problem at the time of its release. It will NOT solve anything now, and could possibly do much harm.
What more do I need to write so that you fully understand this?
I downloaded the full StreamFab 6.1.6.1 installer, and afterward checked and found that the AppData\Local\CEF directory was in fact supposed to update, as now Widevine is at version 4.10.2710.0.
I don't know why the AppData\Local\CEF directory didn't update after running the StreamFab updater... I had replaced the AppData\Local\CEF directory with the one from the temporary CEF fix, so maybe that had something to do with it? Anyway, you might want to check to make sure users running the updater aren't left with old versions of Widevine!â
The reason why the updater didn't install 4.10.2710.0 was it was never intended to. The 6.1.6.1 update was being finalized at the very time when we were just hearing that there might be a DRM issue. There is already a mechanism installed within StreamFab to automatically update the CDM, if need be, when StreamFab is run. This goes back to the 6.1.4.9 update. Just installing 4.10.2710.0 is not going to fix the problem. The Developers need to break the key codes for each affected module. That is where the problem lies, not in the CDM. I am told that the Developers are working night and day, including this weekend, to get a handle on the situation. Please learn to have some patience and let the ones with the source code do the fixing.