This is due to MS just released a new version of windbg -- it is different from https://github.com/Vector35/debugger/issues/1082
This is due to MS just released a new version of windbg -- it is different from #1082