Printing broken by June 2017 updates
-
@Dashrender said in Printing broken by June 2017 updates:
WTF makes printing so damned hard on Windows? Why is it such a problem child? What is happening in 'nix that makes it so much less problematic?
Next question - how many printers work with 'nix vs Windows? Can I go to BB or Staples and buy any printer on their shelf and make it work with 'nix? I know I can with Windows.
Drivers that are available from Microsoft works great. Its when using drivers from the vendors that causes headaches.
Most of the times using the generic pcl in Linux is all you need. Might have issues with certain copiers that has addition features requiring the exact driver.
-
That issue I have seen it mostly in Windows 7 although is affecting Windows 10. Uninstalling the update is the only way to go for now. See this post:
https://community.spiceworks.com/topic/2006071-kb17-06-ie-causing-browser-printing-problems -
On windows 10, using Chrome solved our problem.
-
MS has released a patch for Windows 7 for this problem.
-
MS admits there's a problem, but no fix for any version of Windows 10 yet.
-
@Dashrender Very good indeed.
-
Here's a fun one...
Prints fine from Excel, but not Outlook - Turns out it was just a single email that didn't print. Something weird in the coding.
I haven't tried to print from Korora yet. But likely should be fine as I have older HP printers....
-
@gjacobse said in Printing broken by June 2017 updates:
Here's a fun one...
Prints fine from Excel, but not Outlook - Turns out it was just a single email that didn't print. Something weird in the coding.
I haven't tried to print from Korora yet. But likely should be fine as I have older HP printers....
The problem is web something related, outlook often uses web interfaces, so I'm not surprised.
-
Has anyone had success with the fix?
-
@jt1001001 said in Printing broken by June 2017 updates:
Have not tried it yet.
-
@jt1001001 said in Printing broken by June 2017 updates:
Has anyone had success with the fix?
I don't have any Windows 7 machines to test on. I've read reports that Win 7 is fixed by this.
Still waiting for a fix on Win 10.
-
Microsoft released a new cumulative update last night that appears to address this for Windows 10
I haven't tested it yet.
This specific link is for version 1703
https://support.microsoft.com/en-us/help/4022716/windows-10-update-kb4022716
1607
https://support.microsoft.com/en-us/help/4022723/windows-10-update-kb4022723
1511
https://support.microsoft.com/en-us/help/4032693/windows-10-update-kb4032693
