04-08-2014 10:37 PM
Add me to the list of people outraged by this. I use my MP610 about once a month at most, then when I turned it on the other day the dreaded U052 error. Consensus on best replacement printer brand? Canon what is the fix for this?
04-09-2014 09:52 AM
Add me to the growing list of unhappy customers. I printed a page yesterday on my MG5320. Went to print another page and computer said "Printer Offline" Sure enough it had powered off. When I turned it on, U0052. Jeez. Nothing I've tried has resolved the issue.
This has been a great printer and I'm a loyal fan. Cannot believe this is happening. Replacement head is $100-$130.
I'm in for class action .
04-09-2014 04:13 PM
I just got this error message on my MP610... was hoping for an easy fix, but it sounds like this doesn't exist. Argh... I use my printer all the time and really need a working photo printer!!
04-09-2014 06:11 PM
They acted very quick after the pms last week ... got a replacement printer today at my door .... of course I think its a downgraded model despite the larger model number, but I'll have to give it a try and see how it compares to the prior model.
04-11-2014 11:59 AM
Wow, here I thought this was an isolated incident. Add another dissatisfied CANON customer to the list! I have an MP600 thats worked flawlessly for years then it sat a few months without being used because I have another Canon printer we use. So, the printer ran out of ink so we bought 2 packs of 5 ink cartridges over $100.00 in cost just to find out my MP600 I was going to make buisness cards gave me the dreded "U052 Wrong Printhead Error". I notified Canon for help, some surprise there-not. I have tried the usual: power on and off, disconnect power cord, disconnect data cord, reset the printhead over and over and over, well you get the idea, cleaned printhead with warm water. All this to no avail. I hope Canon makes good on this. I work for the largest aircraft manufacture that make planes we all fly on, I will definiely let the IT division know about all the different Canon models with problems. I won't buy a new printhead because people in this forum are not having any luck with that but, I have one idea left to try and that is uninstall the the printer software and reinstall it without updating it and see if that will over ride the U052 code. How dumb is it where a code makes an all in one printer useless! Very unhappy.....camper.
04-11-2014 12:58 PM
I received my replacement printer 2 days ago and got it set up. I had an MX892 and the replacement is a MX922. I don't know what the differences are between the old and new printer other than the fact that the new printer uses DIFFERENT INK CARTRIDGES. The new printer did come with a set of new cartridges though so I just have some spares for the 892 that I will pass on.
I got the new printer setup and it seems to be working well. I'm hopeful that any software/hardware issues that were causing the U052 issue were resolved before the MX922 was made.
04-12-2014 04:36 PM
Same U052 message on my MP560 - no other previous issues. About a month ago I replaced several ink cartridges with Canon brand ink cartridges - printer was working fine after the replacements and then U052. Tried every solution suggested on other forums and on Canon's forum - multiple times - nothing has worked. Can't waste any more time on this issue.
For this printer, you spend $70 dollars to purchase a set of ink cartidges - for a $130 printer.
Off to buy another printer - will not be a Canon! CANON BUYERS BEWARE!
04-13-2014 01:54 AM
MP 600 After the message took out cartriges, printhead,cleaned reinserted, realigned, Was able to scan 2 items Then error message again Repeat procedure. over and over and over and over Nothing works!!! This is a computer failure, not a printhead problem. Has anyone replaced printhead or had help from Canon? I spent plenty on this and use lightly. Just bought expensive ink. Nothing works except camera card reader.
04-13-2014 01:59 AM
I'm sure they will try to blame it on the customer I am certain I did nothing unusualThere is no reason for this message. I think it is programmed to fail