Windows 10: Windows Image Acquisition process - high CPU usage

Hello,
from some reason, a process called "Windows Image Acquisition (WIA), which I've never seen before is running and using about 30% CPU.
I read in MSDN that "Windows Image Acquisition (WIA) is the still image acquisition platform in the Windows family of operating systems starting with Windows Millennium Edition (Windows Me) and Windows XP."

Does that mean that from some reason my laptop's camera is running now? Maybe my laptop was hacked?

Thanks!

:)

 

Why does Adobe Acrobat Pro continue to run as a background process with high CPU usage after app exit?

The background process uses about 30% of CPU. An additional background process is added every time a .pdf file is opened and exited. The high CPU usage causes the CPU cooling fan to run at high speed. I am able to end the processes manually using Task
Manager. The last added background process continues to run and use use about 30% of the CPU until stopping the process. The other background processes do not show CPU usage.

I am running Acrobat Pro 9 under Windows 10.

 

Windows 10 problems: high idle CPU usage and other failures

I too noticed this and wrote about it here:
Windows 10 High CPU Usage. If all goes well, it should quiet down once those processes finish (all of ours did).

 

As far as I know, you can disable the service, but I'm not sure how that will affect certain functions.

 

I have this service running on a clean install of Windows 10 - it is set to automatic.

Do you have a scanner or external camera you want to plug in? If not as a workaround you could stop it and set it to manual in services.msc. I just tested it and my built in webcam still works with it stopped.

 

Shut down and restarted my all-in-one printer and restarted it. WIA service stopped. Apparently it was involved in a scan service with my printer, though I haven't scanned in along time.

 

I noticed this service using 30% of my cpu as well. My Canon MP495 printer/scanner (which is connected via WiFi) had been turned off and powering it back up made the service return to 0% usage. Maybe WIA gets stuck in some loop looking for scanners that should be connected?