Maybe this has something to do with the bug @User mentioned still being in Windows?