The error exists from patch 2 on. I did some network testing with patch 1 and currently use it and have no errors so far.