Windows 10: error " mtkbtfilter.inf: Successfully added oem45.inf and installed on 0 devices " in...

Hello i have some problems with connecting devices through Bluetooth to my laptopso I'm trying to update my drivers updating automatically didn't work cause it didn't change any of my Bluetooth driversso i tried installing manually by downloading the driver from acer official website and i searched my laptop module by SIND so i think drivers are compatible and installed them by install driver button in device managerand i got this error :mtkbtfilter.inf: Successfully added oem45.inf and installed on 0 devicesbut there is no new drivers shown in drivers list actually i couldn't insert the

:)

 

Does "Intel INF" ever really install anything?

I'm trying to find out if I have the latest chipset drivers. I'm more stubborn than skilled, I hope someone here knows more about how drivers work.

Take first, as a simpler and more straight-forward example of how I thought it always worked, the most common Realtek LAN driver. In the downloaded package, in the same folder as the .inf file (rt64win7.inf), there also is a .sys file (rt64win7.sys) which I assume is the driver, and there also are 2 DLL files (RtNicprop64.DLL and RTNUninst64.dll) and I can guess they are used for viewing properties and uninstall. If I look at my NIC in the Device Manager, under Drivers / More Info, these 3 are listed as the driver files. Also, if I look in rt64win7.inf, there are references to all 3 mentioned .sys and .dll files (e g under heading [SourceDisksFiles]). So it all makes sense.

There are 2 chipset drivers. The ME driver seems understandable. But when it comes to Intel INF installer, there are several things that to me look like they are never used:

The downloaded package consists of only .inf and .cat files, no related code (as in .sys or .dll files).
If I run pnputil.exe -e, make a list of all oemXX.inf files that say "Intel", and open these in C:\Windows\Inf, then I can see the files from Intel that are actually being used, including the original file names (before Windows renamed them to oemXX.inf). And from that I can see that the .inf files in use never are the ones that came with the Intel Inf package (the used drivers I guess are something Microsoft found)
If I compare all .inf files in the downloaded Intel INF package with all .inf files in C:\Windows\System32\DriverStore\FileRepository, only 3 are in common: cougcore.inf, cougsmb.inf and SNB2009.inf. But in these, there are no references to any .sys or .dll file, and under the heading [SourceDisksFiles] it is just blank.
Looking closer at what driver is used for the SM Bus: In Device Manager I see that it uses intelsmb.sys (and intelsmb.inf, via Info / INF name), and that the device's ID is 1C22. I think the Intel INF installer is supposed to match that ID to what devices the .inf files list that they support. Now, with the Intel INF package there came a newer driver for the SM Bus, cougsmb.inf. Both cougsmb.inf and intelsmb.inf are in the FileRepository directory, so it looks like the system has tried to install them at some point. And in both these .inf files, 1C22 is listed under "supported devices". The cougsmb.inf is newer, and it is specifically for Cougar Point chipsets, which is what is on the H67 chipset boards like mine. Still the system uses intelsmb.inf.

So it looks like my system uses old chipset drivers (probably whatever Microsoft found at the original install), and that the files that should install new drivers are empty.

Am I missing something?

PS Running Win7 64bit with i3-2100 and H67 chipset.

 

oem157.inf oem158.inf blocking Windows 11 upgrade

Repeated attempts to upgrade from Windows 10 to Windows 11 have been "hard" blocked by XPS and PDF drivers oem157.inf and oem158.inf. This exact scenario has been reported/documented before with early upgrades to Windows 10. The documented solution steps from this historical issue have not been successful in resolving my current Windows 11 upgrade failures.

XPS and PDF features have been disabled. Every primary and secondary reference linked to oem157 and oem158 has been removed from the registry and the oem157 and oem158 files removed from the Windows/INF folder, yet the Windows 11 upgrade continues to fail with 0xC0900209 error which is caused by oem157.inf and oem158.inf. DISM and SFC have been used to no benefit in this issue.

Would the existence of the prnms001 and prnms009 folders/files in the Windows/System32/DriverStore/FileRepository folder cause the Windows 11 upgrade to be blocked by oem157 and oem158? Are there other items that need to be "cleaned" of the XPS and PDF driver references to allow Windows 11 upgrade to be successful?

Thanks for any suggestions.

P.S. XPS and PDF printer devices have all been deleted.

 

Touchpad (or mouse) INF file

Hi Dave,

I could find "msmouse.inf" under the Events tab in the past and actually inserted this INF file. But, it doesn't load the touchpad driver. It seems to load "mouhid.sys" but for some reason, it doesn't show a mouse pointer on WinPE. Thanks for your suggestion though.