Nice. It looks like there's an unrelated Windows bug in the network package, which I'll try to repro and fix tomorrow.