Local computer not appearing in Explorer "Network" view under Windows 11

Question

Local computer not appearing in Explorer "Network" view under Windows 11

Gary Nebbett 6,216

Hello All,

Does anybody see the local computer in the list of computers in Explorer's "Network" view?

The reason that I am asking is that I think that I have discovered why it does not appear in my list and, if the idea is correct, I would not expect any Windows 11 system to show the local computer.

I think that there has been a long-term problem/bug in evaluating Windows Filtering Platform (WFP) filters for loopback traffic that had been disguised by default settings in Windows 10. A default has changed in Windows 11 and this has allowed the problem to become more visible.

The "missing" local computer is just an easily verifiable manifestation of the problem and not a big problem itself, but I think that some other problems that I have seen in forums might have the same root cause.

Update: I have written about the suspected problem and its causes in more detail at: https://gary-nebbett.blogspot.com/2022/04/windows-filtering-platform-loopback.html

Gary

@CmdrKeene 131 Reputation points

2022-04-09T20:13:21.283+00:00

Well I know I'm just a sample size of 1 person, but I checked here and I do not see my local PC in this view (I do see other computers on the same LAN). I do have network file sharing/discovery enabled and my network type is set to Private (simple home network).
Gary Nebbett 6,216 Reputation points

2022-04-09T20:44:44.013+00:00

Hello @@CmdrKeene ,

Thanks for the reply. I am retired, so I don't have access to a wide sample of systems to check this behaviour. I am writing an explanation of what I think that I have discovered and the techniques used to do so (essentially, detailed Event Tracing for Windows (ETW)). Replies like yours will influence the content of that explanation (e.g. how much room for doubt is there).

Gary
Dennis Enderson 0 Reputation points

2023-05-15T05:19:44.09+00:00

After many months of trial and error, I believe I have discovered a reliable workaround for this incredibly frustrating issue, and it was right in front of me all along. For the many years I have been using Microsoft peer-to-peer networking at home, going all the way back to the early versions of Windows, I have always made sure that all of my systems were assigned to the same workgroup. I recently updated my wife's desktop system to Windows 11, at which time it could "see itself" in the network folder. Following my old practice, I changed that system's workgroup to the same name as the other 3 computers, and it promptly disappeared from the network folder. Recalling that I had long experienced this problem with one of my other systems, I switched it to a different workgroup, and it reappeared in the network folder. Several back and forth experiments verified that this works every time. I hope this works for others experiencing the same problem. (By the way, this issue seems to occur only on systems connected to my router via WiFi. My Ethernet-connected desktop computer has never exhibited the problem.)
Anonymous

2023-06-04T13:43:27.94+00:00

How exactly (step-by-step) did you “switch it to a different workgroup”? Thanks.

6 answers

Your answer

@CmdrKeene 131 Reputation points

2022-04-09T20:13:21.283+00:00

Well I know I'm just a sample size of 1 person, but I checked here and I do not see my local PC in this view (I do see other computers on the same LAN). I do have network file sharing/discovery enabled and my network type is set to Private (simple home network).
Gary Nebbett 6,216 Reputation points

2022-04-09T20:44:44.013+00:00

Hello @@CmdrKeene ,

Thanks for the reply. I am retired, so I don't have access to a wide sample of systems to check this behaviour. I am writing an explanation of what I think that I have discovered and the techniques used to do so (essentially, detailed Event Tracing for Windows (ETW)). Replies like yours will influence the content of that explanation (e.g. how much room for doubt is there).

Gary
Dennis Enderson 0 Reputation points

2023-05-15T05:19:44.09+00:00

After many months of trial and error, I believe I have discovered a reliable workaround for this incredibly frustrating issue, and it was right in front of me all along. For the many years I have been using Microsoft peer-to-peer networking at home, going all the way back to the early versions of Windows, I have always made sure that all of my systems were assigned to the same workgroup. I recently updated my wife's desktop system to Windows 11, at which time it could "see itself" in the network folder. Following my old practice, I changed that system's workgroup to the same name as the other 3 computers, and it promptly disappeared from the network folder. Recalling that I had long experienced this problem with one of my other systems, I switched it to a different workgroup, and it reappeared in the network folder. Several back and forth experiments verified that this works every time. I hope this works for others experiencing the same problem. (By the way, this issue seems to occur only on systems connected to my router via WiFi. My Ethernet-connected desktop computer has never exhibited the problem.)
Anonymous

2023-06-04T13:43:27.94+00:00

How exactly (step-by-step) did you “switch it to a different workgroup”? Thanks.

Answer 1

F G 41

The only workaround that seems to make the local PC visible again is by doing these 2 commands.

