I am having the same issue. I've checked the privacy settings, firewall, anti-virus, updated to the newest version of Zoom, and updated the camera driver - this worked once for a few minutes when I tested it out in Zoom, but upon closing and re-opening Zoom, I'm back to square one.
Camera stops working after Windows Update AGAIN!
Anyone else have this happen- my camera stopped working after a Windows update, then there was an update to fix that and it worked until this most recent Windows software update now my
Windows for home | Windows 11 | Windows update
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.
6 answers
Sort by: Most helpful
-
Anonymous
2024-10-31T02:46:42+00:00 -
Anonymous
2025-01-29T11:53:14+00:00 For over a year now I have had issues with Windows updates and the built in camrea not working after the update. I would not mind so much but I have a mircrosoft Studio 2 device and it keeps happening.
Update camrea does not work after rebooting. Next update problem fixed, that is until the next update.
Why can't Microsoft fix this issue once and for all and at leaset do more testing on there updates before releasing them.
I guess I will now have to wait for them to release the next update to fix the camrea drivers not being loaded on bootup and being able to logon using face ID.
I do not think this depends on the device but more a Windows update problem as I have a Microsoft Studio 2 device, and the issue has been around for quite some time now.
-
Anonymous
2024-11-30T05:41:01+00:00 I had the same problem - turns out there was in my case a Dell driver update which didn't auto-update. Hope this helps
-
Anonymous
2024-11-30T02:56:54+00:00 Having the same problem on my brand new Dell XPS16 with OC02C10 camera!! C'mon Windows. Dell isnt exactly an unknown brand.
-
Kapil Arya 37,826 Reputation points Volunteer Moderator2024-10-17T07:43:20+00:00 Try updating camera driver to latest version using Device Manager, see if it helps.