Windows 10: Solved: Can't see other computers in Workgroup on Windows 10

** UPDATE **

Well this is strange. Turned off all the PC's. Then started them in a different order with my main Laptop that was one of the Win 7's originally.

Now on that Laptop. In File Explorer, I can see and access the other Win 7 Laptop and the Laptop that used to be Win 8.1. But now in both of those they can't see any of the other Laptops.

*Sad

This Threshold upgrade is becoming a real time burner now.

Really not cool also how MS changed App Defaults, Removed a program without notification, and changed a bunch of Settings.

The most valuable thing is your time. And our time is being wasted with this upgrade.

 

** UPDATE **

OK this is interesting now.

Turned Media Streaming to ON on all 3 Laptops.

Then turned all the Laptops off.

This time I started Laptop 3 first.

Now that other that was a former WIN 7 can see the other 2 Laptops in the Network.

ALL the Laptops can see the Media Devices in each. Plus all can see the big screen Samsung and the Samsung sees all of them.

So media streaming devices are all appearing perfectly in File Explorer.

So whichever Laptop gets turned on first can see the other PC's in the network, and then the Laptops turned on second or third can not see any of the others in File Explorer.

This is quite a bug.

Interesting also. Once I turn off the one started first that could see the entire network, neither of the either two get capability to see the other still when that goes off.

Anyone make sense of this with these observations??

 

Absolutely, I agree with you. This OS, in particular the build 1511 is a SHAME. SHAME for PRIVACY, SHAME for all.

Microsoft may have been redeemed by the CIA with the contract of patriot act !

 

I find a way...

Apparently the problem come from build 1511 because it use samba 3, so you have to disabled like that :

Command prompt / administrator and type two lines together like that :

sc.exe config lanmanworkstation depend= bowser/mrxsmb10/nsi
sc.exe config mrxsmb20 start= disabled

clic on enter

This run for me, I can see all my mapped PC now, windows XP, windows 10 and thresold


more infos : Synology Forum View topic - Windows 10 Version 1511 and SMB3

 

I fixed my sharing problem caused by the wrong SMB version in July.

Solved Network Shares not seen with MS account - Windows 10 Forums

Interesting to see how many others are affected with the SMB problem.

 

The problem I'm having is that my son gave my wife his old computer. So I upgraded it to win 10 a few days ago. My wife's old computer has win 7 and it connects fine with mine (win 10 pro 64-bit). I moved her files to one of my HDs so I could put them on the new one. But when I looked at the networks, hers only showed her computer and not mine. But I could see hers and mine from my computer. Then today I mapped drives to her computer to get to the files. I don't know why mine doesn't show up in the network folder, but I can map drives. It's been very frustrating getting this all worked out. The homegroup is just a joke. I couldn't get it working in win 7 and still can't in 10. I would rather have my computer showing up under networks, than having to map drives to connect her computer to mine. Her win 7 works with my win 10 computer.

 

This might be some help in figuring this problem out: I imaged my win10 installation (which was working fine before) to go onto a bigger hard drive. That is when this problem began for me.

When I started the services "function discovery provider host" and "function discovery resource publication" on each of the PCs not showing up, they immediately appeared, especially after "function discovery resource publication" is started. I set them to automatic. Works for me.

 

Open the services menu by clicking start and then clicking RUN and typing 'services.msc' and pressing enter.


Look for the following services in the list:

· DNS Client
· Function Discovery Provider Host
· Function Discovery Resource Publication
· Peer Networking Grouping
· HomeGroup Provider
· HomeGroup Listener
· SSDP Discovery
· UPnP Device Host

Make sure they are set to AUTOMATIC START instead of MANUAL.

Go down the list one by one and even if they are running do a mouse right click and SELECT "RESTART".

On the ones that are showing a blank and not running right click and SELECT "START".

That's all I did and all 3 Laptops are back in the Networking Panel and in the Homegroup WORKGROUP.

 

I can confirm this bug happens with a fresh install from the media creation tool (1511 build 10586 is back up again). I've done both the upgrade from an earlier WIN10 install and then a clean install on the same PC (after reformatting the drive). Both methods have this network issue. I played around with restarting the services that KRL listed and was able to access one of my WIN 8.1 machines but I can't get to all the other WIN10 machines with the 1511 update. I'll try setting the services to automatic on all of them (not sure why that's needed if all the services were running anyway).

 

After trying just about everything I could find to fix networking since 1511 update I found a help page at Microsoft.

http://windows.microsoft.com/en-us/w...nection-issues

Scroll down to step 6. Reinstall network devices using netcfg –d command

Notice that you must be running the 1511 update.

It helped with one of my computers, but the others are still network only when they feel like it.

 

I've found you have to turn on the PC which was the creator of the Homegroup FIRST while the others are turned off. Then turn on the others one by one in sequence. For some reason that fills the Homegroup panel correctly with every PC on the Network showing.

 

See here. Cannot connect to CIFS / SMB / Samba Network Shares Shared Folders in Windows 10 after update 1511/10586

Looks like a SMB version problem. The reason it sometimes works is probably because you are working on the master browser.

 

I just tried that on one pc it allows me to see the pc and shared folders but now I don't have permission to access them.

 

As a follow-up to my last email. I'm not sure if it's completely true what I said about the problem existing on a fresh install of 1511.

On an upgraded PC, I restarted the services above (all running anyway) but never changed them to "automatic". I've restarted since then. When I use that PC (upgraded from the original WIN 10 to 1511) to access another upgraded PC on the network (and it actually lets me see and open the user folder), I'm seeing folders that don't seem typical to me. I see the folder with the user's name I'm also seeing a hidden folder called "default" but then, I see another folder called "default.migrated". I don't see the "public" folder. It seems maybe we're being pointed at the old folders that got migrated during the upgrade to 1511 (just a guess).

However when I use an upgraded computer to look at the PC with the fresh install, it is seeing all the shared public files. So the PC with the fresh install seems OK even though it can't see the files on the computers that have the 1511 upgrade (I have 2 upgraded to 1511, one with a fresh install of 1511 and one WIN8.1 machine). I can see both the WIN8.1 and the Fresh install of 1511 PCs from an upgraded PC but not vice versa.

This is a strange issue and lots of us have it.

 

One thing for sure now I have 0 network out of 4 PCs some they can see but nothing has permission even though it all has permission which renders win 10 network completely useless, MS really screwed the pooch on this one I can't believe how crappy it's been since release, I guess beta testing is if the pc turns on MS passes the os and goes into production. I just reset the pc tonight too and still no meaningful contact with the other towers it's like the network imploded on its' self and did the final death roll.