Windows 10: Home network discovery not working after latest W10 Update

I'm able to get everything functioning only on whichever of my 3 laptops I turn on first. That one can then see the others in File Explorer. But the other 2 can't see the Network.

I was able to get Media Streaming displaying properly in all 3.

I was able to setup a new Homegroup also that works.

But there is a definite BUG in Networking and Sharing with the Threshold 2 upgrade. Probably related to the fact they did a lot of setting resets, deleted all incompatible software without telling you until after the upgrade what got deleted, changed a bunch of defaults back to MS apps, and they added a lot of new security features to protect the core.

Expect some headaches after this upgrade.

 

Probably no help to you but I have Windows 7 Ultimate in Hyper-V and also Windows 10 Pro.

The shares all show up in each PC and Homegroup works.

 

Consider yourself lucky!

 

Still trying to get the other physical PC to connect.

 

has same issue; my computer does not show up when clicking "network" on start menu (or anywhere else) used troubleshooter which recited "files missing" winsock corrupted googled it MS staff post suggested deleting winsock and reinstalling TCP/IP in properties
of ethernet adaptors; however, at last step got message "cannot reinstall these filed" permission needed. what a bunch of crap!
same thing happened on my husband's computer. had to role both back to build 10240 for either of us to see each other's computer on network (we share filed). neither could see our OWN computer in network, even though we had file sharing checked, and all "services" related to networking and peers on "automatic" and running. very frustrating. I could not even access my OWN FILES which are in my "public " shared folder. after rolling back, I had to COPY all files and put them in my "documents" folder as I was too afraid of not being able to access MY OWN FOLDERS. this update to 10586 is a DISASTER. It destroys, or corrupts WINSOCK files which messes up all networking for the entire network, and then does not allow you to "fix" it by reinstalling them (stupid "permissions" does not allow it).
It is a disaster. Network in XP and Win 7 was always breeze; why has MS fouled it up completely? why is MS not "fixing" this issue.
IT IS UNACCEPTABLE! NETWORKING IS THE "CORE" OF WINDOWS OPERATING SYSTEM. WITHOUT IT WE CANNOT FUNCTION!

 

nightmare. neither I nor my husband could see each other's computer on network or even our own computers in our own network folder! impossible to fix. troubleshooter recited it was "winsock" problem; MS staff posted workaround to DELETE winsock files and reinstall TCP/IP, what she DID NOT TELL you is after you go through her "steps" the final one to "reinstall" DOES NOT WORK. get error message "cannot reinstall" "blocked, not allowed, no permissions" now totally screwed as already deleted winsock; fortunately I set system restore before her "worthless workaround" which DID NOT WORK and could then see some computers but NOT my OWN desktop. we had to roll back to build 10240 as 10586 was a DISASTER. TOTALLY DESTROYED NETWORK FUNCTIONS!

We don't care about "cortana" and "bells and whistles" WE JUST WANT BASIC NETWORKING, like we had in XP, win 7, and win 8.1!
MS NEEDS TO STOP WORKING ON MORE BELLS AND WHISTLES AND MUST FIX THE BASIC CORE NETWORK DISASTERS IN 10586!

 

@ geekgirl - I'd be hesistant to delete winsock files like that. If you're go into core files, def make a full image backup of your hard drive first to an external HD. MS Restore is not 100% reliable to bring things back.

I'd recommend using proven reliable 3rd party software to do the image backups. I've been using Casper 8 for my full drive image backups and works flawlessly. Casper has been around for years.

Casper 8 is at Casper hard disk copying software provides complete PC backup protection | Future Systems Solutions

Other popular full image backup programs are:

• Macrium Reflect 6 at www.macrium.com/product/7/macrium-reflect-v6-home-edition.aspx


• AX64 is at Tour Product | AX64 Time Machine Snapshot Imaging Backup

 

thanks after we "rolled back" to build 10240 we got network back

 

beware of the MS staff suggested workaround; she did not TEST her workaround; after user deletes "winsock" user cannot "reinstall" TCP/IP as she claimed. her last step DID NOT WORK as it produced "error message" not allowed as "no permissions" to reinstall TCP/IP
I even tried "take ownership" of windows inf file; still got same error message. we had to roll back to 10240 to get our network back

