Yes, with no special software installed. However, I assume, that it will be fixed by today's firmware update.
Surface Pro 7 Front Camera Not Working
I'm not sure when it started, since I hadn't used the front camera on the device at all, but today I noticed in the Device manager that the "Surface Camera Front" has an error:
This device cannot start. (Code 10) STATUS_DEVICE_POWER_FAILURE.
Sure enough, upon opening the camera app, it acts as though I only have the back camera installed. I am predictably unable to bring up the front camera.
Is there possibly a driver issue, or is this a hardware flaw?
Thanks!
**Edit**: Problem persists through reboots, disable/reenable, troubleshooter, etc. Notably, I realized the front camera worked for at least the first hour that I had the device, since it shows you the camera feed when setting up Windows Hello.
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.
82 answers
Sort by: Oldest
-
Anonymous
2019-12-05T13:09:35+00:00 -
Barb Bowman 80,810 Reputation points MVP Volunteer Moderator2019-12-05T13:27:49+00:00 please let us know if this fixes your issue or not.
-
Anonymous
2020-01-22T13:45:50+00:00 I contacted tech support and they install the firmware. Still the front-facing camera isn't working on sign in....
-
Barb Bowman 80,810 Reputation points MVP Volunteer Moderator2020-01-22T14:52:14+00:00 You don't appear to be the same person who started this thread. Since we don't
know the history of your issue, suggest you first try an in place upgrade/repair
install - see
https://www.tenforums.com/tutorials/16397-repair-install-windows-10-place-upgrade.html
if this fails to resolve the problem, the last step before a hardware exchange
is to wipe and reimage from a downloadable recovery image
-
Anonymous
2020-03-21T23:44:58+00:00 I would like to reopen this thread. I have tried all of the above fixes (other than getting a warranty exchange) without a fix. Is this still a known issue without resolve?