This problem has been going on for years and MS never came up with a proper fix.

net stop FDResPub

net start FDResPub

Gary Nebbett 6,216 Reputation points

2023-08-10T07:06:16.63+00:00

Hello F G,

I wrote about this problem here: https://gary-nebbett.blogspot.com/2021/05/network-discovery-and-name-resolution.html

A workaround for the problem is to add a service dependency to the FDResPub service on the LanmanWorkstation service.

Gary
khisel 0 Reputation points

2023-08-10T22:12:01.2366667+00:00

This almost always works but its effect will not survive a reboot. Tried adding this as a batch file running periodically but the results were unsatisfying and fleeting. I just gave up since it's such a minor, non-critical issue. But it still bugs the you-know-what out of me.
Gary Nebbett 6,216 Reputation points

2023-08-11T10:59:15.3533333+00:00

Hello khisel,

Can you explain how/why an added service dependency (which updates the service definition in the registry) does not survive a reboot?

Gary
khisel 0 Reputation points

2023-08-15T19:31:35.34+00:00

Gary, I was responding to the "net stop FDResPub/net start FDResPub" message from F G. That works temporarily but not after a reboot. Sorry for the ambiguity.
Maksym Kovalchuk 5 Reputation points

2024-03-03T12:46:38.74+00:00

Oh my god, really just restarting this shit service is resolving the problem. Thank you man for help
Josh Russell 5 Reputation points

2024-03-03T12:52:42.62+00:00

You can toggle Network Discovery in the Sharing Settings as well and then refresh the Network File Explorer window. It usually requires the refresh.
Ken Culbert 0 Reputation points

2024-04-19T02:52:36.6566667+00:00

Took forever and a lot of pulling of hair to find this, but it worked.
Guilherme FC 0 Reputation points

2025-04-27T23:16:39.4966667+00:00

for the ones that dont want it to stop working after reboot, change the initialization type to automatic (default is manual).

The english name of this service is "Function Discovery Resource Publication"
Don Troesser 0 Reputation points

2025-06-21T23:25:45.5833333+00:00

OK, I've tried everything that everyone on the Internet came up with to fix this problem. Some didn't work, others did, but were only temporary. I even installed SMB 1. It worked all the time, but has some major security flaws so I removed it from my machine. Restarting FDResPub was the best solution. I even have a Task scheduled to run it for me, but alas, it wasn't something that consistently worked and stayed working all the while my PC was running all day. Even running the command //PCNAME didn't stick. And who wants to turn Network Discovery off and then on every time you reboot? It doesn't actually work anyways. I can't even remember all the other "solutions" I tried, and they all failed.

Bring on Gary Nebbett! So, I tried adding "LanmanWorkstation" to the dependencies for "FDResPub". Rebooted, and it didn't work. WTH!?!?! OK, I forgot that the Task to restart RDResRub was still enabled. I disabled the task, and rebooted once again. After refreshing File Explorer and checking the network drives, my machine and all the others on the network were there. SUCCESS!! It's only be working for a couple of hours now, but that's better than most. THANK YOU Gary!! And yes, it does survive a reboot!!

UPDATE!

So, it's the next day, and it appears that I may have spoken too soon yesterday regarding this solution. I started my machine this morning, and this afternoon I finally got around to checking to see if my PC still showed up in File Explorer under Network.

It did NOT!! Another failure.

I checked the registry, and "LanmanWorkstation" is still showing up as a dependency for "FDResPub". And once again, we were so close to a working solution, but alas...

The best solution would be for Microsoft to actually FIX the problem. There can't be thousands of people on the Internet looking for a solution to this problem if there isn't a problem with the Microsoft code somewhere. After all, we don't all have wonky PC's, so the only common denominator appears to be Windows 11.

MICROSOFT, FIX IT!!!
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Answer 2

Ali Kayn 25

I'm having this problem with a fresh implementation of Windows 11. The fastest fix I've found is : Settings, Network, Advanced Network, Advanced Sharing and just turn the Network Discovery option and the File and Printer Sharing option off and on. The PC will now be visible in Explorer. Turning an option off and on is an old trick.

Josh Russell 5 Reputation points

2024-02-20T05:18:02.49+00:00

Yeah this works for me. I find this issue might be more likely to happen if I start actively using my computer as soon as I turn it on and get into Windows rather than waiting a bit. Annoying. Because Sharing doesn't start working ever if you start using your computer too soon after booting and logging in.
jack johnson 0 Reputation points

2025-02-14T20:34:19.4+00:00

Thanks. I had not tried the off on trick but it did fix my concern.

Answer 3

Bonzer2u 5

