Undo that last workaround, the cause seems to be particular to the machine I tested this with