Windows 10: Ad hoc network..."Private" network doesn't stick

I have a unique situation and I haven't been able to find the answer. I have set up an ad hoc network on the "host" computer (i.e. the netsh "hostednetwork" computer) so that I can remote into the host computer using another computer ("client" PC).

What this does is create a local area network. In the Network and Sharing Center this network is listed as an unidentified network, PUBLIC network. When the network is set to public I cannot remotely connect to the host pc from the client pc. The client PC sees the hostednetwork and I can connect to the network, but when trying to remote into the host computer from the client computer the connection between the computers doesn't work. Both computers are connected to a Homegroup.

Using the Homegroup troubleshooter, the troubleshooter identifies a problem and automatically sets the network to Private. When set to private, I can successfully remote into the host PC from the client PC. This is repeatable, whenever the hostednetwork is set to private I can remote in.

The problem is that whenever I restart the computer the hostednetwork reverts to PUBLIC. I cannot figure out a way to have the ad hoc network stay as a PRIVATE network.

Any help? I should also mention that this was not an issue in Win8.1.

:)

 

connection to ad hoc networks

I think you are mixing up an Ad hoc network with a router with Hidden SSID.

 

WP8 lumia ad-hoc support

OP's problem (and mine too) was about connecting to ad-hoc networks created by symbian phones, not PCs running Windows. By the way, windows 7 and windows 8 support creating infrastructure wifi networks and sharing any kind of internet connection over that
wifi hotspot without the need of any 3rd party software or driver.

Just a nice powershell script would do.



GDR3 also doesn't support ad-hoc networks.

 

I could not get this resolved by troubleshooting, so I did a clean install and now all is well. Both my ad hoc and normal network connections are set to private and it stays private after a reboot. However, with the clean install I opted not to use my microsoft login credentials and just kept it as a local account, and also I purposefully did not join the homegroup. I suspect that joining the homegroup may have been the issue. Strangely, I can still use file sharing etc even without being joined to the homegroup, but I don't really understand all that homegroup stuff.