{"id":3868,"date":"2016-08-20T01:14:19","date_gmt":"2016-08-19T19:44:19","guid":{"rendered":"http:\/\/198.58.113.91\/blog\/?p=3868"},"modified":"2020-09-04T02:39:49","modified_gmt":"2020-09-04T02:39:49","slug":"webcam-anniversary-update-windows-10-yuys-standard","status":"publish","type":"post","link":"https:\/\/www.winhelponline.com\/blog\/webcam-anniversary-update-windows-10-yuys-standard\/","title":{"rendered":"Fix Webcam Issues in Windows 10 by Disabling Frame Server Mode"},"content":{"rendered":"

A technological change made in Windows 10 Anniversary Update caused a problem where webcams failed to work, and the respective software (like Logitech, Skype) simply hung up within minutes of use.<\/p>\n

This problem was first perceived as a bug in the Anniversary Update, but it appears to be an intentional change in the Redstone 1 update. Microsoft seems to have dropped support for MJPEG or H264 encoding standards and moved towards YUY2 for performance. Webcams that use MJPEG or H264 would not work correctly after the Anniversary Update.<\/p>\n

Fix for Webcam issues in Windows 10<\/h2>\n

Rafael Rivera<\/a> has found a workaround for this issue. Follow these steps:<\/p>\n

    \n
  1. Create a Restore Point<\/a> first.<\/li>\n
  2. Start Regedit.exe and go to the following key:\n
    HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows Media Foundation\\Platform<\/pre>\n<\/li>\n
  3. Create a REG_DWORD value named EnableFrameServerMode<\/strong> and leave the data to 0<\/code>.<\/li>\n
  4. If you’re using Windows 64-bit, make the changes here, in addition:\n
    HKEY_LOCAL_MACHINE\\SOFTWARE\\WOW6432Node\\Microsoft\\Windows Media Foundation\\Platform<\/pre>\n
    The above key is for 32-bit applications running on a Windows 64-bit computer.<\/li>\n
  5. Exit the Registry Editor.<\/li>\n<\/ol>\n
    \n
    Realtek drivers specific issue<\/h3>\n
    The following error may be logged in the System Event Log repeatedly:<\/p>\n
    Service Control Manager - The Windows Camera Frame Server service terminated unexpectedly. It has done this 20 time(s).<\/pre>\n
    The following error consistently occurs just after the above error as logged in the Event Application Log:<\/p>\n
    Application Error - Faulting application name: svchost.exe_FrameServer, version: 10.0.18362.1, time stamp: 0x32d6c210\r\nFaulting module name: RsProvider.dll, version: 1.30.0.0, time stamp: 0x57ee1a06\r\nException code: 0xc0000005\r\nFault offset: 0x000000000007bd6d\r\nFaulting process id: 0x458\r\nFaulting application start time: 0x01d6619a58c690a6\r\nFaulting application path: C:\\Windows\\System32\\svchost.exe\r\nFaulting module path: C:\\Program Files\\Realtek\\RsProviders\\RsProvider.dll\r\nReport Id: b5fe8c79-a485-428f-8087-e7a90ce0d976\r\nFaulting package full name:\r\nFaulting package-relative application ID:<\/pre>\n
    The RsProvider.dll<\/code> (a Realtek driver file), appears to be the issue causing the Windows Camera Frame Server service to crash.\u00a0It has been observed that renaming the RsProviders<\/code> folder fixes the issue which would prevent RsProvider.dll<\/code> from being used.<\/p>\n
    Go to the following folder:<\/p>\n
    C:\\Program Files\\Realtek<\/pre>\n
    In that folder locate and then right-click and rename the RsProviders<\/code> folder to something else such as RsProviders_<\/code><\/p>\n
    Log out and then log back in again (or restart the computer).<\/p>\n<\/div>\n
    References<\/h3>\n