Having the exact same problem. I only updated to W10 today and I suspect that during the installation updates were automatically installed so the troubleshooter thinks that it has been fixed already....