Share via

Camera fails in Teams

Larry Lloyd 35 Reputation points
2025-09-16T11:59:29.8066667+00:00

Some of our users are having issues with their camera in Teams, where it randomly turns off, leaving just the 'background' picture.

This happens more often when other members of the meeting either enters or leaves the meeting.

This is happening on numerous devices, both Windows 10 Pro and Windows 11 Pro.

All devices are always kept up-to-date with security patches and drivers, which are forced to all users through intune within Azure. This includes making sure the Teams app is updated constantly.

A work-around is to unplug & re-plug the USB camera.

Some devices have been re-built with a fresh installation of Windows to solve the issue, however, this doesn't always solve the problem.

Our users are based globally and the problem is not limited to one country.

Sometimes the problem will not happen for a week, but then other times, it will happen multiple times in one day (sometimes to the same user).

Please note that unplugging & re-plugging the camera and/or restarting Windows is NOT an acceptable solution to this issue.

On searching the web for this problem, I can see it's been around for some time.

Does anyone know of verifiable fix for this problem please?

I've experimented with proposed 'fixes' I've seen posted on Microsoft sites for the last 6 months or so, without success.

I'm not looking to 'experiment' any further, which is why I've asked for a verifiable fix.

Thank you in advance.

Microsoft Teams | Microsoft Teams for business | Meetings and calls | Audio and video
Answer recommended by moderator
  1. NC123 10 Reputation points
    2025-09-24T16:06:45.3866667+00:00

    May or may not be of use Larry - ours is very much Teams cannot detect a camera error a pull and re-plug then works.

    We are trialling this reg key that seems to have improved matters for a couple of people (Early days)

    You're asking about the registry key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Media Foundation\Platform
