1803 breaks Canon Imageclass D530 laser printers

[Diggs]

The Canon D530 has worked perfectly for a customer (Windows version 1709) until 1803. Windows can see the D530 (USB connected) but cannot print under 1803. Downloaded driver for printing direct from Canon website for 64-bit Windows 10 also fails to do anything. I plug it into a two different 1709 machines and it takes right off. I plug it into two different 1803 machines and both fail. The "Update Driver" is greyed out in properties on 1803 so i can't do anything there. Arrrgggg!

 

[phaZed]

I have also had some issues with Canon drivers after the update... different model and a bit different error, but no workie anyways.

The drivers seemingly install via the Canon installer package but Windows reflects a 2006 MS driver (never actually gets updated) and Windows popped up a message saying the driver is incorrect for this version of Windows - or something along those lines.

 

[Diggs]

... but Windows reflects a 2006 MS driver (never actually gets updated) ...

Yep! Exactly -

I had a quick discussion with a low-level tech at Canon and they are oblivious at this point.

 

[phaZed]

Yep, Canon was unhelpful on my side as well. A client took his 'fixed' and updated computer back home and he couldn't get his Canon going... I remoted into it and I couldn't get it to go as well.. I thought maybe I botched the job somehow so I have him dropping the computer back off on the 21st (he's on business trip ATM)... I might be sending an email instead.

 

[Diggs]

Canon has a 3/1/18 date on the driver download on their website but I can't get it to install. It unpacks, runs then nothing.

https://www.usa.canon.com/internet/...er/d530/imageclass-d530#drivers_downloads_tab

 

[Dave 1973]

I have a Cannon MG 3022 shared by two PC's that were upgraded to 1803 this AM. Now neither PC will print wirelessly.

I got one to print as a wired printer. Both PC's printed fine on version 1709.

 

[GTP]

I'm presently having problems with Epson printers. It seems that they do not like 1803 at all.
Updating drivers does nothing, removing reinstalling does nothing.
Wireless printing fails on all of them, plugging them in gets some to print; others not.
Most of these printers are less than 2 years old, the rest up to 5 years old.
ALL worked perfectly under 1709.
Needless to say there are some very disgruntled end users and one ****** off Tech!

 

[mr m]

This might be worth a shot. I had a similar experience with the recently installed 1803 breaking an HP officejet laser. I could not print from any appl or windows self test for that matter. The print queue remained empty but I would get an error of 0x000007D1

All was well after I deleted this registry key: HKLM\SYSTEM\CURRENTCONTROLSET\CONTROL\PRINT\POSTSPUPGRADE

Check for that key, back it up, delete it and maybe you'll get lucky.

Every freaking Win 10 update is a journey into the Twilight Zone where time, space and reality all diverge.

 

[phaZed]

I never came back to this thread but I was able to get that printer working (The gist of it):

1. Go to C:WindowsSystem32spoolPrinters folder. You’ll need administratorprivileges to access this folder.
2. Delete everything from the Printers folder.
3. Go back to Services window, locate Print Spooler service, right click it and choose Start
   
   https://windowsreport.com/cant-remove-printer-windows-10/

Seems some of the printer software loses rights to access the registry keys... or something...

 

[GTP]

I never came back to this thread but I was able to get that printer working (The gist of it):

1. Go to C:WindowsSystem32spoolPrinters folder. You’ll need administratorprivileges to access this folder.
2. Delete everything from the Printers folder.
3. Go back to Services window, locate Print Spooler service, right click it and choose Start
   
   https://windowsreport.com/cant-remove-printer-windows-10/

Seems some of the printer software loses rights to access the registry keys... or something...

Thanks Aaron, this helped to solve a problem for me.

 

[TechPJC]

1803 broke many things...

 

[Sky-Knight]

Any Epson Scanner that uses EpsonScan is busted too, though apparently if you dig into c:\windows\system32\twain and find the EXE, and set it to run in XP SP3 compatibility mode it "works". I had to roll back...