This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Split from this thread.
I too have a similar problem with the camera and Surface Pro 8. I use Windows Hello to log in and after the device has been left for some time the device will unlock but if you then try to use video in a Teams call the screen will be blank and it will report that no camera is present. I have run Windows update, Updated the camera drivers, and run the surface app to check the firmware is up to date. run the Surface hardware diagnostic tool. None of these found any problem.
I have updated the Teams Client, and tested with both the desktop and web client. when having the issues and the problem it present on both.
I full reboot will get the camera working but that is not possible when in the middle of a call.
The only way to fix it without rebooting is to open the device manager and disable and then enable the camera. This will normally fix the video in Teams.
We are a small company but we all run Surface Pro 8's managed by Autopilot/Intune with very little in the way of additional software. All are less than 12 months old. More than 50% of the staff are having issues with video calls within Teams after a period of inactivity.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Same here. Surface Pro 8, applied January updates (and the one before that, and so forth...) Still getting the same issues with Windows Hello and Camera light stuck on.
It's a little discouraging to hear that the SP9 is working well, as it leaves one to feel that the problem could be addressed on the SP8 if it were a higher priority.
For what it's worth, getting the impression that my one-generation-back product is being ignored will have some impact on my future Surface shopping plans.
Try updating the graphics drivers manually .. it seems like that fixed it on my Surface 8, finally. https://www.intel.com/content/www/us/en/download/785597/intel-arc-iris-xe-graphics-windows.html
These gfx drivers (Intel Xe on my system) apparently arn't always pushed to latest Intel version via windows update b/c it appears the surface team does QA on them before pushing them out.. (this is a good thing generally.. )
but it seems like as a result of that process things that fix bugs like this sometimes lag a little. Hopefully this works for others.
Chiming in with my own experience with what I suspect is the same bug.
Microsoft Surface Pro 7
Fully updated driver on the Surface camera.
I run into an issue any time I use my Surface's camera in a meeting.
In Google Meet (in Microsoft Edge), the camera will function just fine until some time later (usually after a period of inactivity, like while waiting for the other person and working in a different tab). Eventually, the screen just freezes, though the camera says it is there. Turning off the camera in Google Meet suddenly gets the program to recognize that a problem has occurred, because the screen will go black and Google Meet will now insist that I have no camera. Meanwhile, the camera light continues to be on. Going to the Camera Privacy Settings in Windows, it will show the camera is currently in use by the browser. Force closing the browser from the task manager does not change the Camera Privacy Settings from saying that the browser is using the camera. Trying to change the camera's settings in Windows Camera Settings will never finish loading the page to allow you to affect anything other than disabling it. Disabling it will not turn off the camera light (restart must happen in order for the changes to take effect, it says). Finally, restarting the computer an re-enabling the camera works with the camera functioning as it is intended (until its next real use).
Running a Zoom meeting in the app, the camera functioned just fine for about 37 minutes. Mid-meeting and mid-sharing my screen, the call froze, and the entire app had to be force closed. The light on the camera remained on. I tried to re-initiate the call multiple times in the app, but every time it insisted that I was already in a meeting, and gave me no options. I force closed the app again, finally re-joining in the Zoom in-browser version (Microsoft Edge), where I was told that that camera was in use by a different app. Camera Privacy Settings claims it was in use by the Zoom app, despite the app not being listed on my task manager (having been force closed). Several hours later, the light continues to be on, and the Camera Privacy Settings continue to insist that the camera is being used by the Zoom app. Disabling from the device manager results in exactly the same thing as disabling from the Camera Settings -- prompts you to restart in order for the changes to take effect. The light remains on.
No blue screen here, but the camera failing and getting stuck on (and causing other errors in other programs) seems to be a similar trend. There's something causing this camera to get stuck "on", and the only way to reset it is with a full computer restart.
If you have local admin rights if you disable and then enable the camera in the device manager you can get it working without a reboot. Not a permanent solution but saves you from rebooting.
If I don't use Windows Hello, the camera is more stable, but still has a potential to not work time to time, so have to restart it. If I use Windows Hello, for sure it will not even last 1 day. I bought this device thinking its Microsoft so they must be able to integrate the hardware much better, but my Dell PC is far more stable with Windows Hello and the camera. The troubleshooting and hardware replacement are not fixing the issues, this is a software/hardware integation issue. Can we get Microsoft to pay a bit more attention to this problem please?
