svchost trying to connect to IPv6 even that IPv6 is disabled

Microsoft claim that Windows is designed with Ipv6 present, and they say that Windows has not been tested with the feature disabled.

Digital Life said:

Not sure why you want to disable IPv6, I guess you have listened to some misguided fool who thinks it fixes something well it doesn't it's actually an itrigale part of local networking.


With that said try this Microsoft page.
https://support.microsoft.com/en-us/...advanced-users




You might want to set " Prefer IPv4 over IPv6 " and as far as your Home (127.0.0.1/8 - ::1/128 ) I'm not sure --

Good luck

Why should I have it enabled for?
My ISP has ipv4 network, my hardware firewall and dhcp server have ipv4, my local network is ipv4 my old retro computers have ipv4.
So why should i have ipv6 enabled for?

if you look at your link you posted and then look at my EDIT1: you see that is exactly what I did to disabled ipv6 and it doesn't work obviously

iko22 said:

Microsoft claim that Windows is designed with Ipv6 present, and they say that Windows has not been tested with the feature disabled.

Okay, so if Microsoft hasn't tested it, then I'm the guinea pig in other words. *HaHaHa*

Hello, the 3x addresses shown in Resource Monitor - have you used netsh to find the origin of the address?
Open CMD prompt, type

Code:

netsh interface ipv6 show route
netsh interface ipv6 show address

what is the output?

iko22 said:

Hello, the 3x addresses shown in Resource Monitor - have you used netsh to find the origin of the address?
Open CMD prompt, type

Code:

netsh interface ipv6 show route
netsh interface ipv6 show address

what is the output?

The result while i saw active ipv6 addresses.

Code:

C:\Windows\system32>netsh interface ipv6 show route 
 
Publish  Type      Met  Prefix                    Idx  Gateway/Interface Name 
-------  --------  ---  ------------------------  ---  ------------------------ 
No       System    256  ::1/128                     1  Loopback Pseudo-Interface 
 1 
No       System    256  ff00::/8                    1  Loopback Pseudo-Interface 
 1 
 
C:\Windows\system32>netsh interface ipv6 show address 
 
Interface 1: Loopback Pseudo-Interface 1 
 
Addr Type  DAD State   Valid Life Pref. Life Address 
---------  ----------- ---------- ---------- ------------------------ 
Other      Preferred     infinite   infinite ::1 
 
C:\Windows\system32>

It's the loopback adaptor that gets resolved by localhost. I have an idea that editing the hosts file may resolve the issue, on the basis that your registry change has not caused a corresponding change in the host file. Entries in the Hosts file are automatically loaded into the DNS client resolver cache. You could check and customize the hosts file in C:\Windows\System32\Drivers\etc directory. Open it with NotePad:

If this IPv6 line exists in hostfile

Code:

::1	localhost

then comment out, like so:

Code:

# ::1	localhost

AND, if the IPv4 localhost is missing then add to the file:

Code:

127.0.0.1 localhost

You can also delete/disable/customise the loopback adaptor, as it is not installed by default. In Device Manager > View, then tick show hidden devices.
Expand the Network Adapters node, and you should see Microsoft Loopback Adapter.
It is Okay to delete or disable or Customise (via Device Properties) this driver to remove it or change it to IPv4 protocol only

iko22 said:

It's the loopback adaptor that gets resolved by localhost. I have an idea that editing the hosts file may resolve the issue, on the basis that your registry change has not caused a corresponding change in the host file. Entries in the Hosts file are automatically loaded into the DNS client resolver cache. You could check and customize the hosts file in C:\Windows\System32\Drivers\etc directory. Open it with NotePad:

If this IPv6 line exists in hostfile

Code:

::1    localhost

then comment out, like so:

Code:

# ::1    localhost

AND, if the IPv4 localhost is missing then add to the file:

Code:

127.0.0.1 localhost

You can also delete/disable/customise the loopback adaptor, as it is not installed by default. In Device Manager > View, then tick show hidden devices.
Expand the Network Adapters node, and you should see Microsoft Loopback Adapter.
It is Okay to delete or disable or Customise (via Device Properties) this driver to remove it or change it to IPv4 protocol only

Thank you for helping me.
I tried to put # in front of :: 1 then I restarted the computer.
I deleted all my other domain blocks in the host file while I was testing, just to make sure none of it affected the result.
I have no device called Microsoft Loopback Adapter.
But I found a Microsoft 4to6 so I uninstalled it.
The only ones a have left is, Microsoft ISATAP adapter
Unfortunately, ipv6 addresses still appear in the resource monitor


I even did a really unorthodox test.. i did a backup on the registry and then ripped out everything with the name IPv6 or ip6 guts and all... believe it or not, but the damned ipv6 addresses appeared anyway in the system monitor.. I did expect the system to crach or the network not working... but noooo eweryting worked even the ipv6 addresses.

If it's any consolation for you " ::1 localhost " will not pass through your computer to your network, Every computer has that same IP.