I don't have any idea why the bug happens. Starting the server in a child PowerShell process resolves the issue.