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!

Anyone ? :)

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?

Had the same here except it was pushing 50% CPU and 25% RAM. An easier quicker fix is to just restart the service.

lx07 said:

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.

change the startup type from auto to manual it will then turn on if you click on an application that uses it what I think it goes to is windows remote but don't quote me on that.

gam3rk1d98 said:

change the startup type from auto to manual it will then turn on if you click on an application that uses it what I think it goes to is windows remote but don't quote me on that.

You are right - changing to "disabled" would be better than "manual" if you wanted to stop it starting.

It was 5 years ago I posted that though - I'm not sure if it is a problem any more.

I am having a problem with this service using CPU. Haven't nailed down exactly when it starts going off the rails, but I regularly have to kill the process. It's been an issue for a couple of years now.

I have canon MX870 and TS8360 printers. For scanning I use the MP Navigator Ex program, so I'm going to disable the service and see if that affects my printing and scanning with the 3rd party programs.