File Explorer may not detect other devices or perform file sharing on the local network when running Windows 10 version 1803

m.s. tec's  fixed the tbl.

The problem is, none of these answers are "official", or come from Microsoft.  They come from volunteers who may be extremely knowledgeable, but do not really address the problem.  Many of us have tried the "solutions" offered by these volunteers, to no avail.  What needs to happen, is that Microsoft should issue an update that corrects the problem, and reestablishes network functionality to Windows 10.  I resolved the issue, in part, by re-enabling the feature that was disabled by 1803.  I have been told this is a bad idea, for security reasons.  No one has explained what the security issue may be.  Whatever, Microsoft needs to correct this problem.  NOW!

I have tried all the "help solutions" in this thread and nothing works.  Has anyone heard if or when Microsoft will fix this problem?  Not being able to access other computers is making it almost impossible for me to do my work.  I have to physically go to the different computer to do the work.  If they don't have a fix why can't we go back "before" the damaged update?

Feeling flustrated

PERFORMANCE WITH DIFFERENT BUILDS AND AMOUNTS OF MEMORY 2018.07.25

I said that I was dropping this problem.  I confess.  I went back to it.  I am weak.

-- Configuration 1 (both volume sets from backups made in late March) works fine.  

-- Configurations 2 and 3 are nearly useless.  Note 1 describes a wallpaper artifact that

   arises on WARTHOG2-M.

-- Configurations 4 and 5 are useful, as long as I manage to fight off Windows Update.  

   As long as the machine is running, it threatens to update WARTHOG1-M and reduce my

   network to trash.

 ---------------------- Table 4:  ---------------------------------------

|        |            |         |  Main  |   RDC    | File Sharing |      |

| Config |  Machine   |  Build  | Memory | of Other |  From Other  | Note |

|        |            |         |   gB   | Machine? |   Machine?   |      |

|--------|------------|---------|--------|----------|--------------|------|

|    1   | WARTHOG1-M | Backup  |   16   |   Yes    |     Yes      |      |

|        |    "   2-M | Backup  |    8   |   Yes    |     Yes      |      |

|--------|------------|---------|--------|----------|--------------|------|

|    2   | WARTHOG1-M |  1803   |   16   |   Yes    |     Yes      |  1   |

|        |    "   2-M |  1803   |    8   |    No    |      No      |      |

|--------|------------|---------|--------|----------|--------------|------|

|    3   | WARTHOG1-M |  1803   |    8   |   Yes    |     Yes      |  1   |

|        |    "   2-M |  1803   |   16   |    No    |      No      |      |

|--------|------------|---------|--------|----------|--------------|------|

|    4   | WARTHOG1-M | Backup  |   16   |   Yes    |     Yes      |      |

|        |    "   2-M |  1803   |    8   |   Yes    |     Yes      |      |

|--------|------------|---------|--------|----------|--------------|------|

|    5   | WARTHOG1-M | Backup  |    8   |   Yes    |     Yes      |      |

|        |    "   2-M |  1803   |   16   |   Yes    |     Yes      |      |

 -----------------------------------------------------------------------

Notes

  1  When WARTHOG2-M came up, the file shares appeared for several seconds to a minute and

     then disappeared.  he machine's wallpaper appeared briefly and disappeared, leaving the display black.

Evidently, the problem has little or nothing to do with the quantity of installed memory.  The right-center column of shows misbehavior on the part of the services.  I have no faith that these eight magic service have anything to do with the broader file sharing problem.  However, the misbehavior may represent damage from '1803 or other Microsoft interferences that began in February.  I'm going to install backups made in late January and let Windows Update do disgusting things to them.  I'm open to suggestions.  More late.