Essentially, upon each new version or build deployed the problem reoccurs and this is how I correct things to date. Been down the road quite a bit.
Your mileage may vary with those 'restore points'. I have not done restores, nor ever intend to waste such time in troubleshooting issues. It solves nothing. You need a support IT person if you need help beyond these posts. The info is posted for anyone searching terms of this problem with search engines.
MS must solve this debacle. They are not answering this community forum post - their preferred support method - besides $$$, the method they really want from users. That costs a lot in time (like I take & Microsoft's too) and that is unfair.
Good Luck. If I find a cure, or the problem gets fixed in a new build it will be posted. Like I said I am an Insider with Fast build deployments set to test new Windows 10 that you eventually get.
I post a Yes/No evaluation on 'Ready for use' each time on the build. So far it is all NO's because of this and many more Win 10 snafus. There's a lot more Insiders who probably are working elsewhere...