Name: EnableFrameServerMode
Type: DWORD
Value: 0

    Here's what it does and why it's used: Copilot has summarised the key for me too below .

    🔧 Purpose of EnableFrameServerMode

    This registry key controls how Windows handles video capture devices (like webcams) through the Media Foundation framework. Specifically:

    • Setting it to 0 disables Frame Server Mode, which forces applications to access the webcam directly rather than through the Windows Frame Server.
    • This is often used to resolve issues with webcam or microphone functionality, especially in apps like Microsoft Teams, Skype, Zoom, or other conferencing tools.

    🧪 Why You Might Use It

    • If your webcam or mic isn't working properly, or if it freezes or fails to initialise, disabling Frame Server Mode can help.
    • It’s a known workaround for issues introduced in certain Windows updates where the Frame Server interferes with device access.

    🔁 Reboot Required

    After applying the key, a system reboot is necessary for the change to take effect.

    🧹 Troubleshooting If It Doesn’t Work

    If the issue persists, check:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\
    • Look for the {6BDD1FC6-...} GUID, which corresponds to Imaging Devices.
    • Ensure there are no corrupted entries and that UpperFilters/LowerFilters values are present and correctly configured.You're asking about the registry key: 
        HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Media Foundation\Platform

    Name: EnableFrameServerMode Type: DWORD Value: 0

      
  Here's what it does and why it's used:
  
  🔧 Purpose of `EnableFrameServerMode`
  
  This registry key controls how Windows handles video capture devices (like webcams) through the **Media Foundation framework**. Specifically:
  
  - **Setting it to `0` disables Frame Server Mode**, which forces applications to access the webcam directly rather than through the Windows Frame Server.
  
  - This is often used to **resolve issues with webcam or microphone functionality**, especially in apps like Microsoft Teams, Skype, Zoom, or other conferencing tools.
  
  🧪 Why You Might Use It
  
  - If your webcam or mic **isn't working properly**, or if it **freezes or fails to initialise**, disabling Frame Server Mode can help.
  
  - It’s a known workaround for issues introduced in certain Windows updates where the Frame Server interferes with device access.
  
  🔁 Reboot Required
  
  After applying the key, a **system reboot is necessary** for the change to take effect.
  
  🧹 Troubleshooting If It Doesn’t Work
  
  If the issue persists, check:
  
  ```sql
  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\
    • Look for the {6BDD1FC6-...} GUID, which corresponds to Imaging Devices.
    • Ensure there are no corrupted entries and that UpperFilters/LowerFilters values are present and correctly configured.

    2 people found this answer helpful.
    0 comments

7 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  2. Larry Lloyd 35 Reputation points
    2026-01-20T12:41:23.6333333+00:00

    It's been 3 months since my last posting on this issue 7 I thought I'd bring everything up-to-date.

    What was thought to be the final fix, was: the registry entry:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Media Foundation\Platform 

    Name: EnableFrameServerMode Type: DWORD Value: 0 

    and this has worked for 3 months without users reporting the issue, however, we've had 2 new Windows 11 devices built and put into production use and these were flagged up with the same issue and even though the above fix was applied, it didn't resolve the issue.

    With one PC, it was thought where the USB webcam was plugged into the PC's 'front' USB port, it was troublesome until it was then plugged into the PC's 'rear' USB port.

    The thinking behind this is that there may possibly be a power limitation restriction on the front USB port.

    However, with the second PC, this was already plugged into the rear USB port, therefore, the next fix attempt was to try the following:

    1. Identify your Camera's "Device Instance Path" 

    This is the most reliable way to find the exact registry key for your specific hardware. 

    Right-click the Start button and select Device Manager. 

    Expand the Cameras (or Imaging devices) section. 

    Right-click your camera and select Properties. 

    Go to the Details tab. 

    In the "Property" dropdown, select Device instance path. 

    Right-click the value (e.g., USB\VID_045E&PID_0779\6&...) and select Copy.  

    2. Locate the Power Settings in Registry 

    Instead of the Class GUID path, navigate to the specific device's hardware key: 

    In Registry Editor, navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\ 

    Paste the Device instance path you copied into the address bar (after Enum) and press Enter. 

    Expand the folder for your device and look for a subfolder named Device Parameters. 

    Inside Device Parameters, check if there is a subkey named Interrupt Management\TargetDeviceRelation or similar (this varies by driver). 

    If you cannot find AllowIdleIrpInD3 here, look for a subkey named WDF or PowerSettings. 

    3. Apply the Fix (Manual Creation) 

    If the value AllowIdleIrpInD3 does not exist in your camera's Device Parameters folder: 

    Right-click in the right pane of the Device Parameters folder. 

    Select New > DWORD (32-bit) Value. 

    Name it AllowIdleIrpInD3. 

    Double-click it and set the value to 0 (this explicitly disables the camera's ability to go into a low-power "idle" state, which often causes the Teams disconnect). 

    Note: In some environments, setting this to 1 is recommended to enable the IRB protocol, but for "disconnected" issues, 0 is often used to keep the device active. 

    1. Restart your computer to apply the change. 1. Identify your Camera's "Device Instance Path"  This is the most reliable way to find the exact registry key for your specific hardware. 
      1. Right-click the Start button and select Device Manager. 
      2. Expand the Cameras (or Imaging devices) section. 
      3. Right-click your camera and select Properties. 
      4. Go to the Details tab. 
      5. In the "Property" dropdown, select Device instance path. 
      6. Right-click the value (e.g., USB\VID_045E&PID_0779\6&...) and select Copy.  
      2. Locate the Power Settings in Registry  Instead of the Class GUID path, navigate to the specific device's hardware key: 
      1. In Registry Editor, navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\ 
      2. Paste the Device instance path you copied into the address bar (after Enum) and press Enter. 
      3. Expand the folder for your device and look for a subfolder named Device Parameters. 
      4. Inside Device Parameters, check if there is a subkey named Interrupt Management\TargetDeviceRelation or similar (this varies by driver). 
      5. If you cannot find AllowIdleIrpInD3 here, look for a subkey named WDF or PowerSettings. 
      3. Apply the Fix (Manual Creation)  If the value AllowIdleIrpInD3 does not exist in your camera's Device Parameters folder: 
      1. Right-click in the right pane of the Device Parameters folder. 
      2. Select New > DWORD (32-bit) Value. 
      3. Name it AllowIdleIrpInD3. 
      4. Double-click it and set the value to 0 (this explicitly disables the camera's ability to go into a low-power "idle" state, which often causes the Teams disconnect). 
      5. Note: In some environments, setting this to 1 is recommended to enable the IRB protocol, but for "disconnected" issues, 0 is often used to keep the device active. 
      6. Restart your computer to apply the change. 

    I'll try & remember to keep you updated.

    0 comments
  3. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.