Changed to Private but resets to Public every restart? Network sharing broken? Here are 7 fixes that permanently lock Windows 11 network profile to Private.
📋 Table of Contents
🔍 Why Does Network Profile Keep Changing to Public?
Set Network to Private in Settings
This sets the profile immediately. Combine with Fix 2 or Fix 3 to prevent it from reverting.
- Press
Win + I→ Network & Internet - Click your active connection (WiFi or Ethernet)
- Under Network profile type → select Private network
Force Private Profile via PowerShell — Most Reliable
PowerShell sets the network category at system level, bypassing NLA service auto-reset.
Registry Category Fix — Survives Windows Updates
The registry stores network profile settings that Windows loads on every boot. Setting Category to 1 forces Private at a level that survives all updates.
- Press
Win + R→ typeregedit→ Enter - Go to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Profiles - Expand Profiles → click each GUID subkey → check ProfileName to find your network
- In your network GUID folder: double-click Category DWORD value
- Set value to
1(1 = Private | 0 = Public | 2 = Domain) - Click OK → close regedit → restart PC
Forget Network and Reconnect Fresh
The saved profile may have a corrupted Category value. Forgetting and reconnecting creates a fresh registry entry.
Win + I→ Network & Internet → WiFi → Manage known networks- Find your network → Forget
- Reconnect → enter password
- When asked “Allow other PCs to discover this PC?” → click Yes (sets Private)
- Immediately apply Fix 2 to lock it permanently
Restart Network Location Awareness Service
Restarting NLA forces it to re-evaluate the network fresh. Run Fix 2 immediately after for the best result.
- Press
Win + R→ typeservices.msc - Find Network Location Awareness → right-click → Restart
- Find Network List Service → right-click → Restart
- Run Fix 2 PowerShell command immediately after
Update Network Adapter Driver
Outdated drivers trigger NLA re-evaluation on every connection event, resetting the profile to Public each time.
- Press
Win + X→ Device Manager → Network Adapters - Right-click active adapter → Uninstall device → check delete driver → Uninstall
- Download latest driver from PC manufacturer site → install → Restart
- Apply Fix 2 after restart
Lock Profile via Group Policy (Windows 11 Pro Only)
Group Policy completely prevents Windows or any service from ever automatically changing the network profile.
- Press
Win + R→ typegpedit.msc→ Enter - Go to: Computer Configuration → Windows Settings → Security Settings → Network List Manager Policies
- Double-click your network name (or Unidentified Networks)
- Set Location type to Private
- Set User permissions to User cannot change location
- Click OK → restart PC
| # | Fix | Level | Time | How Permanent? |
|---|---|---|---|---|
| 1 | Settings Network Profile | Easy | 30 sec | Temporary — reverts on reconnect |
| 2 | PowerShell Force Private | Medium | 2 min | Permanent — survives restarts |
| 3 | Registry Category = 1 | Medium | 5 min | Most permanent — survives updates |
| 4 | Forget and Reconnect | Easy | 2 min | Creates clean fresh profile |
| 5 | Restart NLA Service | Medium | 2 min | Forces fresh evaluation |
| 6 | Update Network Driver | Medium | 5 min | Stops driver-triggered resets |
| 7 | Group Policy Lock | Medium | 5 min | Strongest lock (Pro only) |
❓ Frequently Asked Questions
Why does Windows 11 keep changing network profile to Public?
How do I permanently set network to Private in Windows 11?
Does network profile affect internet speed in Windows 11?
Why does Windows 11 show my network as Unidentified?
Can I use Group Policy to permanently prevent profile from changing?
✅ Bottom Line
Network profile keeps changing to Public because the NLA service resets it on every connection event. The permanent combined fix is Fix 2 (PowerShell force Private) + Fix 3 (Registry Category = 1). Apply both and your network stays Private through restarts, reconnections, and Windows updates. Windows 11 Home users use PowerShell plus Registry. Pro users add Group Policy (Fix 7) for the strongest possible lock.