Windows 10: Missing helloface.inf and recognition.inf

Hello,I have a brand new Dell XPS 9305 laptop with windows 11. Windows Hello says 'we could not find a compatible camera'. I have tried all the fixes known I think but it seems the lack of the two files within the windowsbio folder means a bigger issue. No idea how to get them. I have updated all drivers via Dell and Windows Update so not sure what is left to do but I assume I should have this feature? Thanks.

:)

 

inf file access

WIN 10 home 64

I have an .inf file in windows/sys32/driverstore/....

can't get access to update a couple of lines to enable driver recognition on my DAW console

I have installed a file unlock app, still can't get sys access

what are my options?

 

Install Option Missing From .INF Files 2020

Hi Cla_Tronix,

Thank you for bringing this concern to us, my name is Anthony I am an Independent Advisor and a Windows 10 OS user like you.

I understand that there concerns install options missing in .INF files.

Please let us work together to find the a solution for this issue.

Let us use these troubleshooting steps provided on the bellow

Install Option Missing From the Context Menu of .Inf Files

whttps://answers.microsoft.com/en-us/windows/forum/windows_vista-hardware/install-option-missing-from-the-context-menu-of/23524ad3-1687-4c2d-ba26-b249b4c4d8e9here

Please let me know on how I can provide further assistance Cla_Tronix, I would do my best to provide further help.

Thank you again for posting this concern , I am glad we where able to work together with this issue.

Please continue to be safe and have a good day.

Best regards,

Anthony De Jesus

Independent Advisor

 

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.