Solved this problem with a temporary fix, I was able to resolve this issue. This problem appears to be limited to version 1809, and Microsoft plans to address it in a future update.