u/AKGeek

We have been fighting update KB5089549 (at least i think) that has stopped some niche software for some clients from installing their drivers and stopped already installed drivers from working. From the looks of things the 100 hour audit didn't take place or failed to take in account the drivers from a few of our clients.

Anyone else experiencing this? Any workaround on this? Since its included in the cumulative update there is no way that I know how to exclude just that one KB.

The official way (ACfB policy) I am not certain is a scalable way of handling this across all the orgs we manage long term.

So far its been a niche CNC program, radio diagnostic program, and someone's ancient scanner (I told them its time to buy a new scanner).

My only current workaround for the one work stoppage this caused is to install an offline PC and install the software on it so it can communicate.

EDIT: Chatted with Practicam to try to get this resolved. Got all the way to one of the owners. He stated that they are seeing this issue on other computers. One was able to build an exclusion for the driver and another he stated was caused by the RMM and asked if we would remove our RMM from that particular machine. I stated that for long term that is not a solution and while we have some security checks we would have been alerted to such a block or removal. I built a computer from an old Win 11 image without any of our tools and the software worked fine. We also had a VM in our lab we forgot about without our tools but did have the most recent updates and it gave us the error for their driver installer.

He then asked us to disable defender, firewall, and a bunch of straw grabby things. He also stated he cant reproduce the issue on their side...

The error with that particular software is their licensing module that uses a driver. Windows pops up with an error message stating that the driver can't be installed because its not signed.

I just hope he gets the driver signed so our client can continue to work.