Answered by:
Cannot Connect To Home Network

Question
-
Hi,
I am having issues connecting to my home network since I upgraded to Windows 10 from 7. I have Wifi signal booster in my basement as an extension of my home network. The extended net work SSID is different. Whenever I try to connect Windows 10 recognize it as a public network and not able to connect. I am tired of it and going back to Windows7.
Tuesday, October 27, 2015 1:52 PM
Answers
-
not able to connect to my home network due to my OS what is the point to upgrade to 10?
The fun of figuring it out? BTW me too. It seems every time my Hyper-V host (W10 RTM) gets updated the connectivity for the VM dies. It has been like this for nearly a year (starting with W8.2). I thought I had a workaround using Homegroup + ICS. Got an update and that stopped working. Then I abandoned wireless for wired. Got an update and that stopped working. I'm convinced it is just security/obscurity but that means that there is no help and no documentation for finding the next workaround. The pretentious deficient UX are beyond frustrating and irritating. If they can't do stuff automatically the way that they aspire to they should at least assist us in understanding what it is that they are misreading.
Robert Aldwinckle
---- Proposed as answer by Karen Hu Tuesday, November 10, 2015 1:44 AM
- Marked as answer by Kate LiMicrosoft employee Wednesday, November 11, 2015 2:00 AM
Thursday, November 5, 2015 10:43 PM
All replies
-
Appricaite the frustration this can cause, if you have not gone back to Windows 7 already.
Is this a HomeGroup you are trying to connect to?
If not can you explain how you are trying to connect, and what error message is displayed?Tuesday, October 27, 2015 7:22 PM -
Whenever I try to connect Windows 10 recognize it as a public network and not able to connect.
You can use PowerShell to diagnose and workaround this symptom.
Get-NetConnectionProfile
e.g. probably shows Name : Unidentified network which is why it is also showing NetworkCategory : Public
Then to change that you can use
Set-NetConnectionProfile -NetworkCategory "Private"
until you let the troubleshooter try to fix your other problem symptoms.
BTW this is just a more straightforward workaround than the more often seen suggestion to use the Homegroup troubleshooter but decline its offer to first use the Network troubleshooter after which it will not try to let you use its workaround of "fixing" the Public problem. ; }
Robert Aldwinckle
---Tuesday, October 27, 2015 9:56 PM -
Thanks for your reply. I tried everything I can. Only solution is to roll back to Windows 7 from 10, Windows 10 sucks big time. Imagine If I am not able to connect to my home network due to my OS what is the point to upgrade to 10? Don't use Windows 10 that's all.Thursday, November 5, 2015 6:16 PM
-
not able to connect to my home network due to my OS what is the point to upgrade to 10?
The fun of figuring it out? BTW me too. It seems every time my Hyper-V host (W10 RTM) gets updated the connectivity for the VM dies. It has been like this for nearly a year (starting with W8.2). I thought I had a workaround using Homegroup + ICS. Got an update and that stopped working. Then I abandoned wireless for wired. Got an update and that stopped working. I'm convinced it is just security/obscurity but that means that there is no help and no documentation for finding the next workaround. The pretentious deficient UX are beyond frustrating and irritating. If they can't do stuff automatically the way that they aspire to they should at least assist us in understanding what it is that they are misreading.
Robert Aldwinckle
---- Proposed as answer by Karen Hu Tuesday, November 10, 2015 1:44 AM
- Marked as answer by Kate LiMicrosoft employee Wednesday, November 11, 2015 2:00 AM
Thursday, November 5, 2015 10:43 PM