New
#10
It is now 6 months since ms pushed bad update....finally acknowledged 'they' had a problem 2 months ago. Is it fixed with an update? I have 2 different devices upgraded from 8.1 pro to 10 pro with this issue. Spent days trying many different fixes(even ms tech support had NO idea!) and then returning to 8.1 pro. Lets hope they have replaced their QA department...oh probably never had a department to start with!
So here we are in July and evidently not fixed, at least in the production build, because I got this today. Like others, drove me nuts for awhile. Hopefully it goes away in the anniversary release. Honestly, based on everything I have read, this should have been an easy hotfix sort of thing rolled out with a security release.
At least for me, it makes me question any error I get now. Makes it very hard to troubleshoot an issue if they have you snipe hunting. Honestly expected more from Windows 10, and Microsoft, by this point.
...with the last updates from ms on 07/12, the problem is still not fixed on my two 10 pro devices...real shame they can not get it together...now 8 months since ms broke their flagship with Threshold...BUT hay, they bought LinkedIn!
NOTE to ms: 'just buy a real software company'...please.