(Let me preface the question with Yes, I have seen similar questions, but not exactly my scenario.)
My environment is
Microsoft V
This is a bug in EF6.3 which is already fixed and included in 6.4.