The problem could be due to an antivirus program. I had to turn off the camera settings in Bitdefender, so it might be a similar problem.
Surface pro 7 login says "Couldn't turn on the camera, please sign in with your pin"
Hi,
After the recent update on my Surface pro 7 Windows Hello Face not working and its saying "Couldn't turn on the camera, please sign in with your pin"
Surface | Surface Pro | Sound and camera
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.
60 answers
Sort by: Newest
-
Anonymous
2020-10-23T03:44:44+00:00 -
Anonymous
2020-10-22T16:07:53+00:00 So....does anyone else think it has gotten better. The Hello Face seems to working a lot more reliably. I didn't see any mention from MS on the subject.
Was there an update with a fix?
I finally got Microsoft to replace my device under warranty and still had the issue on the new one. But about 2 weeks ago it did start working more reliably.
-
Anonymous
2020-10-22T14:04:48+00:00 So....does anyone else think it has gotten better. The Hello Face seems to working a lot more reliably. I didn't see any mention from MS on the subject.
Was there an update with a fix?
-
Anonymous
2020-10-11T20:36:59+00:00 i have no applications installed on my surface pro as 100% of my work is on cloud, yet when i leave the tab for 30-40 minutes and try to login again using the hello sign in it get hangs and the camera will still be on (White light), after multiple updates on windows issue is resolved by 80% and happens now every 2-3 fldays instead of 4-5 times a day, which still an issue for me
-
Anonymous
2020-10-11T20:08:22+00:00 I am still having problems with the Windows Hello Face option mainly because frequently the two cameras are not activated on switch-on. In those circumstances if I revert to the Power Re-start option both cameras activate and log in works as it should. I have noticed that during the course of the day, the problem can re-occur. To summarize, it appears to be a boot-up problem with Windows. I wonder how many people have noticed this same problem?
Regards,
Renwick