Home network discovery not working after latest W10 Update

@ gogreen

I changed "function discovery resource publication" service" to Automatic from Manual and rebooted. It worked, the machine is now visible on the network, at least for now. This is at least the third time I made a change or installed updates that made discovery work on this machine. I got six other PC's with W10 that do not have this problem. Hopefully, it will stay fixed this time. Thanks for making me re-look at the fixes suggested along the way.

I still think there is something going on with systems that were updated when the original version of W10 was released. Like I have said before in this wandering thread, this is the only system that has the discovery problem and it is the only system that I did not do a fresh install of W10?!

I am a MS supporter, and have been for more years than I like to remember, but why are they treating us so badly with this problem? We deserve much better treatment than this, especially the Insiders who have done all this testing from Oct last year.

Networking used to work, updates stuffed it, MS must know what is wrong, particularly as users have led them to the real problem, yet they do nothing.

If it really is that hard to fix, the least they could do is tell us why and get us back on side. Their silence is, at best, bloody rude and at worst, downright arrogant.

Call me increasingly disenchanted as I now question whether I should still be encouraging people to move to win 10.

Ken429 said:

@ gogreen

I changed "function discovery resource publication" service" to Automatic from Manual and rebooted. It worked, the machine is now visible on the network, at least for now. This is at least the third time I made a change or installed updates that made discovery work on this machine. I got six other PC's with W10 that do not have this problem. Hopefully, it will stay fixed this time. Thanks for making me re-look at the fixes suggested along the way.

I still think there is something going on with systems that were updated when the original version of W10 was released. Like I have said before in this wandering thread, this is the only system that has the discovery problem and it is the only system that I did not do a fresh install of W10?!

Hi Ken. I have set mine to Auto too. I will check it tomorrow.

linw said:

I am a MS supporter, and have been for more years than I like to remember, but why are they treating us so badly with this problem? We deserve much better treatment than this, especially the Insiders who have done all this testing from Oct last year.

Networking used to work, updates stuffed it, MS must know what is wrong, particularly as users have led them to the real problem, yet they do nothing.

If it really is that hard to fix, the least they could do is tell us why and get us back on side. Their silence is, at best, bloody rude and at worst, downright arrogant.

Call me increasingly disenchanted as I now question whether I should still be encouraging people to move to win 10.

I wonder how wide spread this problem is. I have not seen much of anything posted elsewhere. Does Microsoft acknowledge that there is a problem?

Degrading the fixes posted here, the average computer-Joe isn't going to be able to fix this on his own.

Does anyone with "insider" Microsoft knowledge know if an update is coming soon to fix this? I can wait a little while longer for a fix - because I don't want to be mess'in around networking stuff I know nothing about. But I would like to be able to share files among my home-networked computers soon.

I searched couple weeks ago and found that some folks are having trouble with cisco vpn causing trouble with networking. They were having to return to their former os, uninstall vpn, then reupdate to get their problems fixed.

Thus far I have tried all the "fixes" listed in this thread with nothing helping thus far (have not tried reinstalling win 10 yet). I see some units one my main rig but other units on other units. Nothing really in a pattern. One unit is invisible everywhere as well as one of my network drives.

CountryBumkin said:

I wonder how wide spread this problem is. I have not seen much of anything posted elsewhere. Does Microsoft acknowledge that there is a problem?

Degrading the fixes posted here, the average computer-Joe isn't going to be able to fix this on his own.

Does anyone with "insider" Microsoft knowledge know if an update is coming soon to fix this? I can wait a little while longer for a fix - because I don't want to be mess'in around networking stuff I know nothing about. But I would like to be able to share files among my home-networked computers soon.

Have a look here; http://answers.microsoft.com/en-us/w...b-07441864d59f

Look for posts by Dusty Harper [MSFT]

eLPuSHeR said:

Hi Ken. I have set mine to Auto too. I will check it tomorrow.

Setting that service to Auto mode did nothing for me. I think it was already started even if set to Manual as defaults. I have been tinkering with the nVidia Ethernet controller and I can see now the other pc by disabling both Priority and VLAN. It's slow as hell to access though (100035 error I think).

Now I have all 4 comps able to see and access shares between each other. Yesterday, one wasn't showing, even to itself, but today it is fine! Go figure. In this state, all comps have the error 1231 with the net view command, thus showing a problem still exists.

So, just the Linux based Mybooklive NAS is MIA. This will show if SMB2 is disabled on the PC thus forcing SMB1, but this stuffs up comp shares.

At least I can add the NAS shares into Quick access so this gets around the SMB version problem.

And, yes, I have been through all the suggestions made by Dusty Harper and others but none of these fixes the SMB problem. That still needs a MS fix as I can't fiddle with the SMB version on the NAS. And, in any event, big laugh if these checks are expected to be done by the masses!!

Not sure I really know why but my problem machine has been visible on the network for several days and made it through the latest Thursday update cycle! My other problem machine got a fresh Win10 install and it too seems ok for now. Good things happen to those who wait and/or do a fresh install!