Windows 10: host process for Microsoft is using my camera!

this issue had happened with me now twice were the app uses my camera!so can i delete it? and why would it use my camera ? should I be afraid ?

:)

 

Driver host process timeout.

Hi,

The default timeout interval for the Driver host process is 60 seconds. If the driver couldn't respond as expected within this period, it's possible that the driver is outdated or incompatible with the operating system. We'll be able to provide the appropriate
steps to resolve the timeout error once we have more information, so please answer these questions:

• Just to confirm, did this error only happen after you installed Fall Creators Update?
  
• What is the make and model of your device?
• Did you encounter this error while your computer was idle, or were you using a specific program?
• What troubleshooting steps have you done so far?

 

Boot Process

Hi,

Please suggest me a link that can explain the boot process step by step of ...

• Windows 7,
• Windows 8.1,
• Windows 10,
• Windows Server 2008 R2 and
• Windows Server 2012 R2

With Regards

InTech

 

Host processes for Windows tasks - stopped working

Hi, in reply to previous correspondents. I tried the Forum suggested by 'jdc1' and while there have been many viewers there is no suggestion of remedy - so far.
Searching further in this matter I find that a similar post also appears in this Forum - see here:
Host Process For Windows Tasks stopped working, Windows 10 1903
and once again many viewers but no remedy.
In Reliability Monitor there is a link to: How to report an error: I followed this link to Microsoft Community - see here:
https://answers.microsoft.com/en-us/...c-db4c1d0592f3
Where there are numerous complainants for this problem. There is one reply ( to-date) of a suggested solution by Microsoft which appears not to be the cure and quite a few more insistent*Devil posts for Microsoft to get this sorted.
The posts themselves include suggested cures like sfc/scannow and DISM which I like many others have tried to no avail. There seems to be a strong leaning towards blaming the 1903 update for this error. One person does indicate a solution which worked for him which is to via System & Storage to click the box to run now and remove earlier Windows Updates. I have just tried this myself and will report the result within the next few days.
Other correspondents are awaiting for further answers in the 'Community' from Microsoft.
So once again time will tell but it would appear that Microsoft are dragging their heels on this one.
Cheers.
.