Z
Zoppl
Hey there,
after updating Win10 my internal camera (Crystal Eye Webcam) is hidden in the device manager and trying to open the camera in any app won't work. In the built-in Windows camera app the error "We can't find your camera 0xA00F4244 <NoCamerasAreAttached>" appears. Unfortunately I now can't recall which update concretely produces the error, since multiple updates automatically installed but it is either Securityupdate KB5000808 or KB5000908, feature Update 20H2 or Update Windows 1909 KB4023057 with cumulative updates KB50001028 & KB4601556.
Basically, Windows fails to regocnise the camera now. Before the update it worked well and I reproduced this error, using the "going back to older Windows builds" which made the camera work until the update installed automatically again. Now for some reason I cannot go back to a build when it was working. As I said, since there were multiple updates involved, I cannot name which update exactly it is, but one of them definitely triggers the error.
My next try will probably be to reset Windows but to hopefully avoid that I wanted to seek in this forum for help. Any kind of help would be highly appreciated.
Continue reading...
after updating Win10 my internal camera (Crystal Eye Webcam) is hidden in the device manager and trying to open the camera in any app won't work. In the built-in Windows camera app the error "We can't find your camera 0xA00F4244 <NoCamerasAreAttached>" appears. Unfortunately I now can't recall which update concretely produces the error, since multiple updates automatically installed but it is either Securityupdate KB5000808 or KB5000908, feature Update 20H2 or Update Windows 1909 KB4023057 with cumulative updates KB50001028 & KB4601556.
Basically, Windows fails to regocnise the camera now. Before the update it worked well and I reproduced this error, using the "going back to older Windows builds" which made the camera work until the update installed automatically again. Now for some reason I cannot go back to a build when it was working. As I said, since there were multiple updates involved, I cannot name which update exactly it is, but one of them definitely triggers the error.
My next try will probably be to reset Windows but to hopefully avoid that I wanted to seek in this forum for help. Any kind of help would be highly appreciated.
Continue reading...