MY CAMERA NOT WORKING
Camera app shows error "0xA00F4244 NoCamerasAreAttached"
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.
223 answers
Sort by: Newest
-
Anonymous
2024-10-18T15:46:42+00:00 -
Anonymous
2024-10-17T18:22:46+00:00 Dan, this is great detective work.
I have an old Dell Latt 3440 and Windows 10 OS.........it works very well but internal camera suffers from same CAMERANOTFOUND and error code as above.
I get that Windows supplies the drivers and not Dell.
But how do I find and revert the 64 driver numbers to the 63 that you have discovered work?
Kind regards
Simon
Simon,
It was easy for me because I use Norton 365 with Lifelock and that anti-virus and fraud detection package includes Norton Driver Updater. When my camera gave me the error code, I checked which drivers had been recently updated. Since the first error was that the camera could not be detected, I reverted that driver using Norton Driver Updater. But, then the video could not be processed even though the camera was detected, so I reverted the AVStream driver. Both drivers are now marked "Skip" in Norton Driver Updater so they won't be updated.
I just found this site that may provide you with a source for the drivers:
https://www.catalog.update.microsoft.com/home.aspx
I recommend minimizing your browser view so you can see all the entries on a page. Enter one of the numbers below to locate a driver.
63.22000.0.12 for the good Camera Sensor driver
63.22000.3.12997 for the good AVStream driver
64.22000.0.10 for the bad Camera Sensor driver
64.25982.13.15388 for the bad AVStream driver
The good Camera Sensor driver was part of "Windows 11 Client, version 22H2 and later, Servicing Drivers, Windows 11 Client, version 22H2 and later, Upgrade & Servicing Drivers", released January 2023.
The good AVStream driver was part of "Windows 11 Client, version 22H2 and later, Servicing Drivers", released in July 2023.
The bad Camera Sensor driver was part of "Windows 11 Client, version 22H2 and later, Servicing Drivers, Windows 11 Client, version 22H2 and later, Upgrade & Servicing Drivers", released October 2023.
I could not locate the bad AVStream driver. I did locate a newer version 64.26100.13.16470 as part of "Windows 11 Client, version 22H2 and later, Servicing Drivers, Windows 11 Client, version 22H2 and later, Upgrade & Servicing Drivers", released June 2024, but buyer beware.
You can download the CAB files for the good drivers, but I cannot guarantee you won't end up with other issues. I have found that Microsoft will sometimes flag attempts to revert to an older version of something. Norton Driver Updater probably overrides the warning to revert drivers.
My laptop is presently at 23H2 and I cannot wait for 24H2 to come out...NOT! I've turned off automatic updates. From what I'm seeing online, 24H2 can brick some systems.
-
Anonymous
2024-10-17T16:41:35+00:00 me too, same problem. please reply if you manage to fix
-
Anonymous
2024-10-17T16:09:27+00:00 How do I resolve this camera issue? Camera app shows error "0xA00F4244 NoCamerasAreAttached"
plese help
-
Anonymous
2024-10-17T15:38:19+00:00 Dan, this is great detective work.
I have an old Dell Latt 3440 and Windows 10 OS.........it works very well but internal camera suffers from same CAMERANOTFOUND and error code as above.
I get that Windows supplies the drivers and not Dell.
But how do I find and revert the 64 driver numbers to the 63 that you have discovered work?
Kind regards
Simon