then I tried to "UPGRADE" by downloading new 3 gig update to 10586. that FAILED at 32% just hung for hours; I had to force reboot
that resulted in an automatic roll back to 10240 which then restored our network and we could actually SEE our own public folders again
however, we still cannot "see" certain computers in the network folder which we could always see before. even the 10240 network is screwed up. MS needs to LISTEN TO USERS. stop devoting all their energy to 200 "new" bells and whistles we DO NOT NEED.
WHAT WE NEED IS RELIABLE NETWORKING OF OUR MULTIPLE HOME OR OFFICE COMPUTERS LIKE WE HAD IN XP,WIN 7, WIN 8.1

NETWORKING AND HOMEGROUP TOTALLY DISAPPEARED IN WIN 10 10856 AND THERE IS NO WAY TO JOIN IT, LEAVE IT, OR START A NEW HOMEGROUP. I THINK THIS IS WHAT IS CAUSING FAILURE IN COMPUTERS APPEARING IN NETWORK MAP. IT IS A DISASTER!
WITHOUT BASIC AND RELIABLE NETWORKING AND HOME GROUP THE ENTIRE OPERATING SYSTEM IS WORTHLESS!

 

I had to do a reset on my wife's laptop yesterday. It started throwing up GPO errors and duplicate .store errors every time she would do something. Along with clocking if she tried to open File Explorer.

I am just reinstalling Office 2013, Chrome and Nuance PDF on it and see how it runs with just that.

 

LOST FILE EXPLORER in first 10586 update on hubby machine; he could not navigate anywhere. UNUSABLE computer when you cannot open any folders on it; when we clicked on file explorer we got just a black screen. we had to roll back to 10240.
a few days later tried we 3 gig download from MS for 10586; file explorer worked this time, and we could navigate folders. but now he lost NETWORK and HOMEGROUP. they are both totally corrupt. he cannot even see his own machine or any files in his "public" folder, although he can see other folders. also, he could not join or leave Homegroup, or start new HG.
nothing but error messages on any attempt to join, leave, or start new homegroup. and absolute DISASTER in 10586.

our entire array of computers in homegroup disappeared. even after rolling back to 10240 no computers appeared in HG
we rolled back to 10240. we then tried a SECOND time to download 10586. it worked; explorer worked; network worked.
he saw his own computer in NW but only one other of 3 computers on and running on same network ethernet to router.
when all computers are ethernet to router there is no reason not to see all of them. they are all in same "workgroup"
on the "properties" folder so no reason not to see them all. after he rebooted he could not even see his own computer again. MS needs to FIX its CORRUPTION of NETWORK, WINSOCK, and HOMEGROUP or 10586 is WORTHLESS.
USERS NEED BASIC NETWORKING. IT WORKED FLAWLESSLY IN XP, WIN 7, WIN 8 AND WIN 8.1
THERE IS NO REASON WHY IS SHOULD NOT WORK IN WIN 10. (IN ALL BUILDS!)

 

I have given up on this new build. I did a CLEAN install on another HDD and still the same thing. I can view 3 computers when they are turned on but, the NAS and the 2 WD My Book Lives I have it does not and I have a Xerox Laser printer that it does not show up in the explorer. I have a PRIVATE network on all my machines and use a different IP address to what most people do and, while on the 10240 build, I have NO Issue but, on the Th2 update it is washed. I even have an Insider machine that has the latest 10586 insider build and it has same issues and has done since Insider build 10158. I have googled this and even tried MS help but, it appears they either do NOT know what it is OR, they simply don't care?

 

I have done the same, given up. Was thinking of trying a clean install but not any more. Thank's for the info!

 

Since mapping works ok for me I am able to work around, but its just a pain.

I am still hoping a fix will be found or MS will post update or something.

I have other things to get upset about so I will put this on the back burner for now.

 

Oh yeah, mapping and reaching by name works for me too. As for most of us. But it's not about that, it's about a crappy release without any real goodies. Bells and whistles, ha. It's about a knullande bad job. Hope your other problems can be solved, you can get rid of this one if you stick to the 10240 release.