Windows 10 laptop cannot access network computers

I wish I had an answer for you. I have the same problem, as of upgrade to the latest BIG update. I do not see any of the computers on the network.

I have not tried to connect to my laptop with other computers, but I can connect to it on my phone.

This sounds a bit like earlier issues with discovery. BTW, the error you quoted is wrong. It is 80070035. Do a search here and you will find lots of hits!

Out of curiosity, what do you get with the command prompt command net view?
And has this Laptop been upgraded to win 10 rather than clean installed?

I see you have looked at SMB versions and I think this may be the problem. When your comp uses Lanman client to interrogate a Lanman server for its shares, it uses the SMB protocol. If your client and the server use different versions they can't talk to each other so your client times out and gives the 80070035 error, path not available.

I had this problem earlier and wrote this:-
"I have done a lot of checking of services etc between my comps to no avail. But today I was drawn to the registry settings of the Lanman Server. I compared the problem comp with a good one and after a while I found a discrepancy. The Registry entry, LanmanServer\Parameters had two extra keys that the good comps didn't have. These were 'Size' and 'SMB2'. I deleted both and was amazed to find that fixed the problem (gotta remember I have had a ton of disappointments!). The shares just popped up as they were supposed to!".

Those two keys were carryovers from earlier windows versions.

Path is HKLM\System\CurrentControlSet\Services\LanmanServer\Parameters. Check Lanman Client as well.

Can't say I can give you the fix but maybe this info will be helpful.

Hi, and thanks for taking the time to reply!
-Yes, it is an upgrade from w8.
-Typing net view in cmd (admin or not) returns error 50, not supported
-Yes, correct error code is 0x80070035 "Network path cant be found" (translated from Swedish)''
-I found the DWORD "Size" in LanmanServer but deleting that (and restarting) did not solve the problem. There were also other items in LanmanServer & LanmanWorkstation parameters folder that differed between the laptop(W10home,upgrade) and the tablet(W10Pro, clean install), but I did not dare to delete these without knowing what they do. Below is a list of items that differed between the laptop&tablet:

LanmanServer/Parameters:
In laptop (has problem) registry:
LmAnnounce,dword,1
Size,dword,1
SrvComment,SZ,*
*=COMPUTERNAME (name of my laptop)

In tablet(no problem) registry:
autodisconnect,dword,1

LanmanWorkstation/Parameters:
In laptop:
AllowInsecureGuestAuth,qword,1**
OtherDomains,Multi_SZ
**I added this both as Q/D word after a forum tip, made no difference

Googling that error 50 seems to point to network provider errors. My comp shows the ProviderOrder as RDPNP, LanmanWorkstation,webclient
Quote:-
Fixed.

I'm not sure how this occurred, but I thought I'd complete the thread in case anyone else finds themselves with a similar problem.

The issue was to do with the registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider

I compared the broken machine against a working one and found that the broken machine had:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\HwOrder]
"ProviderOrder"="LanmanWorks,RDPNP"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order]
"ProviderOrder"="LanmanWorks,RDPNP"

The Microsoft Windows Network is historically known as Lan Manager (or Lanman in shorthand), but I'd never seen it contracted to LanmanWorks. True enough, on a working machine these two key looked like:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\HwOrder]
"ProviderOrder"="LanmanWorkstation,RDPNP"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order]
"ProviderOrder"="LanmanWorkstation,RDPNP"

After a quick modification of the those values and a reboot, all is well.

Still perturbed as to how it happened. I'm sure curious techies break machine inadvertently all the time, but I can't imagine what level of playing around caused this particular modification.
end quote
------------------------------------------------

May have to seriously consider a clean install. Can you get a USB drive for backing up the laptop?

Thanks, I have the same ProviderOrder as you, so I guess it is correct. You are probably right in suggesting a clean install. I have a 64gb USB stick I can use to backup to my desktop or NAS. Restoring it will hopefully be faster via a working network. So annoying to have been spending so much time on this and still having to do a clean install of everything....
Thanks for your support!

No problems, mate.

A clean install is the way to go, now.

Let's know how you go.

Just to let you know, I made a clean install which solved the problem as expected. Thanks for your support!

Well done. There definitely comes a time for a clean install.

Cbeers.

See here the solution

Can see NAS but cannot access it or mapped shares after recent update - Windows 10 Forums