Enable Camera for Windows Hello

V

vinconti

New Member
edit nm got it. I guess I still can't figure out how to get NTLite to post-setup install things with OEM key and thought something was installed that wasn't.


I am beginning to suspect this might not be an NTLite thing so my apologies, but maybe someone here can help anyway? I have a thinkpad yoga g8 with the IR front facing camera, trying to get the face sign-in with windows hello working. I read you need Virtualization Based Security, but I still can't get it to recognize the camera. I loaded all the drivers, and went so far as to just not even remove anything from the windows image, only to add drivers, but the Facial Recogntion still reports "This option is currently unavailable".

Any ideas? TIA
vin
 
Last edited:
The whole 'Windows Hello' thing is a pain in the backside. Personally I get the same with my fingerprint reader on the latest build of windows (clean install ), so i think it isn't really an NTlite thing, it is more of a microsoft thing. i always find that even when drivers are installed, it says ' device not recognised , or , not available at this time ) , but once i hit the update button, voila, it starts working.
 
This preset doesn't list any removals or changes, unless those steps were done in a different session.

I'm not sure you're adding drivers the right way. The usual method is to extract drivers to staging folders, and add those folders in the Drivers page. AFAIK VBS isn't required for normal Windows Hello, it might be different for Windows Hello for Business since that's an Enterprise feature.
 
garlin said:
This preset doesn't list any removals or changes, unless those steps were done in a different session.

I'm not sure you're adding drivers the right way. The usual method is to extract drivers to staging folders, and add those folders in the Drivers page. AFAIK VBS isn't required for normal Windows Hello, it might be different for Windows Hello for Business since that's an Enterprise feature.
Click to expand...
yeah, this preset was just testing to see if *any*thing I was doing was breaking it, I intentionaly didn't make any removals or changes. and I might be installing the drivers wrong, still figuring this program out, but how you described is exactly how I had been doing it, download all the executable installers from lenovo, manually select "extract only" in the UI of the exe installer, and stick them all in a directory, which I then select to add in the drivers page. I believe it works, when I tried to install win11 by stock methods before running it through ntlite to add drivers, it couldn't find my NIC or even my ssd (sometimes), but the NTLite with slipstreamed drivers it could find all that stuff.

Fixing the windows hello camera required some combination of manually running the installers for some combination of trusted platform, system interface, 3 different camera drivers, and several other exe files that were available from Lenovo driver page, but look like they did more than just install drivers. I thought if I had run them post-setup that would work but doesn't look like it did. As I said I still have to dig into the unattended setup, assuming there is still that issue where OEM keys break the post-setup scripts? they seem to for me (apps get installed fine on virtual machine but not on physical machine).

my belief that it had something to do with virtualization based security came from here https://learn.microsoft.com/en-us/w...ences/windows-hello-enhanced-sign-in-security but you very well may be right and I am not sure I needed that stuff. Might experiment more later

thanks all!
 
Lenovo's have OEM keys, so look in the Unattended page's toolbar and check OEM SetupComplete to force execution of Post-Setup commands.

If you haven't made any changes, VBS should be enabled by default -- unless you have non-compliant device drivers or have disabled SecureBoot. Presuming you're using the official Lenovo drivers/installer, I don't see why it shouldn't work.
 
Hey everyone, following up on previous post (new thread with new info). I cannot for the life of me slim down my windows and keep my Windows Hello facial recognition. Attached are two reset XMLs, the fat one works and the slim one does not work. I absolutely cannot figure out why.

I can see Windows Hello face needs VBS and TPM 2 ( https://learn.microsoft.com/en-us/w...ences/windows-hello-enhanced-sign-in-security ) and as far as I can tell, everything that even could possibly be needed is left in. Does anyone have some clever way of tracing dependencies, or figuring out why something isn't working, that doesn't involve simply making hundreds of variations of of ISOs to try?
 
Your first preset doesn't reveal any fresh details, because there are no removals. My suggestion would be to restore 'Device Experience'. Your Lenovo software might have a hidden dependency on other Windows components to run.

If someone doesn't share the same HW as you, it might be difficult to trace any system errors blocking Windows Hello. You could end up having to do this by trial & error in controlled batches.

Delete a block of around 20 consecutive removal lines in the preset, then make a new ISO. If that doesn't work, repeat and delete the next 20 removals (skipping the languages & keyboards). When the camera finaly does work, you will have localized the problem within the most recent set of removals.

Now divide and conquer and split that section in two 10-line blocks. And so on until you've figured out what the offending component is.

When removals are done in batches, less time is spent trying to guess what's broken.
 
if anyone else runs into this, removing one or more of the following broke the windows hellow face login.

<c>trkwks 'Distributed Link Tracking Client'</c>
<c>troubleshootingsvc 'Recommended Troubleshooting service'</c>
<c>unp 'Universal Notification Platform (UNP)'</c>
<c>waasassessment 'Windows Update Medic Service'</c>
<c>webclient</c>
<c>winai 'Windows AI Machine Learning'</c>
 
Pretty sure it's not Troubleshooting Service (standalone diagnostic wizards), WU Medic Service (self-repair for Windows Update), or AI Learning (which didn't exist until recently). Thanks for the follow-up.
 
oh and it also wasn't the distributed link tracking client, so if that is true than it is Universal Notification Platform or webclient that is necessary. BTW in case it helps anyone, I am sure there is an easier way but the way I saved some time with making sure my windows directory was clean after 5 million operations on it was to extract a stock ISO to a folder, then remove system write and modification security privs on it, and write small cmd file that just deleted and recopied a fresh one every time. I use %cd% instead of drive letter because those change on partition deletion and recreation during install.

rmdir /S /Q %cd%NTLite\vin-data\winscratch-refresh-every-time
md %cd%NTLite\vin-data\winscratch-refresh-every-time
robocopy %cd%NTLite\vin-data\winscratch-source_do-not-edit_copy-only\ %cd%NTLite\vin-data\winscratch-refresh-every-time /E
 
You must log in or register to reply here.
Back
Top