Camera app shows error "0xA00F4244 NoCamerasAreAttached"

Reported
Anonymous
2024-03-24T00:28:08+00:00

How do I resolve this camera issue? Camera app shows error "0xA00F4244 NoCamerasAreAttached"

Windows for home | Windows 10 | Devices and drivers

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.

0 comments No comments

223 answers

Sort by: Oldest
  1. Anonymous
    2024-06-10T15:43:24+00:00

    I have tried all these before after checking on the Internet. None of these steps fixed the issue. When I newly got the laptop, the camera was working ok. Until after a week, I suspect there was an update that ran in the background. Most Windows updates often break something. I was hoping to roll back to the initial time I used the laptop without a camera issue but there is none and I don't want to reset my PC just because of this. There is no camera in my device manager. I even tried installing a camera driver from Windows but I'm still not seeing it. I'd done a couple of reboots, but the issue is still there.

    How to solve this iisue am also facing same

    0 comments No comments
  2. Anonymous
    2024-06-10T17:03:34+00:00

    I am facing the same issue. My Samsung Galaxy Book 3 Pro 360 (Model NP960QFG-KA1US) has a built-in camera that was working perfectly until it wasn't. I don't use it every day and I can only surmise that a Windows or Samsung update occurred that rendered it Camera Not Found. I also use Norton Driver Update, which periodically updates drivers when they are released to the public, so that too could be the culprit. Samsung could only offer to factory reset (which would destroy my apps and data) or send it to a service center (2-4 week turnaround), neither of which is acceptable. Microsoft Support did an in-place rebuild of Windows 11 but that did not correct the issue. I believe the issue may be that the camera device driver may be unique to Samsung, but they do not provide a link to download it. My next option to try is Best Buy Geek Squad since it is covered under a warranty. I received a notice from Samsung for a BIOS update before the camera failed, but thought nothing of it and allowed it to be updated. That is my current belief on what trashed the camera. My BIOS version is P07ALN. I don't know what it was before the BIOS update.

    0 comments No comments
  3. Anonymous
    2024-06-11T02:20:47+00:00

    SOLVED!

    I use Norton Driver Update to keep the device drivers current on my Samsung Galaxy Book 3 Pro 360. At least one of these two (2) device drivers got updated and caused the issue with CAMERA NOT FOUND. I suspect the first one, given the name of the driver, but since the camera is now working, I am afraid to update the second one to the latest version. If I determine the Intel(r) AVStream Camera driver is not the culprit, I will update this thread. For now, I am just pleased my camera is working again and it is not a hardware issue.

    1. Camera Sensor, 63.22000.0.12, January 5, 2023
    2. Intel(r) AVStream Camera, 63.22000.3.12997, July 2, 2023

    Microsoft Support had me do an in-place Windows 11 re-install that updated Windows 11 and all device drivers, but it did not solve the issue with CAMERA NOT FOUND.

    Samsung Support tried updating device drivers to the latest as well, but of course, they failed to correct the issue as well since the problem is with the current version of these device drivers. All they could recommend was sending the laptop back to a Samsung Service Center (2-4 weeks without a computer), or doing a factory reset which would wipe out all of my apps and data. They even offered me a $400 trade-in allowance to purchase a $1,800 Book 4 laptop.

    More information, the device driver versions that did NOT work are:

    1. Camera Sensor, 64.22000.0.10
    2. Intel(r) AVStream Camera, 64.25982.13.15387

    I may try reverting the Intel(r) AVStream Camera driver to the latest and if I do, I'll report the results.

    UPDATE:

    I reverted the Intel(r) AVStream Camera driver from the one that I know works, 63.22000.3.12997, to 64.25982.13.15387 and even to a newer version 64.25982.13.15637 April 14, 2024, and neither work. The camera is found, which is to say the original issue with CAMERA NOT FOUND is directly correlated to the Camera Sensor driver, as I suspected. By reverting the Camera Sensor driver to 63.22000.0.12, your camera will be found. The issue with the 64.25982.13.15387 and .15637 drivers is that the camera CANNOT BE STARTED. Now, it may be both drivers have to be of the 64.xxx series, but until Microsoft gets its act together to fix that series of drivers, stay with the following versions:

    1. Camera Sensor, 63.22000.0.12, January 5, 2023
    2. Intel(r) AVStream Camera, 63.22000.3.12997, July 2, 2023
    0 comments No comments
  4. Anonymous
    2024-06-11T11:18:07+00:00

    Troubleshoot Camera App error code 0xA00F4244

    0 comments No comments
  5. Anonymous
    2024-06-12T23:24:09+00:00

    This is how I fixed mine:

    Some laptops and other devices have a physical switch or button to turn the camera on or off. When the switch is off, Windows doesn't register the camera.

    Check your device for a camera switch or button and make sure it is switched on.

    0 comments No comments