Since Windows update Mice and keyboard not working on some devices

[Theldron2.0]

Hi all,

 

Hope you are well.

 

Not sure if anyone else is having this issue but Windows updates installed on some PCs last night and now keyboards and mice will not work on those devices.

 

In device manager there is an exclamation mark on the keyboard and mouse and it says:

 

Windows cannot load the device driver for this hardware. The driver may be corrupted or missing.

 

An Application Control Policy has blocked this file.

 

We are using intune, it was working fine yesterday. I jumped on a random computer that was working, installed the updates, and then it stopped working. So it's definitely the latest windows updates causing the issue. I am just trying to roll back the updates as we speak.

 

But I didn't know if anyone else was experiencing this or just me?

 

Thanks

[Synkrox]

We've had a few lenovo laptops where the mouse has vanished over the last week - which I think is down to an update.

A power off and quick reset sorted it. (in our case holding power button down for about 20 seconds). Regular reboot might have worked but I just do this out of habit.

[DavR]

If you look in C:\Windows\System32\DriverStore, has the update installed any new USB drivers?

 

Sounds unlikely, but, we used to have this problem with one particular generation of Intel USB driver a while back. Every time we updated our drivers on SCCM with the new Intel Chipset Utility, it would reintroduce the bad driver again!

[Theldron2.0]

I have done some testing and we are using App Control for Business (WDAC), we are using the built in controls, Trust apps from managed installer (Which has been set as intune), Trust app with good reputation which has been set as disabled, as we don't want students installing anything.

 

This policy is deployed to all devices, so I excluded one particular room that has the issue, sync'd and restarted a couple of devices and the drivers became unblocked. Removed the exclusion, restarted the devices, drivers restricted again. So it seems like the policy does not trust the drivers, even though I think they are generic windows drivers.

 

How do people control these things, do you combine WDAC with applocker XML or use the WDAC wizard and add publisher rules?

 

Thanks