Two machines updated to build 6584....Network discovery issues on one

Hi

I have a Main PC and then a NUC, both were fine after sorting out shares on Windows 24h2 build 4946. Both could see each other within discovery, map and share drives and files.

Both have now updated through WU to build 24h2 6584....



On the Main PC the NUC will no longer show within the "Network" screen BUT I can fully access the mapped drives and content. I can also type in its designation and access it....

For some reason the "Main" computer now shows in its own open Network Window, not the NUC though....



the above shows that I can still map the NUC from the MAIN, but I can no longer see it, but I can see MAIN.


When I RDC into the NUC, it works as expected......




Networks are noted as Private, discovery on, shares etc all set as they should be.

All the following are set to auto as services...

• Function Discovery Resource Publication
• Function Discovery Provider Host
• SSDP Discovery
• UPnP Device Host

and running.
I just can no longer see the NUC as I could earlier on today before both machines went and updated, from the MAIN PC. But now it shows itself.

Any ideas..?

Loathed to go too deep into this, in case I lose the access I have at the moment.

But it would be good and useful to see the NUC again within the Network Window show.

At times, more often these days, I dread Windows Updates.

Thanks.

EDIT: After a couple more reboots the Main PC doesn't seem to see itself within the Network Window but it also still does not see the awake and accessible NUC.

Resolved by removing KB506426 on both machines, this reverted each 24h2 build to 4946.

Having a search is seems some issues can be associated with that update.


Network discovery and functionality working as expected.

In my case my network issues were caused by my cloning the machines without sysprep'ing causing an SID clash

Thanks.

I had read a number of posts where that had been an issue.
Each of mine is a unique install.
A second NUC will arrive today, that will be formatted and a fresh insrall of 24h2 will be applied.

It seems that, in some circumstances, other issues can apply.
searching with that build number of Windows, or KB update would show that.

At least it was easy enough to roll back, this time.

It has somewhat changed now that all three machines have updated....

Another user within the Windows 10 forum, similar issue with their Sept update, upgrading from 10 to 11, and previous, where Network discovery does not see a PC. This is for me on Windows 11 with this 6584 update......




the above being via Network Discovery. It does not see itself "Main", as expected.


The one below is by creating my own folder and shortcuts, as suggested to create in that other forum............




the "missing" NUC Media Server can then be seen. It and its drives can be accessed there if needed. They can also be mapped without issues.

Network Discovery is on and all settings remain the same. Access is fine, machine pingable as it can have its content accessed and shared with no issues.
RDP into it and opening its own Network Discovery and it sees the other two fine.

It is what it is. for now. At least it works, just the one machine cannot be seen in ND, but still fully accessed, by the other two, as well as media devices that share the content from that server.

Amazing how the basic common sense "Don't fix it if it isn't broken" has never occurred to anyone at Microsoft.

If I open "Network" to show the computers etc that can be seen over it I do not see the NUC 3. BUT, if I type in \\NUC3 on the top address bar it will show the NUC 3 in the left column and, if I did it, show all of its shares. It just does not show up as a computer.....



as noted, it is fully accessible, drives can be mapped and content can be accessed. RDP to and from it is fine.
Network Discovery is turned on and checked for each machine. It remains to be that that one particular Windows 11 NUC cannot be seen by either of the other two under Network, but can be accessed.

BUT, whilst it does not show as a computer, I can share, and be seen above, its media, as media sharing is enabled.

I gave up on "Network Discovery" long ago. M.$ want's you to use their cloud instead of your LAN.

I now make shortcuts to the other computers on the LAN then pin the opened LAN destination to Quick Access.

Oddly, once the destination has been opened via the shortcut, it shows normally in the folder tree until you restart windows explorer.

Indeed, it seems so. Yes, I have noted it shows up within the Explorer tree, albeit not in the typical icon way within the discovery window. It is what it is.....it seems :)