Thank you for your feedback



How to Prevent TCP/IP to WSD Port Conversion After Upgrading to Windows 10

Document ID:HO3985

Usergroup :External
  Languages  
  Properties  

Problem

Queue port automatically converted; Printer queue conversion; Port changes;

Solution

What you will see


After upgrading a Windows 7 or Windows 8.1 operating system (OS) to Windows 10, all TCP/IP print queues are updated to Web Services Device (WSD).

NOTE: Windows 10 drivers may not be immediately available. In the meantime, you may use Windows 8 or 8.1 driver packages for Windows 10 supported printers.

 

Explanation


Print Driver Behavior

This is a Windows 10 operating system behavior designed by Microsoft. All TCP/IP queues for print drivers will be migrated to WSD queues if the OS detects that a WSD port is available; i.e., the connected device is WSD-capable. All custom driver settings are retained after port conversion.


Scan Driver Behavior

For a WIA scan driver connected over TCP/IP, two scan drivers will be available after the OS upgrade:

  • A WIA scan driver connected over TCP/IP port
  • A WSD scan driver connected over WSD port

 

Exceptions


The TCP/IP port will not be converted to WSD if more than one print queue (e.g., v3 or v4 drivers) is connected to the TCP/IP port during the OS upgrade.

 

Suggested remedy


To prevent port conversion from TCP/IP to WSD, create the following value in Windows 7 or 8.1 registry prior to upgrading to Windows 10. To do so:

To open the Registry Editor, click on Start > type regedit, and then click on Regedit.

Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\QueueMigration
Value: PreventOnUpgrade
Type: REG_DWORD
Data: 1 (or any value greater than 0)

NOTE: This value will be removed from the registry once it is processed and the upgrade is completed. Click here to view Microsoft's article for more information.

IMPORTANT! This procedure requires editing of the Windows registry. Editing the registry should be done by advanced users only. Incorrect use of Registry Editor can cause serious instability to the operating system. Lexmark is not responsible for incorrect use of Registry Editor.

 

Still need help?


If you need additional assistance, please close this window, go to your product's support page and locate  Get In Touch with Lexmark! for contact information. NOTE: When calling for support, you will need your printer model/machine type and serial number (SN).

Please be near the products described in this article to expedite the support process and reduce call-back situations.

 



Link:
Please enter the email address you would like to send a copy of this page to.