When I looked in my update history, it had a list of five updates identified by nothing more than a KB number. I rolled all five of them back. The camera is working again.
So what this tells me is that Microsoft Windows updates is breaking cameras. But this is not a fix because this means I can't roll forward with Windows updates. I'm not really technically enough to know how to find out which one of them broke it.
Did you roll back the updates one by one, rebooting after each rollback, and then testing the camera? If so, that would identify which update (KB???????) caused the problem with the camera. That would be helpful for Microsoft. In my case, I use Norton Driver Updater, a feature of Norton 360 with Lifelock. I was able to see when the camera drivers were updated and roll back to the previous versions of the Camera Detect and AVStream drivers. The former interfaces with a device by a third-party supplier of the camera for my Samsung Galaxy Book 3 Pro 360 laptop. The latter interfaces with the camera itself. Rolling back just the Camera Detect driver allowed the camera to be detected, but the latter restored video processing.
Also, check under Privacy & Security Settings. I don't know when Microsoft added a control feature for the camera but there is a setting (often controlled by a function key) to control the microphone and camera. The default setting is disabled. Perhaps, an update brought that feature in and by default the microphone and camera were disabled.