Hey there.
Can you test and see if reverting to v5.6 of the Scanner for .NET fixes things? We just released v5.7 and it seems there might be a bug.