May 29 2019 06:58 PM
So, I've placed this issue on the feedback hub and apparently this has been read by Microsoft. That was about a month ago. Does anyone have any solutions to this error because I doubt this issue will be fixed as I am still stuck on build 18865
