Forum Discussion
Error code: FACILITY_VISUALCPP/ERROR_PROC_NOT_FOUND
- Apr 13, 2022One potential cause we've found for this is for users who have manually installed FFMpeg at some point. Can you see if the file C:\Windows\System32\ffmpeg.dll exists? If it does, try renaming it to something like ffmpeg2.dll and see if that helps. If it does, then you're hitting the known issue.
- Hashad870Sep 19, 2022Copper Contributor
josh_bodner
Can't find a file with such name, what can I do then? - mangomasseJul 30, 2022Copper ContributorI have the same problem but the ffmpeg.dll does not exist in my file. What can I do?
- AliAmine88Sep 08, 2022Copper Contributor
mangomasse Hi i have same probleme and i don't find the ffmpeg.dll too, so did you find the solution plz?
- Sabri01Apr 18, 2022Copper ContributorThanks, this fixed it. To confirm, I'm on Edge Dev Version 102.0.1220.1.
- XaeonApr 14, 2022Copper ContributorHi Josh,
Similar to MartMcd1, I have the ffmpeg.dll file (since 2016 in my case) and renaming it did fix it for me as well. Many thanks for that! 🙂
Why does this media codec suddenly affect the operation of the Edge browser in such a dramatic way? And why does it matter it was installed 'manually'? Is it now part of any of the standard MS components? - MartMcd1Apr 13, 2022Copper ContributorThanks Josh, That fixed it.
Now I just need to figure out where ffmpeg came from and do I need i - mjdalwaysApr 13, 2022Copper Contributor
josh_bodner Thanks that fixed it, although curious why it only just broke, its been working for months without a problem, just the latest version caused the error (which makes it much harder to troubleshoot).
- MartMcd1Apr 13, 2022Copper Contributor
josh_bodner I haven't manually installed ffmpeg (at least not knowingly) and the .dll is dated August 12th 2014.
however, I noticed that Edge Canary suffered the same issue and have now renamed the .dll. Edge Canary is now working so this does look like it may be the solution.
I had uninstalled Edge Dev and installed an older build which is working, having renamed the dll I will try the update again and let you know.