As I understood disabling TCP/IP v6 causes the problem?
Interesting, I haven't seen that yet. Gotta link?
Most of the world is still using IPv4 successfully, but Microsoft decided that Windows 10 -defaults- to IPv6, so a lot of networks (my workplace included) disable IPv6 to avoid confusion after a reboot. Maybe this update is Microsoft's attempt to convince the rest of the world that IPv6 MUST be used, practicality be damned.
If so, best of luck with that, MS. IPv6 is slowly catching on in places where it makes sense (cell-data IPs for example), but IPv4 is still humming along just fine in its little 32-bit spaces, using NATs and such. Sometimes the "IPv4 IS RUNNING OUT OF ADDRESSES!!" doom-sayers sound like the Global Warming doom-sayers.