Thank you for reporting the issue. A fix is available through Windows Update. For more information about updates for your Surface available through Windows Update see the Surface Pro 8 update history page.
Surface Pro 8 camera issues; have to constantly disable and re-enable camera driver to get it to work
I've had an on-going issue with my surface pro 8 since I first got it about 20 months ago. The camera will stop working, light will stay on. This happens quite frequently, up to a few times per hour sporadically while using the camera. I've only really been bothered by this more recently as I've been using the camera more for work.
Both front and rear-facing cameras will cease working when this happens.
Disabling and re-enabling the camera driver solves the problem temporarily, making me think it's a driver issue. I've previously attempted to uninstall and install the latest drivers to no effect.
Thank you for your time in this matter.
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.
51 additional answers
Sort by: Most helpful
-
Anonymous
2024-03-14T16:17:36+00:00 Paste this into a .txt document and then save it as .bat
If you're going to put it on your taskbar (recommend), you'll need to shift+right click it, properties, shortcut, advanced, and ensure "Run as administrator" is checked.
I improved your batch file a bit so that you don't have to shift-right click. I find it a bit easier when using the device in tablet mode. Save it as a .bat file, double-click, and approve the admin prompt.
Batch script below:
@echo off if not "%1"=="am_admin" (powershell start -verb runas '%0' am_admin & exit /b) wmic path Win32_PnPEntity where "name='Intel(R) TGL AVStream Camera'" call disable wmic path Win32_PnPEntity where "name='Intel(R) TGL AVStream Camera'" call enable -
Anonymous
2024-03-05T08:10:26+00:00 Paste this into a .txt document and then save it as .bat
If you're going to put it on your taskbar (recommend), you'll need to shift+right click it, properties, shortcut, advanced, and ensure "Run as administrator" is checked.
wmic path Win32_PnPEntity where "name='Intel(R) TGL AVStream Camera'" call disable
wmic path Win32_PnPEntity where "name='Intel(R) TGL AVStream Camera'" call enable
I just tried manually disabling and re-enabling the camera in device manager and voila it works. (I got an error code for the first time today after facing the problem for over 2 months now (0*A00F420<Unknown>(08007001F)). Thank you for this. I have been facing the same problem, ditto how you have described it in the thread. I am a non-tech person and appreciate these simple to understand instructions. Talking to MS Support on the other hand is like talking to wall.
-
Anonymous
2024-02-29T21:29:39+00:00 Here's a link to the updated driver that I eventually found.
https://www.catalog.update.microsoft.com/Search.aspx?q=Intel(R)+AVStream+Camera
- Download the first item in the list.
- Go into File Explorer and double-click on the CAB file. (CAB is kind of like a ZIP file.)
- Copy all the files inside of the CAB file into a working folder.
- Go to Device Manager and update the driver, telling the driver update wizard to look in the working folder you created.
- Windows will update the driver.
I just did this, and now the driver version is showing 64.22000.13.14550, instead of 60. I haven't restarted my computer yet, or tested this driver yet, but this might be the answer. Good luck!
UPDATE: Now Windows cannot find my cameras at all. Doesn't matter how many times I restart, or whether I disable/re-enable. I'm going to have to roll-back the driver. A partially working camera is better than nothing at all.
UPDATE 2: I reinstalled Intel - Camera - 60.22000.5.12796. There are two of these in the list. This one is the one with the slightly larger file size. Camera works again, at least for now.
-
Anonymous
2024-01-19T09:18:49+00:00 Unfortunately, we all know it's a driver issue at play and the issue won't be fixed until Microsoft fix the driver. It sucks to be stuck like this, but in the meantime I've set up a script to disable and reenable the camera driver quickly so I don't have too much camera downtime... lol...