Microsoft, why does this have to be so freaking hard?

by Volker Weber

SharedScreenshot

There is a simple b/w Samsung laser printer on my network. I don't print often, but this little machine gets the job done. I can print via AirPrint from my iPhones, my iPads. It works with all the Macs and I made it work with every single Windows computer. It never worked out of the box, I always had to download a driver from Samsung and now HP. But I got it to work.

Not with the latest Surface Pro.

While I can still print from every single machine I have, Surface Pro insists on telling me it does not have a driver for this printer. Well, I also connected it via USB and then it works immediately. Not over the network, although it does spot the printer and identifies it correctly. But then it keeps telling me it does not have a driver, which, to be honest, it could have downloaded without asking me to go to Samsung and find it in the first place. This isn't rocket science. Apple can do it, on both macOS and iOS.

So what did I do until now? I dropped a PDF on OneDrive, opened it with the iPad Pro and printed it. Over AirPrint. Since I did not have time to nail this new challenge.

Comments

I wrote recently about the importance of degrading smoothly (though it was in a different context). One of the issues that Microsoft seems to have is the inability to recognize "I can't find a highly specific driver for this exact model of this device, but I'll bet this slightly earlier or more generic driver will work." Especially with printer drivers, this should be a no brainer, as they don't actually change that radically.

Ben Langhinrichs, 2019-01-19

Ich muss meinem Yoga Tablet auch gefühlt alle drei Monate den Samsung Drucker neu installieren.

Robert Treuenfels, 2019-01-19

Doing the same fir different reasons. My personal devices print all nicely on my Brother MFC, but I am not admin on my work computer, so I can't install the driver. I would also bet that Windows actually includes a generic driver that is perfectly good enough for the basics. But I simply cannot use it...

Ragnar Schierholz, 2019-01-19

