Windows 10: Can't access Windows shares after 1803 update Solved

Page 2 of 4 FirstFirst 1234 LastLast
  1.    03 Jul 2018 #11

    Hey Fixer,
    This is a real long shot ... Try manually accessing the network pc by \\pcname.local or network share by \\pcname.local\sharename

    Note: I was doing a test, see more here - Network Share \\PCNAME vs \\PCNAME.local - Windows 10 Forums
      My ComputersSystem Spec

  2.    03 Jul 2018 #12

    swaldman,

    You may also want to check out the following solution that has worked for me and a number of other TenForums users.

    Edit Hosts file to fix network issues after 1803 update
      My ComputerSystem Spec

  3.    03 Jul 2018 #13

    DrFrog said: View Post
    swaldman,

    You may also want to check out the following solution that has worked for me and a number of other TenForums users.

    Edit Hosts file to fix network issues after 1803 update
    Surely that won't help when even specifying the IP address of the target machine fails?
      My ComputerSystem Spec

  4.    03 Jul 2018 #14

    I ain't looking again at this until England v. Columbia is resolved.
      My ComputerSystem Spec

  5.    05 Jul 2018 #15

    swaldman said: View Post
    After quite a lot of wasted hours I found... maybe a solution, maybe more of a workaround, elseweb: turning off and on the association of File & Print Sharing with the network adapter on the target computer (the one whose share you're trying to connect to) appears to fix it. So far the fix has stuck for me, but others have reported it only lasting until the next reboot, or possibly (if on wifi) the next network change.

    Cycling this can be put in a Powershell script:

    Code:
    Disable-NetAdapterBinding -name "adaptername" -ComponentID ms_server
    Enable-NetAdapterBinding -name "adaptername" -ComponentID ms_server
    Needs to be run as Administrator.
    This is frustrating as I'd really like to test this. Unfortunately the inaccessible computer is running the 32 bit version of Win 10 Pro and PowerShell (Admin) errors when given the Get-NetAdapterBinding cmdlet.

    Might there be another way of disabling and re-enabling File and Printer Sharing, bearing in mind my knowledge of Powershell is, let's say, a bit limited? I don't mind having to get rough with it as I do have restorable images.
      My ComputerSystem Spec

  6.    05 Jul 2018 #16

    You can open Network and Internet in settings. Then click on Change adapter options. Right click your connection and click on properties. Then uncheck File and Printer Sharing for Microsoft Networks. Click OK and close it.(maybe reboot) Then go back and turn it back on:

    Click image for larger version. 

Name:	Screenshot_1.png 
Views:	42 
Size:	17.2 KB 
ID:	194607
      My ComputerSystem Spec

  7.    05 Jul 2018 #17

    Access Denied said: View Post
    You can open Network and Internet in settings. Then click on Change adapter options. Right click your connection and click on properties. Then uncheck File and Printer Sharing for Microsoft Networks. Click OK and close it.(maybe reboot) Then go back and turn it back on:

    Click image for larger version. 

Name:	Screenshot_1.png 
Views:	42 
Size:	17.2 KB 
ID:	194607
    No need to reboot, IME - just turn it off and on again. This is how I tested before finding it worked and automating it.
      My ComputerSystem Spec

  8.    05 Jul 2018 #18

    No good guys. Response has gone from initially showing the shared folders but hanging when folder access is requested, to now Windows cannot access <computername>. I may be wrong but the fact that Homegroup is still allowed in the firewall, and cannot be unchecked or deleted, looks the likely culprit to me. Maybe bits of Homegroup are still active in the 32 bit version. I'll see if I can turn Defender off and re-test.


    Late edit: turning firewall off does not change behaviour
    Last edited by Fixer; 05 Jul 2018 at 10:37. Reason: nnew information
      My ComputerSystem Spec

  9.    06 Jul 2018 #19

    Just restored the inaccessible system to v1709.16299. LAN working perfectly using File and Print sharing, Homegroup disabled. Currently it's updating itself to 1803. I'll let you know how it goes.
      My ComputerSystem Spec

  10.    06 Jul 2018 #20

    Upgrade to 1803 has caused exactly the same problem as before. I've restored 1709 again and blocked 1803.


    Important to note that this problem has only occurred on a 32 bit version of Win 10 running on a 64 bit machine. Two 64 bit versions on the same LAN have not had any problems.
    Last edited by Fixer; 06 Jul 2018 at 13:05. Reason: Clarification
      My ComputerSystem Spec


 
Page 2 of 4 FirstFirst 1234 LastLast

Related Threads
Feeling embarrassed to ask as I suspect this might be something really simple. Since updating to 1803 yesterday, I've lost access to all of my email accounts in the Windows Mail app. Every one says "System error" and "Can't get mail". Any...
Hi there I KNOW this must be a 1709 update -- I have several Windows machines with earlier releases than 1709 and they all work. With 1709 my NON Windows devices cannot access Windows shares even though they see the computer and can ping it....
Hi, I have set up a VPN on my server at home. I am not using a domain. I can ping IP's on the network I am connected to and access things like my router using a local IP address. I can't however access any of my mapped drives. I've tried...
My laptop ran a monster update for windows 10 a few days ago and since then I have not been able to connect to my Buffalo Linkstation on my wireless network. I connected to it just fine before and could connect on another laptop the other day that...
Cannot Access Windows Network Shares in Network and Sharing
Three machines: Surface Pro 4 - fully updated Surface Pro 3 - Windows 10, fully updated Lenovo X220T - Windows 8.1 Fully updated All three machines can see all available network devices, including each other. All three machines can...
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 05:48.
Find Us