I've attempted a fix with the troubleshooter and it did nothing.
Same. It seems like everyone is having this problem. And not everyone is technical enough to use command line to manually fix this known issue.
Now it seems we are having to do MS work for them when this should have been programed in the update to begin with. You never know what those commands will do to your computer. I do not feel comfortable doing it since MS cannot even put the fix in their update.
don
I don't feel comfortable either, I genuinely hope microsoft fixes this ASAP because I do not want to mess with my laptop lke that.