Anyway, unless you do static addressing you'll never see less than a /64 as a end user, you need that much for self assigned addresses. And that still gives us a 64bit network portion.
Why would IPv6 go wrong?
First off, it's a standard - not merely a Windows standard, but a global standard. (Windows has supported it out of the box since the famous XP Service Pack 2, and Linux has supported it since the 2.6 kernel series. Android and iOS have always supported IPv6 - the major driver of IPv6 for a standard was, in fact, mobile devices, and especially in developing nations, not the developed world; the Asian nations were the the first to push IPv6 out on a national basis, with Japan and South Korea leading that push.)
Second, the holdup with IPv6 has been embedded devices with non-changeable firmware. XB360/PS3/XB1/PS4 all support IPv6 explicitly - no idea about Nintendo. (Still, that does mean the consoles of both the curent-generation and previous-generation are covered.) Routers - I know of exactly zero consumer or prosumer routers that don't support IPv6 out of the box today. It may be disabled by default, but the support is there.
IPv6 support in XP sucks, it "works" but at a bare minimum. The 360/PS3/PS4 don't do IPv6 either.