Windows could not automatically detect this network's proxy settings

Anonymous

Recently, I have noticed a small caution triangle appearing with my network icon on the task bar. When I right click and troubleshoot, it comes with this message. Windows could not automatically detect this network's proxy settings. My internet has been very slow lately, but I'm wondering if this is a problem with my network? or is this something that my ISP has to fix?

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

Anonymous

(This post is intended for all reporting the problem)

Check Internet Options (from Control Panel or Internet Explorer Tools / Options /Connections Tab / LAN Settings and make sure Proxy Server is unchecked even if using Firefox. Check settings in Firefox in Tools / Options /Advanced Connections / Settings (should be either use system proxy settings or no proxy).

Check for malware especially using malwarebytes.

Try these two commands in that order in an elevated command prompt. Do the first one first then reboot and try. If still bad try the second.

netsh winsock reset

netsh int ipv4 reset

If these don't help, please post the output of an ipconfig /all command

0 comments

Answer accepted by question author

Anonymous

I had the same problem this morning--couldn't connect on one computer but could on the other. Got the same message about not being able to detect the proxy settings. However, I used System Restore to reverse some changes that had happened during the night and that corrected the problem.

0 comments

173 additional answers

Anonymous

2018-09-14T13:16:17+00:00
IPCONFIG /ALL RESULTS POSTed below

(This post is intended for all reporting the problem)

Check Internet Options (from Control Panel or Internet Explorer Tools / Options /Connections Tab / LAN Settings and make sure Proxy Server is unchecked even if using Firefox. Check settings in Firefox in Tools / Options /Advanced Connections / Settings (should be either use system proxy settings or no proxy).

Check for malware especially using malwarebytes.

Try these two commands in that order in an elevated command prompt. Do the first one first then reboot and try. If still bad try the second.

netsh winsock reset

netsh int ipv4 reset

If these don't help, please post the output of an ipconfig /all command

Wireless LAN adapter Local Area Connection* 3:

   Media State . . . . . . . . . . . : Media disconnected

   Connection-specific DNS Suffix . :

Wireless LAN adapter Local Area Connection* 5:

   Media State . . . . . . . . . . . : Media disconnected

   Connection-specific DNS Suffix . :

Wireless LAN adapter Wi-Fi:

   Connection-specific DNS Suffix . : Belkin

   Link-local IPv6 Address . . . . . : fe80::f03f:2eae:a28b:309%24

   IPv4 Address. . . . . . . . . . . : 192.168.2.67

   Subnet Mask . . . . . . . . . . . : 255.255.255.0

   Default Gateway . . . . . . . . . : 192.168.2.1

PS C:\WINDOWS\system32> all

all : The term 'all' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the

spelling of the name, or if a path was included, verify that the path is correct and try again.

At line:1 char:1
- all
    + CategoryInfo          : ObjectNotFound: (all:String) [], CommandNotFoundException

    + FullyQualifiedErrorId : CommandNotFoundException

PS C:\WINDOWS\system32> ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : LAPTOP-1787ICOM

   Primary Dns Suffix . . . . . . . :

   Node Type . . . . . . . . . . . . : Hybrid

   IP Routing Enabled. . . . . . . . : No

   WINS Proxy Enabled. . . . . . . . : No

   DNS Suffix Search List. . . . . . : Belkin

Ethernet adapter Ethernet:

   Media State . . . . . . . . . . . : Media disconnected

   Connection-specific DNS Suffix . :

   Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller

   Physical Address. . . . . . . . . : 54-AB-3A-6A-42-C2

   DHCP Enabled. . . . . . . . . . . : Yes

   Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Local Area Connection* 3:

   Media State . . . . . . . . . . . : Media disconnected

   Connection-specific DNS Suffix . :

   Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #8

   Physical Address. . . . . . . . . : CA-FF-28-27-99-6D

   DHCP Enabled. . . . . . . . . . . : Yes

   Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Local Area Connection* 5:

   Media State . . . . . . . . . . . : Media disconnected

   Connection-specific DNS Suffix . :

   Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #9

   Physical Address. . . . . . . . . : DA-FF-28-27-99-6D

   DHCP Enabled. . . . . . . . . . . : Yes

   Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wi-Fi:

   Connection-specific DNS Suffix . : Belkin

   Description . . . . . . . . . . . : Qualcomm Atheros QCA9377 Wireless Network Adapter

   Physical Address. . . . . . . . . : CA-FF-EC-27-11-FD

   DHCP Enabled. . . . . . . . . . . : Yes

   Autoconfiguration Enabled . . . . : Yes

   Link-local IPv6 Address . . . . . : fe80::f03f:2eae:a28b:309%24(Preferred)

   IPv4 Address. . . . . . . . . . . : 192.168.2.67(Preferred)

   Subnet Mask . . . . . . . . . . . : 255.255.255.0

   Lease Obtained. . . . . . . . . . : Friday, 14 September 2018 11:02:56 PM

   Lease Expires . . . . . . . . . . : Tuesday, 22 October 2154 5:40:59 AM

   Default Gateway . . . . . . . . . : 192.168.2.1

   DHCP Server . . . . . . . . . . . : 192.168.2.1

   DHCPv6 IAID . . . . . . . . . . . : 214499112

   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1E-AB-C7-7F-54-AB-3A-6A-42-C2

   DNS Servers . . . . . . . . . . . : 192.168.2.1

   NetBIOS over Tcpip. . . . . . . . : Enabled

PS C:\WINDOWS\system32> ^C

PS C:\WINDOWS\system32>
Was this answer helpful?

0 comments No comments
Anonymous

2018-11-27T16:14:16+00:00

![](https://learn-attachment.microsoft.com/api/attachments/7a0fb681-1f52-4746-b526-f570f08fa7e0?platform=QnA you go
Was this answer helpful?

0 comments No comments
Anonymous

2018-11-28T09:38:22+00:00

![](https://learn-attachment.microsoft.com/api/attachments/7a0fb681-1f52-4746-b526-f570f08fa7e0?platform=QnA you go

Microsoft Windows [Version 10.0.17134.407]

(c) 2018 Microsoft Corporation. All rights reserved.

C:\Users\iam>netsh winsock reset

The requested operation requires elevation (Run as administrator).

C:\Users\**>netsh int ipv4 reset

Resetting Compartment Forwarding, OK!

Resetting Compartment, OK!

Resetting Control Protocol, OK!

Resetting Echo Sequence Request, OK!

Resetting Global, failed.

The requested operation requires elevation (Run as administrator).

Resetting Interface, failed.

The requested operation requires elevation (Run as administrator).

Resetting Anycast Address, OK!

Resetting Multicast Address, OK!

Resetting Unicast Address, failed.

The requested operation requires elevation (Run as administrator).

Resetting Neighbor, failed.

The requested operation requires elevation (Run as administrator).

Resetting Path, failed.

The requested operation requires elevation (Run as administrator).

Resetting Potential, OK!

Resetting Prefix Policy, OK!

Resetting Proxy Neighbor, OK!

Resetting Route, OK!

Resetting Site Prefix, OK!

Resetting Subinterface, OK!

Resetting Wakeup Pattern, OK!

Resetting Resolve Neighbor, OK!

Resetting , OK!

Resetting , OK!

Resetting , OK!

Resetting , OK!

Resetting , failed.

The requested operation requires elevation (Run as administrator).

Resetting , OK!

Resetting , OK!

Resetting , OK!

Resetting , failed.

The requested operation requires elevation (Run as administrator).

Resetting , OK!

Resetting , OK!

Resetting , OK!

Restart the computer to complete this action.

________________________________________________________________________________

That is my result of the command prompts suggested.

I have since been researching how to open command promt as administrator....

I do appreciate the continued attempts to sort this annoying bug in Windows 10.
Was this answer helpful?

0 comments No comments