Question Driver error : Desktop - Drivers And Printers

[donis1]

When i open Devices And Printers I see Driver Error over desktop icon. When i check Device Manager I see no errors. Any ideas why i get this and how to fix it?

D

 

[Lutfij]

For the sake of relevance, what version of Windows 11 are you on?

When posting a thread of troubleshooting nature, it's customary to include your full system's specs. Please list the specs to your build like so:
CPU:
CPU cooler:
Motherboard:
Ram:
SSD/HDD:
GPU:
PSU:
Chassis:
Monitor:
include the age of the PSU apart from it's make and model. BIOS version for your motherboard at this moment of time. Listing your peripherals also helps shine some light on your issue.

 

[Ralston18]

@donis1

In Device Manager did you also check for hidden devices?

Device Manager > View > "Show hidden devices"

Also, for starting purposes, look in Reliability History/Monitor for any related error codes, warnings, or informational events.

 

[donis1]

@donis1

In Device Manager did you also check for hidden devices?

Device Manager > View > "Show hidden devices"

Also, for starting purposes, look in Reliability History/Monitor for any related error codes, warnings, or informational events.

Hi Ralston

I just checked hidden devices and non errors to see there. I also checked Reliability History and found some error regarding windows update so did a manual update.

I still have same driver error in Devices And Printers. When i click it i see Troubleshooting needed. Last days we had some USB issues where USB disconnect and connect at times. I not see any errors for any USB any place.

D

 

[Ralston18]

Take a "deeper dive".

Use a Powershell cmdlet to look at what devices are being sensed/found.

Specifically the "Get-PNPDevice" cmdlet. Run as admin.

Reference:

https://learn.microsoft.com/en-us/p...evice/get-pnpdevice?view=windowsserver2025-ps

The cmdlet results may be lengthy but easily scrolled down the list.

Look for both devices that you expect as well as devices that you do not know or recognize (Unknown).

You can also use the Get-WindowsDriver -Online -All cmdlet in much the same manner.

Note: the cmdlet may take a bit of time to run and complete. And will be lengthy - scroll through the results (no need to rush) and get a sense of it all. Then go back and look again for anything that seems amiss.

= = = =

Also, after reading back, have you tried using "dism" and "sfc /scannow" to look for and fix buggy or corrupted files?