Windows 11 update 24H2 changes network access

Back into the fray. I am sharing Stan's frustration with MS. I have tried all the suggestions (and others in this thread) to no avail. I also tried switching FDResPub off and on again as you have suggested. No change. My local 24H2 machine (with W11 reinstalled) does not show itself or any other network device under Networks (Computer. (Except for a Synology NAS). But this machine and its shares are visible to all other 23H2 machines on the network which are working fine. Also, I can access other machines on the network from the problem 24H2 machine using network shares and mapping. So, the issue does not appear to be a restriction to access, but a problem with display in Explorer. Clearly, there is something(s) that needs to be changed having upgraded to 24H2. But I cannot find out what it is. Grateful to you for your efforts though. What I need to know from someone who has experienced this issue is what changes they made which solved the problem.

Why does not MS recognise this issue and resolve it?

Back into the fray. I am sharing Stan's frustration with MS. I have tried all the suggestions (and others in this thread) to no avail. I also tried switching FDResPub off and on again as you have suggested. No change. My local 24H2 machine (with W11 reinstalled) does not show itself or any other network device under Networks (Computer. (Except for a Synology NAS). But this machine and its shares are visible to all other 23H2 machines on the network which are working fine. Also, I can access other machines on the network from the problem 24H2 machine using network shares and mapping. So, the issue does not appear to be a restriction to access, but a problem with display in Explorer. Clearly, there is something(s) that needs to be changed having upgraded to 24H2. But I cannot find out what it is. Grateful to you for your efforts though. What I need to know from someone who has experienced this issue is what changes they made which solved the problem.

Why does not MS recognise this issue and resolve it?

Did you file an FBH report with your specific problems?

After the changes I described earlier, my machines are all fine now on the network, and I have a mix of 23H2 and 24H2 plus a windows 10 PC.

Some on public release Build and some with insider Builds.

Without looking at your specific configuration and settings, I cannot really know what you may have different that is causing your problems.

I see reports from different users describing different symptoms after they upgraded to 24H2.

I can only describe the issues that I had on my network and how I solved them for my home local network.

Sorry, that did not help your case. 🤷‍♂️

@GazzaGDBB,

Here is another difference I found on some machines with 24H2.

A) One 24H2 machine had this service set for Manual (Trigger Start) and the service never even started, it does not show Running.

Without the service Running the PC will not show up at all on the network on any PC.

B) This other 24H2 machine at the same Build level has this service set for Automatic (Trigger Start) and it shows Running.

The difference is:

A) In case A the PC will not show anywhere unless you start the service.

B) In case B the PC shows up on all the other PCs on the network but not on the local PC unless the service is restarted. 🤐😜🤷‍♂️

Anyway, looks like they have a bug when using Manual (Trigger Start) the trigger is not working and the service does not start. 🤬

Yes it is somewhere in that area as well as the Firewall Settings for File Sharing SMB in particlular.

YES it is in there somewhere. It starts and says running BUT after awhile although still running you no longer see your own PC. Stop and restart it and BAM all is good until it goes to sleep again. Also the Firewall SMB settings need to be tweaked for File and Printer Sharing.