Solved Windows 11 updates making home network invisible

Just in case anyone else has had this problem and you have a home network set up with windows 11 updates and you stop being able to see other machines on your network, but the network still pings ok. normally going into services and turning the function discovery on or off on would cure it making it re announce itself. This for me didnt work and although the network was ther via IP access seeing it in file explorer it was still missing. The cure i finally came up with was using a CLI command (you can make a new shortcut on desktop if you wantand just enter this) "C:\Windows\System32\cmd.exe /c "net stop fdrespub && net start fdrespub" && pause && exit". This so far has cured at least the last 4-5 times an update has messed up my network, running this on any of the affected machines brings back full visability. Not sure why doing the same thing in services doesnt work and this does ive not looked into. Hope this might help the odd few out there.

This problem has existed since Windows 10 Version 1709/1903. There seems to be no pattern to when any individual computer starts to suffer from it.
Your network has not become invisible. A fault in File explorer stops it displaying its Network section reliably.

Some people run an fdrespub solution at every boot.
Others stop using the File explorer, Network section and have a set of shortcuts to their shared folders which they use instead.


Denis

It has long been a suggestion to add lanmanworkstation as a dependency to the FDResPub service at startup to make devices more reliably show up in the network map. No need for any command or shortcuts.This has worked for many people, but not all. It is referenced all across the web. One such reference is

Do this on all systems in network.

add "LanmanWorkstation" as an additional startup dependency for the "Function Discovery Resource Publication" (FDResPub) service, which seems to do the trick. To do this, you simply open an elevated command prompt (i.e. use the "run as administrator" right-click context menu option to start cmd.exe), then execute the following command:

sc config fdrespub depend= RpcSs/http/fdphost/LanmanWorkstation

Reboot each device after executing this command, and the devices should see each other more reliably in Network and File Manager.

Thanks to all for adding their own solutions, and i will try them next time they are needed, but as someone has pointed out i have now added my fix as a statup item so i havent had the problem for some time now and it only started with win 11, also as you can probably see non of my machines should be running Windows 11 anyway but they do and are rock solid and my 2 main desktops both run at 4.1ghz and have done for many years without any breakdowns, overheating throttling, plus a quick question about the specta and meltdown vulnerability that do exist but from all my research ive not found anyone anywhere that has been attacked with either even MS cant tell of any. Was it just an excuse to slow older machines down to a usless speed so people purchase new hardware?

Hippytitimus said:

plus a quick question about the specta and meltdown vulnerability that do exist but from all my research ive not found anyone anywhere that has been attacked with either even MS cant tell of any.

Click to expand...

Likely not exploited because they were patched. But things like Meltdown and Spectre are huge deals in data centers, especially something like a multi-tenant data center. For home PCs, sure one process can get access to another's memory, but is that a big deal at home? Usually not.

Hippytitimus said:

Was it just an excuse to slow older machines down to a usless speed so people purchase new hardware?

Click to expand...

Yes, all conspiracy theories about selling new hardware are true.

pseymour said:

Likely not exploited because they were patched. But things like Meltdown and Spectre are huge deals in data centers, especially something like a multi-tenant data center. For home PCs, sure one process can get access to another's memory, but is that a big deal at home? Usually not.

Click to expand...

I have both the Spectre and Meltdown mitigations disabled on my X99 board. I've not checked in quite some time but there was a significant performance hit with SSD's running with them enabled.

Yes there was a lot of old machines that got slowed down to the point of being useless, unless the patch was disabled, and with the risk to home users being 99.99% exploited with it mine has been disabled since it was first introduced and i think it was just a caes of microsoft knowing it was possible but extreamly hard to impliment they decided to install the patch so it stopped anyone sueing them over it. as ive said my old x58 boards and i7s are still giving 4.1.ghz and can keep up with a lot of the newer systems available now. it aint broke so im not fixing it.

Hippytitimus said:

i think it was just a caes of microsoft knowing it was possible but extreamly hard to impliment they decided to install the patch so it stopped anyone sueing them over it.

Click to expand...

Were they also worried about the patches for Linux and macOS? What about the ones for Synology and Cisco?

Well on those i cant comment as ive only had fleeting useage of them, and ive stuck with window os, but as the patch was for the CPUs of intel and i think AMD, although i think they said AMD at the time wasnt affected until later, but today we are still using CPUs with the same vulnerability but now the mainboards are fitted with a chip (TPM) that effectivly does the job of the patch only quicker. and no doubt i will get corrected on that but that what this chat is for so if im wrong im wrong. but after years of disabling the patch and building many other machines since of varying specs, so far none have had any problems, except for the odd picnic errors that ive had to deal with.

Well you sort of missed the point. This isn't a Microsoft "thing," other than they're in a position to push microcode updates to Windows devices. There's nothing to sue over, and it affects more than just Windows.

I'm not sure what a TPM has to do with Spectre and Meltdown, other than as it pertains to keeping cryptographic keys hidden, but those two vulnerabilities are about more than what a TPM is used for. This thread is kind of all over the place; I'm going back to cat videos.

well i guess thats a good idea but cat videos? oh well, im off for now got some paint drying i need to check on.