printer install for TCP/IP but got WSD instead RRS feed

  • Question

  • I just got a bunch of new Dell Laptops and I'm connecting them to printers as I have done for decades. It seems someone broke printer set ups and wasted a lot of my time.

    We normally use static IPs to connect to our printers because it is stable and it has worked for decades, until today. I'm adding printers manually and explicitly indicate the static IP of the printer. But, WinX 1809 decided what I really want is a WSD connection instead! Really? Come on MS REALLY?  It is my experience that WSD type of connection only sometimes works and I need it to always work, instead. I also specified a specific printer driver but once again WinX 1809 connected a MS driver instead of the one I specified. Obey the human WinX! I don't care what MS thinks I want. I want what I want not what MS thinks I want!

    I have seen this now on 5 new laptops.

    This causes two printer instances to be created. One says there is no driver. If I delete that one, both disappear. I can reinstall these printers and the specific driver and maybe on the 4th try it will work. It does eventually work after wasting so much of my time.

    I want the old way back and quit breaking things, please. Stop wasting so much of my time! It should never take an hour to install a printer that does not even work. The old way took just minutes and worked very well. How can this be progress?

    Thanks in advance for any work-arounds for this new issue.


    Tuesday, April 23, 2019 3:17 PM

All replies

  • Hi Kurt,

    I used to be a helpdesk, I like classic TCP/IP printer install method in XP and Win7, for Windows 10, this is my method:

    1.Disable in Windows 10 "Let Windows manage my default printer".

    2.Removing the following registry key and restarting Print Spooler. This will disable the WSD Port Monitor.

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors\WSD Port

    Reference case: WSD port delete


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact

    Wednesday, April 24, 2019 1:58 AM
  • One more thing

    System > Advanced System Settings > Hardware (Tab) > Device Installation Settings > NO(your device might not work as expected)

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact

    Wednesday, April 24, 2019 1:59 AM
  • Thanks for the reference. I'll look into this option. I"m wondering if there is a gpo solution as well.

    I am amazed that MS continues to ignore the needs for the front line folks that keep domains working well. Why do they hate us so much? It seems they go out of the way to make our lives HELL on earth. The MS QA, which seems to no longer exist, are just as bad as the developers for not stopping defects getting out to the public.


    Wednesday, April 24, 2019 3:17 PM
  • I deployed 7 of 9 new laptops and found #7's results very interesting. I added one printer using it's static IP and it failed again with two installed WSD instances, one of which has no driver, BUT it also added 6 other printers without any input from me, none of which were my target printer! When I deleted the driverless target printer, this time the instance with a driver did not also delete. I did have to manually add the port and then check the static IP.

    Well done MS! Miracles do happen.

    I deleted all of the false target printers and I got lucky. The one targeted printer worked correctly on only the second try. In some cases I have had to install the same printer 5 times for it to finally work as advertised.

    I'm all for adding new methods such as WSD, but new methods must never interfere with established and working protocols. If MS had a meaningfull QA program this would have never made it out into the wild. Millions of deployment folks would not be wasting so much valuable time. Maybe it is time to have a big I'm sorry I'm so greedy party on one of the worlds largest yachts, or at least the top 3 largest. Call it a "I don't have a QA but I own three very large boats" party. Invite all the virtual slaves whose time was needlessly wasted. In my case all this valuable wasted time was at our taxpayers expense. I hate greed.

    Thursday, April 25, 2019 12:03 PM
  • We are now having a second department in our government on different vlans with loss of printer issues. They worked for years and now suddenly stop working via WSD connections.

    We originally set them up with static IPs. This suggest that a recent MS patch is causing this new issue.

    These are all WinX instances.

    I am not alone. Thanks Microsoft (NOT)

    Monday, May 20, 2019 6:34 PM
  • I have a private client, a Best Western motel with 5 Windows Ten PCs in a workgroup. They have a front desk printer and a back office MFP. I told WinX to NOT manage my printers. I added the printers using the static IP but WinX keeps reverting back to WSD connections, which have a low probability of actually working. I keep setting them back to static IP. I keep getting paid for doing the same work over and over. The owner is unhappy with WinX over riding my work. I don't blame him.

    We have a new issue to report today. This same property is now reporting that after I set the default printer to front desk, WinX keeps changing the default printer to the back office, which causes a lot of frustration for the poor workers!!! The group login for all users is non-admin. They all share the same login.

    Why is the new and improved printer management in WinX so terrible? How do I stop this madness?



    Tuesday, September 17, 2019 7:26 PM
  • On the printers we use (Xerox), WSD is a service advertised on the printer and can be disabled.  If it's disabled on the printer, Windows won't use it.  Maybe check if your printers have such an option.  There's no on/off switch for WSD in Windows, and anything related to it is tied into other things that may be bad to disable.  You could try blocking WSD traffic on the Windows firewall.  For the record, we use WSD and it doesn't seem to be a problem in our environment.

    You may want to review the settings for the computer that keeps changing the default printer.  I haven't run into that before, though I assume if a printer becomes unreachable the computer may pick a different printer.

    Thursday, September 19, 2019 12:01 AM