Was from another beta that I am involved with running on windows 10. Was an issue on Microsoft's side and our developers received word from Microsoft that "The issue HAS been fixed in build 10102" and to test it out. Which of course I replied to them that that build has not been released to the public as of yet and will do so once it has.