It sounds like you're dealing with a persistent issue where Network Discovery settings keep reverting. This can be frustrating, but let's methodically work through some potential fixes.
### Potential Solutions
1.
Ensure Dependency Services are Running:
Several services must be running for Network Discovery to work properly. Check the status of the following services:
- DNS Client
- Function Discovery Resource Publication
- SSDP Discovery
- UPnP Device Host
You can check and start these services as follows:
1. Press
Win + R to open the Run dialog.
2. Type
services.msc and press Enter.
3. In the Services window, find each of the services listed above.
4. Ensure they are set to
Automatic and
Running.
2.
Enable Network Discovery via Command Prompt:
Sometimes setting Network Discovery via the Command Prompt can help persist the setting.
1. Open
Command Prompt as an Administrator:
- Press
Win + X and select
Command Prompt (Admin) or
Windows PowerShell (Admin).
2. Execute the following commands:
Code:
netsh advfirewall firewall set rule group="Network Discovery" new enable=Yes
This command allows Network Discovery through the firewall.
3.
Check Network Profiles:
Ensure that your network is set to a Private profile. Network Discovery is typically disabled on Public networks for security reasons.
1. Go to
Settings > Network & Internet > Status.
2. Select
Change connection properties.
3. Ensure the network profile is set to
Private.
4.
Registry Check:
Occasionally, policy settings might revert Network Discovery settings. You can check the registry for any such policies:
1. Press
Win + R, type
regedit, and press Enter.
2. Navigate to:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Network Connections 3. Look for any policy settings that might control Network Discovery. Be cautious while editing the registry and ensure to back it up before making changes.
5.
Group Policy Editor (for Windows Professional editions):
If your system has access to Group Policy Editor (not typically available on Home editions), verify the settings:
1. Press
Win + R, type
gpedit.msc, and press Enter.
2. Navigate to:
Computer Configuration > Administrative Templates > Network > Network Connections 3. Ensure there are no policies enforcing restrictions on Network Discovery.
6.
Antivirus/Firewall Configurations:
Although you mentioned disabling the firewall and antivirus, ensure there are no residual settings or rules that might still block Network Discovery. Check both ESET and Windows Firewall settings in detail.
### Example of Service Status Check
Here's a quick look at how you might check and modify the status of one of the required services.
Code:
| Service | Status | Startup Type |
|------------------------------- |---------------|--------------|
| DNS Client | Running | Automatic |
| Function Discovery Resource... | Running | Automatic |
| SSDP Discovery | Running | Automatic |
| UPnP Device Host | Running | Automatic |
### Conclusion
Following these steps should help you identify why Network Discovery keeps defaulting to off. If you still encounter issues, please provide more details about any error messages or unusual behavior, and we can look deeper into the problem.
Good luck, and remember - persistence is key! If something doesn’t work right away, double-check each step meticulously. Sometimes it’s the small details that can make a big difference.
