Windows 1703 Update Problems Solved

  1.    #1

    Windows 1703 Update Problems

    I'll never learn! I either let Microsoft update my computers or I forced an update to 1703 on the others. I have seven computers running W10 1703 and thought everything looked ok...but it ain't. I stumbled into the networking problem when a did a fresh install on one of the systems because it refused to let the 1703 complete. I then discovered that I could not access my "Home Server" where I keep all the stuff I want to install on a fresh install of Windows. It was not in the network! Then I discovered several of the other systems did not have the server in the network. The problem went undetected by a "trusting user" because I had Mapped all the drives I routinely accessed on the server. Computers are missing from my home network on some computers and systems come and go on others. The "Map Network Drive" option is missing on some systems etc.,etc.

    It appears like I'm not the only one having problems:
    Anyone else notice the network issues with Windows 10 Creators edition?

    The above thread has many solutions that may or may not work. Has anybody come up with what needs to be done, short of MSFT fixing the problem or reverting the systems back to pre-1703, to get the network working. It's almost like the 8.1 initial networking bugs reappeared. Help would be appreciated.

    Now that things have settled down it appears I have one major problem. All of the computers on the home network are picked up and shown in the under Network in file manager. I can share the folders with these systems without any issues. However the "Home Server" is not shown. "Home Server" is just a Windows 10 system that I use to store common data. In order to use the Home Server Mapped drives on the other systems I had to use with my Windows Account Password. Never had to do that until I updated the Home Server to 1703. So it would seem when I updated the Home Server to 1703 I screwed something up that makes it invisible to all the systems and I had to log into the Servers Mapped drives with a different password! What the heck do I need to change on the Home Server system to get it working as part of the WorkGroup like it was before the 1703 update?

    More information: All of the systems that are recognized by file manager on my network are using either a Realtek or Intel network adapter EXCEPT the one that is not recognized. It is using a Killer network adapter on an ASRock Z97 Killer MB. I've tried updating to the latest Killer network driver but that had no effect. I don't know if that is my issue or not but it sure seems more than a coincidence. However, on the thread mentioned above there seems to be a multitude of issues that people are have with networking since installing 1703.

    Another piece of the puzzle: 1703 does not recognize my Z77 Extreme4 systems that have a Broadcom adapter! It looks like one of the posters on the thread above is right - go out and buy a bunch of Intel adapter cards and make 1703 happy!
    Last edited by Ken429; 25 May 2017 at 16:10.
      My ComputerSystem Spec


Related Threads
Hi , two days ago ( 2/5/2017) upgraded my windows 10 system from ver.1607 to ver.1703 , so called Creators update and immediately ran sfc /scannow ( no integrity violation ), DISM /Online /Cleanup-Image /ScanHealth ( component store repairable )...
I'm having problems upgrading my old laptop, which was happily running version 1607, to version 1703. Any ideas what I should try next? When I say "old" laptop... it came with XP, but has run Windows 8, 8.1, 10 Preview, and versions of Windows 10...
Source: New update options for Windows 10, version 1703 Windows for IT Pros
Hello, I'm running Windows 10 Pro Anniversary (1607) with Microsoft RSAT (Remote Server Administrative Tools) 1.2 which was a special "newer" version of these tools I needed when I upgraded from Windows 10 1511. I have the Windows 10 upgrade...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 01:33.
Find Us