Camera Problems

Anonymous
2021-01-01T06:31:53+00:00

I am running W10 on a Surface Pro (5th Gen). My Camera's driver is an Intel(R) AVStream Camera 2500 (30.15063.6.8611 - 12/3/2018) and Device Status: This device is working properly. My problem is my Microsoft Cameras, Front, IR Front and Rear (30.15063.6.8611

  • 12/3/2018), all saying: This device cannot start. (Code 10) STATUS_DEVICE_POWER_FAILURE. When trying to load my camera I get the error code: 0xA00F4244 <NoCamerasAreAttached> ~ I've researched online, went thru the tutorials, uninstalled/reinstalled...and still get the same results: error code: 0xA00F4244 <NoCamerasAreAttached>...suggestions?
Surface | Surface Pro | Sound and camera

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

44 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Barb Bowman 80,820 Reputation points MVP Volunteer Moderator
    2021-03-17T09:46:40+00:00

    I had this exact issue, and tried everything suggested in this community including a complete wipe and re-install on my Suface Pro 6.  Days of effort to no avail

    Question for you - before this issue occurred, did you ever run a third party driver utility like Driver Booster or even the Intel Support Assistant? Several others reported they did this and the issue started after doing so.  Did you use the downloadable recovery image to wipe and reinstall your SP6 and did you have this issue after using the recovery image or did you perform updates and then experience the issue?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2021-03-17T10:47:30+00:00

    Hi Barb - I've never used a 3rd party tool.  The issue happened after I updated to Windows10 Home 20H2 just over a week ago (OS Build: 19042.867)

    Yes I used the downloadable recovery image, and yes the camera issues were the same after doing so.  I then found the process above (I can't credit the original poster of it as have lost the thread) and it resolved it straight away

    Was this answer helpful?

    0 comments
  3. Anonymous
    2021-03-17T17:51:41+00:00

    S4MST3R

    ...nothing to lose (except time:), will give it a try!

    Thanks!

    Polo...

    Was this answer helpful?

    0 comments
  4. Anonymous
    2021-03-17T17:59:49+00:00

    This will work 100%.  I tried literally everything before this

    I created a doc with the seven drivers, dates and versions and did it step by step.  I’m not very technical and was over the moon when it worked.  Essentially, if you see a mismatch in those driver dates then that’s your issue

    Was this answer helpful?

    0 comments
  5. Anonymous
    2021-03-18T11:15:41+00:00

    Had the same Problem - either with Surface 5th Gen and new one - Try all suggested fixes which you can find on Google. Non of them worked. My guess it has something to do with the latest Win10 update - it's a shame that in Corona Times People using virtual communications massive Microsoft allowed such a bug!!! My last try is to complete reset win10 with an older version

    Was this answer helpful?

    0 comments