Our problem here isn’t duplicate drivers, but tons of unused drivers that are applicable to different models. Most of those seem to work by deleting old versions of duplicate drivers. Anyone know how I can tell via powershell (or some other way that I can automate) what drivers are currently being used, so I can wipe the garbage off these machines?Įdit: To be clear, I know there are tons of scripts out there to cleanup drivers. But after days of Googling, I can’t find anything to point me in the right direction. So Windows has to have a way to tell me what drivers are being used - disk cleanup is able to figure it out. Right now we have over 1700 drivers in our image, and we have multiple models, so I can’t just build a list of good drivers for each model and remove the remaining. Power shell can get me a list of drivers, but I can’t find a field that tells me if the driver is in use or not. Disk cleanup works great to get rid of them, but of course the driver cleanup isn’t an option in sageset, and I can’t manually run disk cleanup on 3000+ machines. Then navigate to Display adapters, right click on your GPU, and select Properties. Search for Device Manager in the search bar and open the utility. So now we need to apply the 1909 update, and the extra 20gb in drivers is starting to cause problems. Device Manager is one of many tools for configuring devices connected to your PC, and it can update, rollback, and delete drivers. If anyone ever suggests this as a way to speed up deployment, don’t do it. Bad idea, but someone did it and now we are stuck with it. A decision was made that, to speed up the deployment process, we would save all possible drivers for each model in the driverstore on the wim. We reimaged all of our machines for the Windows 10 upgrade last year, since we were replacing most of the hardware anyway. I have a weird scenario I am hoping someone has some insight on.
0 kommentar(er)
