Can't access Windows shares after 1803 update

Eagle51 · 03 Jul 2018

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

DrFrog · 03 Jul 2018

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

swaldman · 03 Jul 2018

DrFrog said:

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?

Fixer · 03 Jul 2018

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

Fixer · 05 Jul 2018

swaldman said:

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.

Access Denied · 05 Jul 2018

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:

Attachment 194607

swaldman · 05 Jul 2018

Access Denied said:

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:

Attachment 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.

Fixer · 05 Jul 2018

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

Fixer · 06 Jul 2018

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.

Fixer · 06 Jul 2018

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.