cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

MP990 has yellow exclamation mark in Device Manager

FishMan
Apprentice

Hi,

I have had this printer for a few years now, and it has performed perfectly fine.  I bought a new computer in January 2015 with Windows 8.1 Pro (x64) and connected the printer.  No problems.

I don't use it for scanning very often (about 1 or 2 times per month), and yesterday was one of the times I needed it.  I opened my scanning software, and the MP990 wasn't there.  To cut a long story short, I can print to the printer but I cannot scan from it - either by software on the PC, or by pressing the button on the printer.

I looked in Device manager, and the printer shows fine, but the Image Acquisition has the MP990 with a Yellow Exclamation mark.

I have tried:

1.  Uninstall ALL canon software, uninstall all canon drivers, laboriously go through the registry and delete all references, and delete all Canon folders on the PC.  Reboot PC and printer.

2.  Install latest drivers from Canon UK website and try again.

3.  Still a yellow exclamation mark, so repeat 1.

4.  Install latest drivers from Canon USA website and try again.

5.  Still a yellow exclamation mark, so repeat 1.

6.  Connect printer and let Windows find the correct drivers.

7.  Still a yellow exclamation mark.

Checked all services to make sure nothing was disabled that shouldn't be.

Checked GPEdit to see if scanning was disabled - No it isn't.

 

I have no viruses or malware (checked with 3 different AV progs and Spybot).

 

Can anyone suggest anything to try ?

 

Thanks,

Paul

 

 

1 REPLY 1

FishMan
Apprentice

Bump !

Also some extra info.  When selecting the MP990 "Properties" in the "Imaging Devices" of Device Manager, it gives the following:

Windows cannot start this hardware device because its configuration information (in the registry) is incomplete or damaged. (Code 19)

 

I have also run sfc /scannow and DISM many, many times.  sfc always returns "Corrupt files found and is unable to fix them".  Prior to the scanner problem, sfc used to come back clean.

 

In 5 days, there have been 178 people reading this.  Do they all have the same problem and are looking for an answer ?  or,

Do they have an answer but don't want to suggest it, as it seems too basic ?

I don't care! it may be the one thing I haven't tried.  Just reply with your idea - PLEASE.

 

Regards,

Paul

 

Avatar
Announcements