DeviceSetupManager event 201/202. Help needed to check/fix registry

aardvark said:

By chance, if you have a Microsoft wireless mouse and have upgraded the driver recently, check this thread to see if a driver rollback will help clear those Event ID 200, 201, and 202 errors:

https://www.tenforums.com/drivers-har...ad-device.html

As far as the metadata link goes, mine is exactly the same as yours.

Ok, I checked event viewer and I have this error too: "The driver \Driver\WUDFRd failed to load for the device {C5A047D8-CB5B-40E9-B9E3-316AB06B5A18}\WirelessKeyboardFilter."

Before proceeding to roll back the driver, I have a couple questions.

1- Once I've rolled back to the old driver, will the new one (1.0.102.0) try to install itself again upon restart, that is, automatically?

2- In case Microsoft fixes this issues, how do I put back in place the more recent (1.0.102.0) driver? And is there a way to know if and when Microsoft will come up with a fix?

3- By any chance, did you select “No, let me choose what to do" and “Never install driver software from Windows Update” to prevent the new driver (1.0.102.0) from being installed again? That would explain the absence of DeviceSetupManager errors. These options are located at Control Panel > System and Security > System > Advanced system settings > Hardware > Device Installation Settings.

Thank you for your precious and invaluable help. Hope you can answer my questions

Following aardvark advise I got rid of Event 219 "The driver \Driver\WUDFRd failed to load for the device {C5A047D8-CB5B-40E9-B9E3-316AB06B5A18}\WirelessKeyboardFilter."

Yet errors with Event ID 200, 201, and 202 still persist. This is possibly because i did not select “Never install driver software from Windows Update” beforehand, and the system keeps checking for updated drivers as it is supposed to do. So, apparently, that is not a solution for the specific topic of this thread.

Can someone else please check his/her registry and see if these values for "Device Metadata" are correct? Do you have the exact same data as in the image below? The key is located at "HKEY_LOCAL_MACHINE > SOFTWARE > Microsoft > Windows > CurrentVersion > Device Metadata."



I would also like to know if you are or are not experiencing Event ID 200, 201, and 202 errors. And if you altered the options in Device Installation Settings

aardvark said:

Sorry you didn't find my information helpful. BTW, what I proposed "IS" the solution to your problem. And, there is a simple way to prevent "only" that wireless driver from being auto updated. Unfortunately, I went to sleep and your impatience got the best of you.

Thank you very much aardvark!

Upon third-fourth reboot it seems the annoying 200, 201, and 202 events are finally gone. As you rightly suggested, it was a matter of patience. Thank you again for your precious help, and for your kindness. Let me wish you a beautiful and blessed day.

For anyone interested, the comprehensive solution to this issue can be found in a thread by aardvark at this link

https://www.tenforums.com/drivers-ha...ad-device.html

Also, in order to prevent the more recent driver (1.0.102.0) from reinstalling itself, the Microsoft "Show or hide updates" tool is required (see post #6 by aardvark)

http://support.microsoft.com/en-us/kb/3073930