Ok, so it seems that a windows update is responsible for the issues and that removing the KB5000808 & 802 resolves the issue. Has anyone managed to remove these KBs?
