Getting a "Conversion failed. Transcoder crashed or failed to start up" error.

[sa2000]

@eutsey

after following this thread on and off since February-ish of 2018 I finally feel compelled to reply. While Malwarebytes may very well have caused problems, as any AV could do, I’ve not used MB, even in a temp fashion, on my systems. I’ve suffered from transcoder errors for over a year, still to this day (upnp is fine). I’ve gone through the troubleshooting suggestions on this thread that I could, excluding installing betas and uploading my logs. I’ve run my Plex box with no AV or firewall at times, and through different switches and routers, just to rule that out. I stream to different devices including Xbox, Apple, Win7 and Win10 w/different browsers and the apps, all with failures. In my case, MB is not the problem. AV is not the problem. So, to proclaim that an AV or security app is the ultimate problem is BS. I do see that I dodged a bullet though, as I was fixing to do a premium membership when this problem started back in 2018. Luckily, I didn’t. I’ll keep checking back every once an a while and see if anything comes up. But, at this point it looks like the folks posting problems here have moved on as have I

The error this topic relates to is generic and could be due to lots of different reasons. Underlying errors within logs may point to specific causes and the reference to malwarebytes premium was very specific to a specific set of underlying log entries that appear in the log.

Each case needs to be looked into and investigated starting with debug logs and may need clips/sample media files etc

I cannot see any logs from you in the forums or any request for assistance. The issue now seen to be caused by recent changes / functionality in MalwareBytes Premium did occur before that after a windows 10 update which Microsoft retracted 8 days later - back in July 2018.