If you've disabled IPv6, read in


Recommended Posts

The article shows how you might regain 5 seconds of your boot time. It turns out that MS's method for disabling IPv6 (not that you should be disabling it in the first place, in most cases) has been faulty for a number of years until very recently.

 

http://blogs.technet.com/b/askpfeplat/archive/2014/09/15/a-5-second-boot-optimization-if-you-ve-disabled-ipv6-on-windows-client-and-server-by-setting-disabledcomponents-to-0xffffffff.aspx

  • Like 2
Link to comment
Share on other sites

thanks for the fix will push it out the new registry fix in a gpo, I only leave ipv6 enabled on wds and tmg servers where its necessary don't use direct access or remote assistance easy connect

Link to comment
Share on other sites

The only time I've "disabled" IPv6 is by using the network control panel and unticking it in the connection properties, nothing more.

And even then only for the rare case where it had an actual issue, otherwise I've left it alone.

Link to comment
Share on other sites

Yes, the check box method doesn't create the Registry entry (the crux of the problem) that the official method did.

 

Although, I don't think the check box method is considered (by MS anyway) to be the proper way of disabling IPv6, which is unfortunate since it's a simple check box available in a logical place. I don't recall the details now, but I think it's considered to be an incomplete solution.

Link to comment
Share on other sites

What if my boot time is under 6 seconds :/

Then you could SAVE!!!!!!111 .... 0.1 seconds on your bootup. :p

 

 

Using the checkbox would just stop IPv6 "binding" to that interface, wouldn't actually disable the functionality (You'd still have ::1 most likely, etc.)

I believe that's the case, yes. But usually stops any rare problems which might conflict with IPv6.

  • Like 1
Link to comment
Share on other sites

What if my boot time is under 6 seconds :/

 

Then you should expect your PC to be on seconds before you even press the button... that, is a decent boot time :p

Link to comment
Share on other sites

You need a faster CPU  :laugh:

And Flux Capacitor 

Then you should expect your PC to be on seconds before you even press the button... that, is a decent boot time :p

I  think that could be done via NFC tags if the buttons on my laptop were "digital" (and if I knew anything about electronics)

 

According to my task manager, current bios boot time is 1.6s, on my watch it takes just shy of 5 seconds for windows to be fully loaded. Though I might add, this under windows 8 and its "magical" hybrid boots.

Link to comment
Share on other sites

The article shows how you might regain 5 seconds of your boot time. It turns out that MS's method for disabling IPv6 (not that you should be disabling it in the first place, in most cases) has been faulty for a number of years until very recently.

 

http://blogs.technet.com/b/askpfeplat/archive/2014/09/15/a-5-second-boot-optimization-if-you-ve-disabled-ipv6-on-windows-client-and-server-by-setting-disabledcomponents-to-0xffffffff.aspx

IPv6 is not, and has never, been disabled by default in any version of Windows.  While Windows XP (with Service Pack 1) was the last version to ship without IPv6 support, it was offered in Service Pack 4 for Windows 2000, and Service Pack 2 for Windows XP; all versions of Windows since have included it, and it has been active by default.

 

However, some users - and even some OEMs - *did* turn off IPv6 by default - at the request of their customers.  The issues (for the customers) was two-fold - non-support by their infrastructure (routers and ISPs - that is still an issue in some places/cases), and "trimming of un-necessary services" - THAT issue goes back to 9x, if not NT.  While Teredo (as an implementation methodology) is still the default methodology, native (non-Teredo) IPv6 support has been available (again, going back to the aforementioned Service Packs).  I have, in fact, been using IPv6 - either natively or via free IPv6 tunnel services (such as HE TunnelBroker) for three years.

Link to comment
Share on other sites

Following up, the article included this juicy tidbit that might be overlooked amid the possibility of achieving flux capacitance. Question: Are all of the things mentioned actually IPv6-only?  It can be read that way, but there's some wiggle room in the interpretation. I can see how the relatively obscure and corp-only DirectAccess could be, but the rest?!

 

If IPv6 is disabled on Windows 7, Windows Vista, Windows Server 2008 R2, or Windows Server 2008, or later versions, some components will not function. Moreover, applications that you might not think are using IPv6?such as Remote Assistance, HomeGroup, DirectAccess, and Windows Mail?could be.

Therefore, Microsoft recommends that you leave IPv6 enabled, even if you do not have an IPv6-enabled network, either native or tunneled. By leaving IPv6 enabled, you do not disable IPv6-only applications and services (for example, HomeGroup in Windows 7 and DirectAccess in Windows 7 and Windows Server 2008 R2 are IPv6-only) and your hosts can take advantage of IPv6-enhanced connectivity.?

Link to comment
Share on other sites

Yeah, HomeGroup requires IPv6 (As it says :laugh:), I think DirectAccess used to be able to operate over IPv4 (by tunneling IPv6) but Microsoft wants to move away from Teredo entirely (They want to turn off their Teredo server and let ISPs run their own, primarily for the Xbone which wants to use IPv6 as the default)

I'm not sure if Windows operates this way, but I know on some OSs binding a socket to "::" will create a socket that listens on IPv4 and IPv6 (Compared to listening on "0.0.0.0" for just IPv4), so apps that used that method would probably break if IPv6 was disabled at the OS level, which is funny, since the only reason you'd ever want to disable IPv6 is if important apps can't break with it enabled (Which should probably be replaced if they haven't been updated since the 2k/XP era), not having IPv6 WAN connectivity doesn't matter (Since you still want it for LAN communications)

Edit: And if you have networking hardware that can't handle IPv6, it's junk that should be replaced.

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.