Disable IPv6 and its Components




How to disable IPv6 and its components in windows

Have you ever experienced, that an computer still responds to your ping, even though ipv6 is disabled through network interface properties?

It seems, that unchecking the ipv6 interface isnt exacly enough. Here I will show you, how to completly disable IPv6 and its components, so it cant respond on its interface, regardless.





What you need, besides unchecking the "Internet Protocol Version 6 (TCP/IPv6)", is creating an regedit entry.

Open "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TCPIP6\Parameters", and create a new DWORD(32bit) called "DisabledComponents" (Note: Its case sensitive), modify the attribute to "ff" (255 hex). See image below.



Restart the computer, and IPv6 is now disabled.


If you need to deploy it to multiple machine, you can create a regedit file and place the following inside it.


[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TCPIP6\Parameters]
"DisabledComponents"=dword:000000ff



Popular posts from this blog

[SOLVED] Veeam: Failed change tracking (CBT)

Image
Failed to flush change tracking data, using full scan to determine changes. Failed to create change tracking time stamp for virtual disk file I've encountered the above, after i added some new CSV to a cluster. The backup jobs have been running fine for ages before this. As per say, this is not really a critical issue, since the backups just takes longer. Needless to say, i wanted it to function. I tried: Reboot Nodes, Hosts, VMs Fully update Stop VeeamFCT service and Start it again Update hyper-v integration service Delete previous backups Run full backups Read Veeam forums Running Reset-HvVmChangeTracking Din't work. However!
Read more »»»

Fixing Error 25541. Failed to open XML file

Fixing Error 25541. I had to install Compact 4.0 on a client computer today. However, i got the error below: Error 25541. Failed to open XML file C:\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG\machine.config, system error: -2147024786 Setup failed. Rolling back  This was a huge pain in the a**, but the solution was very simple.
Read more »»»