"In March 2002, Apple Inc. adopted CUPS as the printing system for Mac OS X 10.2.[5] In February 2007, Apple Inc. hired chief developer Michael Sweet and purchased the CUPS source code."
(https://en.wikipedia.org/wiki/CUPS)

Apple solved it by taking maintainership of CUPS and building it into OS X. Printing since then was problem-free for me at least....

With Microsofts current state of love-affair with open-source one would expect them to adopt cups as well?!

Daniel Kirstenpfad, 2019-01-19

You might want to try the Samsung Universal Print Driver 3, d/l from HP these days > https://ftp.hp.com/pub/softlib/software13/printers/SS/SL-M3370FD/SamsungUniversalPrintDriver3.exe

Thomas Cloer, 2019-01-19

Daniel, unless you upgrade the Mac to a new OS X version which drops support for color printing on your existing Deskjet. Yes, I have been there.

Volker Weber, 2019-01-19

Thomas, I did. As you can see the printer works with USB but not on the network. It's a network issue deep down in Windows that manifests itself in the printer problem. I can also not access my router in Edge, but I can in Firefox. It's just one of these convoluted problems that take forever to solve in Windows.

Volker Weber, 2019-01-19

Ah, I see. I have an older MFD from Samsung and the driver usually works fine for me when printing wirelessly (which I rarely do, to be honest).

Thomas Cloer, 2019-01-19

At least this Problem: "I can also not access my router in Edge" is a known issue (KB4480116) of the January Update: "After installing KB4480116, some users report that they cannot load a webpage in Microsoft Edge using a local IP address. Browsing fails or the webpage may become unresponsive."

https://support.microsoft.com/en-us/help/4480116/windows-10-update-kb4480116

Gerhard Heeke, 2019-01-19

Thank you, Gerhard. Brilliant hint. Workaround fixes Edge but not the printer issue. That apparently needs a fix from Microsoft.

Volker Weber, 2019-01-19

MS having some issues on useability:

My old Dell Latitude Laptop does not show the Windows 10 1809 Update. All other Updates for Windows 10 1803, Defender, Office, etc. show up and install without problems.
Except an HP printer driver. I don´t have or had any HP device.

MS says, there are no more blockers in the updating process.

So, when i still get no update: what is the reason?
It would be fine to have a user-readable message like: "you don't get the update because you have software x or hardware y installed."
With this information i could take steps to resolve the problem or just give up, if it is not solveable.

I could use the media creation tool to force an upgrade. But i just want to know what is wrong in my system.
I do not really need the upgdate. I´m just curious and MS is not helping.

Hans Giesers, 2019-01-20

@Volker Re workaround
Am I correct in thinking you tried you tested adding http://192.168.58.99 and this did not solve the problem?

Hypothesis: The protocols are separately filtered, and communication with printer happens over another port...

If adding exceptions to the trusted zone with the internet options is implemented by changing windows firewall settings, you may also get it working by adding an exception for the printer to the firewall settings.

Another hunch: I've had trouble accessing stuff on the local network in Windows when Windows viewed my newly added network adapter (as in I updated the driver and suddenly local network stuff is problematic) as being in a 'Public' network instead of a 'Private' network.

That problem is solved by telling Windows the current network is a 'Private' network.

Does this help?

Lars Berntrop-Bos, 2019-01-21

My first attempt was to disable the firewall completely, which did not change anything. I also made sure that Windows sees me on a private network.

I cannot really nail it down since a second Windows machine with the same configuration does not exhibit this behavior.

Volker Weber, 2019-01-21

Recent comments

Amy Blumenfield on Tools and Weapons #nowreading at 19:44
Horia Stanescu on You are famous on Botnet at 12:33
Volker Weber on You are famous on Botnet at 20:17
Dr. Kurt Glasner on You are famous on Botnet at 17:29
Mathias Ziolo on You are famous on Botnet at 14:12
Stephan Herz on You may secretly be a Bing user at 13:45
Volker Weber on Man stelle sich vor, es ist MWC, und keiner geht hin at 20:19
Andy Mell on Man stelle sich vor, es ist MWC, und keiner geht hin at 19:53
Volker Weber on You may secretly be a Bing user at 19:09
René Fischer on You may secretly be a Bing user at 19:02
Roland Dressler on Man stelle sich vor, es ist MWC, und keiner geht hin at 13:00
Tobias Müller on Man stelle sich vor, es ist MWC, und keiner geht hin at 09:22
Karl Heindel on Man stelle sich vor, es ist MWC, und keiner geht hin at 09:58
Bernhard Kockoth on Man stelle sich vor, es ist MWC, und keiner geht hin at 09:18
Jochen Kattoll on Surface Pro X vs Surface Pro 7 vs iPad Pro vs iPad at 16:56
Andreas Eldrich on Man stelle sich vor, es ist MWC, und keiner geht hin at 13:46
Armin Auth on Surface Pro X vs Surface Pro 7 vs iPad Pro vs iPad at 13:40
Markus Mews on Surface Pro X vs Surface Pro 7 vs iPad Pro vs iPad at 13:39
Andreas Eldrich on Man stelle sich vor, es ist MWC, und keiner geht hin at 13:30
Volker Weber on Surface Pro X vs Surface Pro 7 vs iPad Pro vs iPad at 12:44
Roland Dressler on Surface Pro X vs Surface Pro 7 vs iPad Pro vs iPad at 12:28
Volker Weber on Surface Pro X vs Surface Pro 7 vs iPad Pro vs iPad at 11:56
Roland Dressler on Surface Pro X vs Surface Pro 7 vs iPad Pro vs iPad at 11:46
Hanno Zulla on Surface Pro X vs Surface Pro 7 vs iPad Pro vs iPad at 11:28
Marco Schirmer on Surface Pro X :: Erste Eindrücke at 17:29

Ceci n'est pas un blog

I explain difficult concepts in simple ways. For free, and for money. Clue procurement and bullshit detection.

vowe

Contact
Publications
Stuff that works
Amazon Wish List
Frequently Asked Questions

rss feed  twitter  amazon

Local time is 19:38

visitors.gif

Paypal vowe