This sort of resolved itself on its own after the windows 10 cumulative update for Insider preview 14986. Big thanks for the support staff here for the overwhelming response to an issue I would have paid to fix.