Posted 03 May 2018 - 10:31 AM
One can always initially try going into Device Manager and hitting the button noted in the screenshot below:
as the first thing to try to see if it solves the issue. It's difficult to know what version of Win10 is involved without having run the winver command since we're right at the cusp of a new version and we don't know when this work was done.
It would also be most helpful if you were to publish a Speccy system snapshot and provide the web address for it in your next reply. Here are downloadable step-by-step instructions for doing this:
- Using Speccy, PDF Format
- Using Speccy, MS-Word Format
Edited by britechguy, 03 May 2018 - 10:41 AM.
Added Speccy information
Brian AKA Bri the Tech Guy (website in my user profile) - Windows 10 Home, 64-Bit, Version 1803, Build 17134
. . . the presumption of innocence, while essential in the legal realm, does not mean the elimination of common sense outside it. The willing suspension of disbelief has its limits, or should.
~ Ruth Marcus, November 10, 2017, in Washington Post article, Bannon is right: It’s no coincidence The Post broke the Moore story