FYI, I just stumbled upon an apparent fix with my new win11 pc not showing up in its own local file explorer 'network' folder by simply installing 'virtual machine platform' in windows features.

For whatever reason my local win11 PC and wireless networked printer/scanner have been showing up consistently ever since, go figure.... DOH!

Tested successfully with several reboots, YMMV...

Bonzer2u 5 Reputation points

2023-02-23T20:34:48.7666667+00:00

Unfortunately, this fix didn't hold long term. After coming out of sleep mode (laptop) or refreshing the network folder, both the local win11p computer and wireless networked printer disappeared again however, both devices reappear again after a reboot---> for awhile which is only better than not at all as before...

I run a simple private networked 'workgroup' with 3 windows pc's, 1-win11p and 2-win10p. Both of the win10p pc's see all networked devices fine, the only one with this issue is the new win11p pc.

This is basic networking 101 stuff MS, is anyone listening?
Gary Nebbett 6,216 Reputation points

2023-02-24T08:19:26.1066667+00:00

Hello Bonzer2u,

There is a link in my first message that leads to a more detailed description of the problem and includes a "pktmon" trace command. If you are prepared to perform that trace and share the captured data, then I would see if I can determine why the wireless printer/scanner is not appearing in the list of discovered devices.

Gary
Dale Hildestad 0 Reputation points

2023-03-27T17:42:03.16+00:00

I still had the problem WITH virtual machine, so I put in all features having ANYTHING to do with networking or support there of. First glance the problem is fixed. My old clunky Epson I use only for faxing/scanning anymore is gone most of the time, but sometimes appears. Probably a problem with the printer. Avoid Epson. Various nuisances will likely relegate any unit to trash or partial use. Printing is NEVER problem-free.
F G 41 Reputation points

2023-08-10T02:55:24.63+00:00

I tried that and it did not help.
andre1935 0 Reputation points

2024-05-31T08:34:31.7766667+00:00

No, does not work for me

Answer 4

Anonymous

Gary, some windows 7 and 2016 servers do show up on the only Windows 11 I have installed here, but the 11 box does not appear.

Edit: all I needed to do was change the public firewall profile to private and then it shows up.

Gary Nebbett 6,216 Reputation points

2022-04-10T08:34:47.083+00:00

Hello Dave,

Thanks for this feedback. It is not what I expected - the private profile is active on my PC and the local computer does not appear. My current understanding of what is happening on my PC also strongly suggests that the Windows Defender active profiles should have no impact on the behaviour.

I will write-up in detail a report on this topic and add an update to this thread when it is ready in case anyone wants to explore the behaviour on their own systems.

Gary
Anonymous

2022-04-10T13:07:12.203+00:00

I don't remember exact wording but on another 10 box when I did the same steps of turning on Network Discovery (Control Panel\Network and Internet\Network and Sharing Center\Advanced sharing settings) I got a notification that its blocked on Public profile and did I want to change to Private. So I went back to the 11 box and sure enough it was still OOB and on Public profile. As soon as I changed it to Private, it showed up in the net hood.
Gary Nebbett 6,216 Reputation points

2022-04-10T15:56:38.177+00:00

Hello Dave,

I have written about the problem in more detail at https://gary-nebbett.blogspot.com/2022/04/windows-filtering-platform-loopback.html which ends with a note that "someone" was unable to verify that the mooted problem even exists...

Gary
F G 41 Reputation points

2023-08-10T02:57:24.19+00:00

I'm already on a private network and my PC does not show up until I stop and start FDResPub service.

Answer 5

Limitless Technology 39,916

Hi @Gary Nebbett

You make an interesting point. I don't see my local PC in the Network List on Windows 10.

This is an interesting document:

https://learn.microsoft.com/en-us/windows/win32/fwp/windows-filtering-platform-start-page

This was first introduced with Vista, so maybe the issue has existed since then?

-------
--If the reply is helpful, please Upvote and Accept as answer--

Gary Nebbett 6,216 Reputation points

2022-04-15T08:30:19.127+00:00

Hello @Limitless Technology ,

What I believe to be the underlying problem (failure to correctly match loopback interface traffic against ALE multicast flows) may well have been present since WFP was first introduced in Windows Vista.

It was the change of "sublayer" of some built-in app isolation and Windows Service Hardening filters in Windows 11 which has made the "problem" apparent (easily detectable) in Windows 11.

The local PC should be visible in Windows 10 - if it is not visible there then that is for a different reason (perhaps the start-up ordering of the FDResPub and LanmanWorkstation services, as discussed in https://gary-nebbett.blogspot.com/2021/05/network-discovery-and-name-resolution.html).

Gary

Share via

Local computer not appearing in Explorer "Network" view under Windows 11

6 answers

Your answer