Homegroup removed! How to get network sharing work with Windows 10 v1803.

Anonymous
2018-05-11T04:03:57+00:00

Here is short description how I get my network sharing work with Windows 10 v1803.

(I haven't never use Homegroup so I start directly from step 2.)

  1. Only for those PC's which are still using Windows 10 v1709 or older:

    Disconnect from non-existing Homegroup if you have used it.

2.1. All PC's: Check Network profile and Network discovery and Share settings

Sometimes this selection to change between Private and Public network profile is missing from Settings / Networks page. In that case profile must change by PowerShell. Right Click Windows Icon (Start button) and open PowerShell (Admin) and use following commands to get interface index number and change profile to Private (or Public):

Get-NetConnectionProfile

Set-NetConnectionProfile -InterfaceIndex <index number> -NetworkCategory Private

2.2. All PC's: Check Network Discovery and Share settings

https://learn-attachment.microsoft.com/api/attachments/f7770a4f-8e37-48c9-a436-2fe4e8e12ca0?platform=QnA

  1. All PC's: Set Start type to Automatic and start following services that allow PC's to be visible on Network. (Reboot.)

   Push Win Key and type "Services", locate these services.

   - Function Discovery Provider Host

   - Function Discovery Resource Publication

   - SSDP Discovery

  • UPnP Device Host

  1. Setting shares.

4.1. Check your current shares.

Open file explorer and type \localhost to address bar to see what shares are made in this computer.

![](https://learn-attachment.microsoft.com/api/attachments/d9a66593-0cd1-499b-908f-36a6854f27c1?platform=QnA

4.2. Create new share (here I use folder "Test"). 

(Setting "Turn on sharing so anyone …" in Step 2.2.  make share for folders in C:\Users automatic.)

Folder is now shared and Network share path is: \PCNAME\Test

4.3. Safe way to share folders.

Create user account to all users on your network to whom you want to give access to shared resources.

Use same user ID and password which they have on their own computers.

Right click "Test" and open Properties and select Security tab to see current settings.

Default security settings are shown in next picture.

Those settings allow access to shared folder(s) only for those users who have user ID on that computer.

4.4.  Sharing folder "Test" to Everyone" (Very unsafe setting! Think carefully do you need to select this!)

If you want that everyone have access to that share then go to Security tab and:

  • When back to Permissions dialog select which rights you want to give to "Everyone".

Now anyone on your home network should have access to shared folders without credentials or having user account on your computer.

  1. Now when click Network on File Explorer all your PC's should be visible in Computer and Network sections.

This should be cover the essentials to sharing your data over local network. This share is not limited to C:\Users folder, every folder can be handled like shown in steps 4.

Now your PC's should visible, but if not then try to reset all network settings:

Go to Settings / Network & Internet / Status, scroll down to find "Network reset, on next window click "Reset  Now" button.

It will takes about 5 min to perform this reset and then PC reboot automatic.

When you sing in first time you get notification something like "Do you want your PC to be access by other computers", click Yes for that.

If you get error message "Windows cannot access \PC_NAME" when you try to connect shared folders then continue to step 6.

  1. There is some bug on Windows 10 1803 and because of that PC's can't always connect to each other by Name.

If you get error "\PCNAME path not found" you can solve this by adding your PC's and IP-addresses to hosts file.

6.1 New routers (or modems) may have feature to remember which IP-addresses are assign to each device, but with older routers (or modems) you have to check that your router or modem is set give predefined IP-addresses linked to each PC's MAC-address.

This way PC's will get same IP-address every time when it ask IP-address form router (or modem) DHCP-server.

There should be some kind of list of PC names with MAC addresses and given IP-addresses of each connected PC. 

Picture show that list on my router. In my case with old router I had to select manual assignment  in each line. 

6.2. Add all PC's IP-addresses and Names to hosts file (C:\Windows\System32\drivers\etc\hosts). 

You can check your IP-address and PC's name by opening command prompt (CMD)

For IP-address type command: ipconfig you get line like this: IPv4 Address ………. 192.168.100.101

For PC name type command:  hostname

Write down IP-address and Name of each PC and add those to that hosts file.

To edit copy hosts file to some another location, right click it and use notepad to edit and save it. Replace original file with edited file. Because hosts file is located on system folder replace will ask administrators rights to perform it.

localhost name resolution is handled within DNS itself.

# 127.0.0.1             localhost

# ::1                        localhost

192.168.100.101  PC1   # Ethernet  

   192.168.100.102  PC2   # Ethernet

   192.168.100.202  PC2   # Wi-Fi

Windows for home | Windows 10 | Files, folders, and storage

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

326 answers

Sort by: Newest
  1. Anonymous
    2018-05-22T04:32:43+00:00

    This is NOT a bug. Only Home Edition still supports NetBIOS Computer Browser as of 1803 -- Windows Pro just lost support as Enterprise Edition etc did before.  MS announced that NetBIOS was obsolete and insecure and would be eventually be removed over 15 years ago (when Active Directory Services was released for enterprise networks).  But phasing out NetBIOS has taken so long time most people forgot and most home users where never really directly informed.

    Anyways move to DNS based name services like the Internet uses. CIFS runs fine without NetBIOS names. Its not hard to access Samba or Windows file servers with raw IPs or DNS names. But networks still work best with your own central DNS server on your network for name-IP persistence when machines are in sleep mode or off etc.

    Also there are a ton of built in services to automatically discover and fill network resources to DNS servers or individual machines on an ad hoc network.  Assuming you filled in DNS host names as you should and did not turn off such services during installation because NetBIOS names were still working. Heh MS probably should have turned such services on by default when removing NetBIOS for those machines which had file and print sharing on.

    Well less sophisticated home networks and cheap NAS may not have default DNS name services in many cases. Which is why Windows 10  Home edition still supports NetBIOS browsing. But seriously home routers and NAS should support home network DNS along with DHCP. The industry just needs dynamite to move off their chairs for such a minor issue. Expect it in your router and do not buy unless you do.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2018-05-21T22:07:49+00:00

    Pauli O.

    I know that the external virtual switch works because I've used it before, but removed it.  It is just that all of a sudden Windows is not letting me add it back.  I've found advice to use Powershell >netcfg -d to clear and re-establish virtual adaptors.  I will go that route if necessary, but have to take care of some other issues first.  Thanks.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-05-21T22:01:10+00:00

    That is not my point. My point is, how much do you really know. Seriously, how many PC's and networks have you did. Because with experience comes knowledge. You can not just micky mouse things, especially when it is someone else's and especially a business and their network. That is my point. You would last about a week.

    And when you start troubleshooting systems and networks, you do not just do anything, because then that comes with problems and problems for others, which is not good for them or yourself.

    Take Care Paul.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-05-21T21:53:49+00:00

    "I been doing this over 15 years on 1000's of PC's, Servers and on Home and Business networks"

    I have never had any need to boost myself with my experience or my education and I don't see any reason for that in this forum.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2018-05-21T21:28:07+00:00

    Testing for servers. LOLOL, you mean on your little Home Network with 3 PC's and never a server.

    Your belief running garbage to begin with like "Hypervisor"  (Hyper -V or Virtual PC) for which I am sure for no reason at all, and advising your changes to people is outright bad advice "PERIOD", with or with those running.

    A guy that has only probably worked on 10 PC's in his life and on maybe 3 Home Networks advising others is Comical to say the least.

    Take Care Paul!

    Was this answer helpful?

    0 comments No comments