Looks like we've been able to track this one down. We only see this issue in Windows 10 1809, our tests of 1803 can't reproduce this issue.
We've found the area of our code which handles this and we're not doing anything different, but our native-os calls are being handled differently at the OS level.
It's unclear if this is by design due to their changes or an unexpected consequence of something.