Hi @genne, the next update to Cursor should fix this issue. In the meantime, could you try the technique described here to manually patch the net core test explorer?