{"id":2803,"date":"2017-05-07T01:05:00","date_gmt":"2017-05-06T23:05:00","guid":{"rendered":"http:\/\/borncity.com\/win\/?p=2803"},"modified":"2022-06-23T20:58:16","modified_gmt":"2022-06-23T18:58:16","slug":"windows-10-version-1703-fix-for-network-printer-install-issue","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2017\/05\/07\/windows-10-version-1703-fix-for-network-printer-install-issue\/","title":{"rendered":"Windows 10 Version 1703: Fix for network printer install issue"},"content":{"rendered":"<p><img loading=\"lazy\" decoding=\"async\" style=\"float: left; margin: 0px 10px 0px 0px; display: inline\" src=\"http:\/\/www.borncity.com\/blog\/wp-content\/uploads\/2015\/01\/win102.jpg\" width=\"58\" align=\"left\" height=\"58\">[<a href=\"http:\/\/www.borncity.com\/blog\/2017\/05\/06\/windows-10-version-1703-netzwerkdrucker-nicht-installierbar\/\" target=\"_blank\" rel=\"noopener\">German<\/a>]User of Windows 10 Creators Update are facing probably a strange issue: In some scenarios network printer aren't installable. Printer setup won't find the device. Here are a few details and a workaround.<\/p>\n<p><!--more--><\/p>\n<h3>What's the problem?<\/h3>\n<p><img loading=\"lazy\" decoding=\"async\" alt=\"\" src=\"https:\/\/ssl-vg03.met.vgwort.de\/na\/20834456827d4fd5b60cdb97d5d6d077\" width=\"1\" height=\"1\">Windows 10 provides a printer install wizard to search for devices and add the appropriate drivers. In Windows 10 Creators Update (Version 1703) the wizard fails on machines, with less then 4 GB RAM. Setup for a network printer (a WSD device) didn't find the the device. The installation fails. <\/p>\n<blockquote>\n<p>WSD stands for Web Service for Devices, a Microsoft API to access devices (Printers, <a href=\"https:\/\/technet.microsoft.com\/de-de\/library\/dd871131(v=ws.11).aspx\" target=\"_blank\" rel=\"noopener\">Scanner<\/a>) within a network (<a href=\"https:\/\/en.wikipedia.org\/wiki\/Web_Services_for_Devices\" target=\"_blank\" rel=\"noopener\">see<\/a>).&nbsp; <\/p>\n<\/blockquote>\n<p>In previous Windows 10 version this issue doesn't exists. Microsoft has <a href=\"https:\/\/answers.microsoft.com\/en-us\/windows\/forum\/windows_10-hardware\/network-printers-may-fail-to-install-on-windows-10\/4bdca057-f72a-40f8-94e0-6827f813fa21\" target=\"_blank\" rel=\"noopener\">confirmed<\/a> this issue. <\/p>\n<blockquote>\n<p>When connecting a network printer (a WSD device) to a network with a PC that contains less than 4 GB of memory and is running Windows 10 Creators Update (version 1703), if I run the printer's setup software on the PC, the setup software fails to discover and install the printer. This problem did not exist prior to installing the Creators Update.<\/p>\n<\/blockquote>\n<p>They are investigating this issue and offers a workaround. Because the solution is a bit 'short' here are a few additional details. <\/p>\n<h3>How to fix this network printer install issue <\/h3>\n<p>Microsoft wrote within the MS Answers forum post: <em>Microsoft has confirmed a known issue that may prevent network printer software from discovering and installing the network printer on systems with low memory (&lt; 4GB). This is due to firewall hardening rules added in Windows 10 Version 1703. <\/em>To fix this, they suggest to run the required service within it's own process. Here are the steps:<\/p>\n<p>1. Enter <em>cmd <\/em>into the task bars search box, and wait, till the <em>Command prompt <\/em>search result entry is shown within the start menu.<\/p>\n<p>2. Right click the <em>Command prompt <\/em>search result and select the context menu command <em>Run as administrator<\/em>. Confirm UAC. <\/p>\n<p>3. Enter the command <em>sc config fdphost type=own<\/em> into the administrative command prompt windows and press the enter key.<\/p>\n<p>4. Restart Windows and try to install the network printer again. <\/p>\n<p>At this point a few background information. <em>fdphost <\/em>is a service (<a href=\"https:\/\/technet.microsoft.com\/de-de\/library\/cc727719(v=ws.10).aspx\" target=\"_blank\" rel=\"noopener\">Function Discovery Provider Host<\/a>) to detect network devices. Obviously this service has trouble to be executed in Windows 10 Version 1703, if memory runs low. The command used above uses the <em>sc <\/em>command to advise Windows, to execute the <em>fdphost<\/em> service within its own process (see also this <a href=\"https:\/\/technet.microsoft.com\/de-de\/library\/cc990290%28v=ws.10%29.aspx?f=255&amp;MSPPError=-2147217396\" target=\"_blank\" rel=\"noopener\">Technet article<\/a> and <a href=\"https:\/\/superuser.com\/questions\/860117\/isolate-hosted-service-svchost-exe-in-its-own-process\" target=\"_blank\" rel=\"noopener\">this discussion<\/a>). It seems, that isolating <em>fdphost <\/em>within it's own process, solves the issue \u2013 the network printer will be found via WSD, the installation should run successfully. <\/p>\n<p><strong>Similar articles<\/strong><br \/><a href=\"https:\/\/borncity.com\/win\/win10-wiki\/\">Win10 Wiki<\/a><br \/><a href=\"https:\/\/web.archive.org\/web\/20210512202711\/https:\/\/borncity.com\/win\/2016\/07\/06\/windows10-open-command-prompt-window-as-administrator\/\">Windows 10: Open command prompt window as administrator<\/a><br \/><a href=\"https:\/\/borncity.com\/win\/2016\/12\/31\/how-to-block-windows-10-updates\/\">How to block Windows 10 updates<\/a><br \/><a href=\"https:\/\/borncity.com\/win\/2016\/12\/24\/stop-windows-from-installing-updates-over-and-over-again\/\">Stop Windows from installing updates over and over again<\/a><br \/><a href=\"https:\/\/borncity.com\/win\/2016\/07\/05\/how-to-decode-windows-errors\/\">How to decode Windows errors?<br \/><\/a><a href=\"https:\/\/borncity.com\/win\/2016\/10\/15\/windows-10-analyze-upgrade-errors\/\">Windows 10: Analyze upgrade errors<br \/><\/a><a href=\"https:\/\/borncity.com\/win\/2016\/11\/29\/windows-how-to-decode-update-0x8024-errors\/\">Windows: How to decode update 0x8024\u2026. errors<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>[German]User of Windows 10 Creators Update are facing probably a strange issue: In some scenarios network printer aren't installable. Printer setup won't find the device. Here are a few details and a workaround.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[448,463,2],"tags":[821,820,598],"class_list":["post-2803","post","type-post","status-publish","format-standard","hentry","category-devices","category-issue","category-windows","tag-install-issue-fdphost","tag-network-printer","tag-windows-10-creators-update"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/2803","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=2803"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/2803\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=2803"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=2803"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=2803"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}