Windows 10: CAMERA APP DOES NOT WORK?

i CANNOT GET MY CAMERA ONwIDWS 10 PC DESKTOP TO WORK?

:)

 

camera not working

If you have the camera connected to the computer, I would suggest that you disconnect the camera and then try to open the Camera app.



If the camera app opens, follow the steps below:

• Press “Windows key + C” from your keyboard to open “Charms bar”.
• Select “Settings” option.
• Select “Permissions” option.
• Turn on “Allow this app to access your: Webcam and Microphone” option.
• Lose the app by pressing “Alt key + F4” from your keyboard.
• Reopen the Camera app.
• Connect your camera and then check how this app works.

Goodluck!

 

WINDOWS 10 CAMERA APP NOT WORKING

Hi,

We appreciate your time and effort for getting back to us.

If you are referring to the Camera app then, I suggest you to uninstall the apps which came inbuilt with Windows 10 using Windows Powershell and reinstall using Windows Store. Follow the below steps:

• Open the Start menu, type Windows PowerShell in the
  search bar.
• Right click on the Windows PowerShell and select Run as administrator.
  
• Enter the below command to reinstall the Camera app.
  

get-appxpackage *Microsoft.WindowsCamera* | remove-appxpackage



After performing the above steps, install the Camera app form the Windows Store.

Reference: Refer to the following Microsoft article on
Camera app and webcams help.

How to use the Camera app - Microsoft Support

Note: The steps for Windows 8.1 applies to Windows 10.

Kindly let us know if you need any further assistance with Windows. We are glad to assist you.

Thank you.

 

download Windows camera app

Success in resetting Store; that produced a download of the Windows camera, despite seeing error message again, download proceeded. Screen shows MS app for Windows camera and indicates downloaded. (Camera now listed in app list.) But when Launch was selected,
no action after screen with camera icon. Eventually message appeared " something went wrong: here is message code if needed: 0x400F4271>MediaCaptureFailedEvent>0xC00D3704. We seem to be moving ahead a step at a time. Next suggestion?