WU is showing me a driver update which I would like to install manually. The update is a cab file with the following files in it (AuthenTec driver update for TouchChip Fingerprint Coprocessor) Code: tccoinst.dll 20440 2/28/2013 tcwbf .dll 1014880 2/28/2013 tcwbfadv.cat 12273 5/31/2013 tcwbfadv.inf 11970 2/28/2013 ufma .exe 59560 2/28/2013 upkbu .dll 3742856 2/28/2013 WdfCoInstaller01009.dll 1721576 2/28/2013 WinUSBCoInstaller2.dll 1002728 2/28/2013 WUDFUpdate_01009.dll 2152176 2/28/2013 If I try and install the inf from its context menu, I get "the inf file you selected does not support this method of installation" Same thing if I use InfdefaultInstall.exe If I try and update via the device manager context menu for that device, I get "The folder you specified doesn't contain a compatible software driver for your device" The only way the driver gets installed correctly is to let WU do it. Does anyone know what WU runs to install this driver?
I'm guessing here, but I think WU uses DISM to install drivers on live system, so you use the cmd below to install the driver and see if that helps:- Code: dism /online /add-driver /driver:X:\ Where X is replace with drive letter that the driver is stored on, and adjust the path to the location where you stored the driver!
I forgot to mention that I also tried pnputil and devcon and both gave errors. I tried pnputil again to try and uninstall the device and it did not uninstall. I tried the -f parm and all that did was delete the inf file. The device was still shown as installed in device manager. Uninstall only works from Device Manager. I've used pnputil for other inf files which worked fine, but this one looks like it needs another program to install it. I haven't been able to find out what though. I've attached the inf and setupapi.dev.log. Maybe someone can make more sense out of it then me to get this thing installed manually. View attachment setupapi.dev.txt View attachment tcwbfadv.txt If there's a more suited forum for this kind of problem, please let me know.
They were sold to Apple for 356 million back in 2012. The point is that Windows Update knows how to install it and I'm just trying to find out how I can do this manually.
I always make drivers available for later installation which shows in WU by following way When any drivers are installed it first downloaded in C:\Windows\SoftwareDistribution\Download First step it downloaded raw files Then it starts to install it At this point i Pickup folder named install which contains drive setup which can be used later on same hardware and architecture. I successfully pick up Intel display drivers,some HP modem drives ,etc if drivers are small in size u will get very short time to copy that folder and paste to another location. U can try this way.
pnputil will error if the drivers installed is newer, or the dev id does not match, or if the one you are trying to install is not signed. Also -f will only force uninstall the driver, if you want to delete the device try devcon (I think you can do it with this) Post your hardware id let me see what I can find (I am pretty good at locating the latest driver)
Rick, This is what what happened when I used pnputil. No error, but only the inf gets created. The device is still not installed properly. The hardware id is listed in the setupapi.log I attached which is only for the install of the biometric coprocessor. In the log I see a drvinst.exe mentioned, but can't find much info on it. Below is an image from device Manager Code: C:\>pnputil -i -a D:\@Drivers\$T60\W7\BioCoprocessor\tcwbfadv.inf Microsoft PnP Utility Processing inf : tcwbfadv.inf Successfully installed the driver on a device on the system. Driver package added successfully. Published name : oem15.inf Total attempted: 1 Number successfully imported: 1 Device ids
Oh Sh*t, I just noticed that the driver from Windows Update Catalog which is supposed to be for Architecture: AMD64 , IA64 , X86 has an inf file that is set up for AMD64. All this time I was trying to install the inf for %Mfg%=Models,NTAMD64 instead of %Mfg%=Models,NTx86 Pnputil accepts both inf files without throwing an error, but will only properly install the inf with the correct architecture specified which I was not using. Arrrrgh Sorry for the false alarm.