Windows 10: Windows 10 camera app displays diffused image

Hi there,

It's a bit hard to explain but when I use my laptop's webcam e.g. for video chats, it looks like I'm using a portrait effect, like a photographer who would be using a scrim or someone who would be using a paintbrush effect to have a more flattering image.


Do you know if I can change this or is this done on purpose?


Many thanks for your help!

:)

 

Missing apps: Store, People, Photos, Games & Camera on upgrading to 10

Thanks for replying spunk. That's the 'alphabetical' list I was referring to, none of these apps are in that 'All apps' list. Any more suggestions?

 

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.

http://windows.microsoft.com/en-US/windows-8/camera-app-faq

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?