I have recently had this happen in Windows 10 Beta 0.13.0. Should I continue here or start a new bug report?
I have recently had this happen in Windows 10 Beta 0.13.0. Should I continue here or start a new bug report?