Network adapter continuously changes to "public"

Question

After a bunch of research I see that there are a lot of people effected by this issue: network adapter keeps changing from "Private" to "Public". I have gone so far as to change the settings in my registry, to set it in Powershell, and in Windows itself.

No matter what I change, the adapter immediately changes back to Public.

It appears that Microsoft doesn't really care about this problem, as every thread I read comes with the usual "We care about this issue, here's a non-fix" followed by the thread being locked.

Any and all assistance is greatly appreciated.

Answer 1

Sir,

    I was going to make a long post detailing every step that I took from EVERY link you posted, but I can see you are not actually interesting in assisting me. Good day Sir.

Answer 2

Sir,

    I attempted all of the things that you listed except to wipe my PC again, I also have other machines on my network that aren't experiencing the same issue, so I don't believe that the problem will lie with my ISP, but I will contact them to see if they set something in my router that I can't see or change. Why is the only other option when Windows inevitably messes up to wipe it and start from scratch? I do that at work, but I don't want to have to image my machine every 6 months because Microsoft refuses to fix this issue that has apparently been happening since 2015?

Answer 3

Sir,

    I have indeed attempted all of those steps as well, they did not help. Thank you.

Answer 4

Sir,

    As I stated in my earlier replies (and my original post) is that I have tried all of these things thus far. Even in my last post I stated that I do imaging as a normal part of my job to start with. 

I agree that a clean install will more than likely fix this issue, and have a clean image from the last time I did my last clean install (less than a year ago).

What my question in my last post was, Why is this an issue that has been around since 2015 and has yet to be fixed? I've combed through the forums already and 90% of the links that you sent me, I had already visited.

No offense to you, but what I'm hearing from you is that Microsoft has a broken product, and rather than fix it you advocate for a clean install.

I'm not saying that you aren't at least trying to be helpful, but I can also google issues. Like most of the IT community, that is the first step I take when troubleshooting.

I thank you for your assistance thus far, and I mean no disrespect if that is how I'm coming across. This is very frustrating and it wasn't a problem that arose in the XP days, or even in the Windows 7 days. I can just reimage and have the problem fixed. I was hoping that someone would be able to tell me why this issue is happening so that I could better understand it. Hopefully this 5 year old problem will be addressed by Microsoft, but I doubt it at this point if a forum MVP doesn't have the answer at this point.

Answer 5

Hi ME. I'm Greg, awarded MVP for eleven years, Volunteer Moderator, and Independent Advisor here to help you until this is resolved.

Have you tried the fixes from Shane and others in this thread, usually resolve it:

https://superuser.com/questions/944644/windows-...

I hope this helps. Based on what you report back I can answer any questions and may have other steps to perform.

______________________________________________

Standard Disclaimer: There are links to non-Microsoft websites. The pages appear to be providing accurate, safe information. Watch out for ads on the sites that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the sites before you decide to download and install it.