Canon LiDE 120 Error message: "Cannot communicate with scanner for these reasons:"

[SimplyTev]

I've tried troubleshooting multiple times:

- Uninstalled and reinstalled drivers

- Returned and bought same model scanner

- Tried different drivers

- Tried different USB ports

My computer build is:

Intel i7 4770k

16GB 1866MHz RAM 

Asus Maximus Impact VI

nVidia GTX 780

Corsair RM550

Windows 8.1 64bit 

I don't know what I'm doing wrong. Anyone else get this? It's making me quite livid just trouble shooting it. I've read a lot of reviews on this on Amazon and other websites that says that this is plug and play for the most part. What am I doing wrong??

[andredutoit]

Just installed my LIDE 120 today, same problem on OSX El Capitan.  Looks like Canon is not doing anything about it, if I read this thread. I am going to try and return it to the supplier.

[w64bit]

Driver v1.02 is posted.

History:

[Ver.1.02]
- The scan error in the certain PC has been rectified.

Maybe this will fix the scanning errorfor good.

[digirambo]

Whoa! 5 consecutively successful scanning with the newest driver on W10 x64! Just the other day, I couldn't not get it to scan one picture! Thank you!

[FinnFellow]

I can confirm that this thread problem is fixed now, Win10 usb2&usb3, with newest Canoscan Lide -driver of 13 April, version 17.0.5 , so install it from Canon Support site and scanning works.

[ReneDenmark]

Well i guess i bought the scanner not knowing the problem so i will share it with my facebook friend 😞

This sux soz

[digirambo]

Problem is confirmed by a few users to be fixed with the latest drivers. I confirmed that it's working fine after the update as well.

[ReneDenmark]

Mine still not working after laste update and running in a usb 2.0 working maby every 10-15 time 1 time then the same stops at 10-15 % and error

[digirambo]

Are you running W10 x64? That's the OS I have and I am also using USB 2.0. I went through the same pain of trying and timing out or getting an error until the latest update. I haven't scanned more than 10 times since the last update, so I don't know if I was just getting lucky or not.

[ReneDenmark]

Same os  😞 same old problem 

[digirambo]

Oh boy... Thanks for the info.