They claim it was related to the restarts after Windows Update - maybe that really was true, and only the windows clients need to be changed to alter the timing of the logins or something similar?

Naaaah, it was an issue where when a bunch of nodes of their peer-to-peer network cycled off and on, the “self-healing nature” of the network failed; they claim that they identified some component of their P2P implementation that, due to a bug, caused the failure. The new Windows client ostensibly contains the fix to the implementation, but given that we’re talking about the platform-independent part of their technology — the network and how it’s managed/implemented — that solution needs to be pushed out to *all* their platforms. It’s just weird to me that they chose only to fix the Windows side of it.

(Also note that there are a lot of voices out there expressing doubt that Skype’s explanation makes any sense; this month’s MS patches weren’t distributed any differently, and there’s no reason that all those Windows machines out there should have behaved any differently in installing the patches. The fact that only the Windows client got fixed is another data point in favor of there being another explanation of what happened…)