It was found that there is a race condition on the windows environment that leads the test to hang forever waiting for the pauseShardSplitAfterBlocking fail point to be reached and instead the timeout happen and we go directly to the .onError step which hangs the test forever and the service is waiting for forget shard split command to be kicked in from the test which is currently blocking on the failpoint to be triggered.