Windows 10, Version 1809. Network does not show computers

Hey galileo1564, you seem to have a good understanding of this situation. Your response was in reply to this statement in the previous post:

> To add the trigger, run as Administrator:

> sc triggerinfo FDResPub start/strcustom/fbcfac3f-8460-419f-8e48-1f0b49cdb85e

> /PROFILE_CHANGED_TO_PRIVATE

I'm trying to get a better understanding of what is happening here.

What are the actual circumstances that will cause this trigger to activate?

What does the statement "/PROFILE_CHANGED_TO_PRIVATE" actually mean?

To me, (and I'm not a programmer, just a self-taught computer geek with an MS in EE) this doesn't look like a piece of programming syntax that I recognize as fitting with some programming language. It strikes me as more like a comment or placeholder, as though the coder was leaving a reminder for himself to come back and put in the right code when he figured out what that was.

What's your take on this? Thanks!

I didn't and I just added the task to the scheduler.  I guess discovery goes on then off then back on.

In addition to this procedure, is it also necessary to use command prompt as administrator to delete the trigger of Function Discovery Resource Publication by typing:

sc triggerinfo FDResPub delete ?

I have this issue on multiple machines. Dell machines, Lenovo machines, EVGA  motherboard self built machines. This is an issue that Microsoft is ignoring.

BUT, attention K-Mart shoppers, this is the best fix because it is self contained and fixed all of the issues on all of the machines that I have. It is simple and minimal. Since it is self contained it is easy to remove. Credit goes to an earlier poster. I have needed this on multiple windows versions up to current release.

Add the following to Task Scheduler.

Name:  FDResPub

Description:  Restart the FDResPub service.

Run whether user is logged on or not - Do not store password.

Configure for:  Windows 10

Trigger:  At Startup

Actions:  (here is the magic for no script)

    - Action:  Start a program

    - Program/script:  cmd

    - Add arguments:  /c net stop FDResPub && net start FDResPub

    - Start in:  (leave empty)

Conditions:  start only if the following network connection is available - Any connection

Settings:  (leave defaults)

Yes,  that is another workaround that works, restarting FDResPub service takes care of the problem.

Still waiting for MS to fix this bug properly :-(

I have this issue on multiple machines. Dell machines, Lenovo machines, EVGA  motherboard self built machines. This is an issue that Microsoft is ignoring.

BUT, attention K-Mart shoppers, this is the best fix because it is self contained and fixed all of the issues on all of the machines that I have. It is simple and minimal. Since it is self contained it is easy to remove. Credit goes to an earlier poster. I have needed this on multiple windows versions up to current release.

Add the following to Task Scheduler.

Name:  FDResPub

Description:  Restart the FDResPub service.

Run whether user is logged on or not - Do not store password.

Configure for:  Windows 10

Trigger:  At Startup

Actions:  (here is the magic for no script)

    - Action:  Start a program

    - Program/script:  cmd

    - Add arguments:  /c net stop FDResPub && net start FDResPub

    - Start in:  (leave empty)

Conditions:  start only if the following network connection is available - Any connection

Settings:  (leave defaults)