Windows Hello (PIN) - Activate with NTLite?

Does Windows have to be activated to use Windows Hello? My testing VM is not activated because I only have the one licenses for my physical machines.
 
Hammer of the Gods said:
I think you can see why I'm confused after seeing my preset. The only thing I thought it might be was UAC as well, but apparently not. Nothing else related to login or "biometrics" was disabled abart from picture password, which has it's own component check mark and no dependency, so I don't think that would cause the issue either.
Click to expand...
This is a standard debug step, remove any [suspect] Settings customizations to retest if a problem originates from Settings or removals.
 
I'd also eliminate excess variables so we can know for sure if the preset is even the culprit, as well as eliminate the possibility of file corruption. Here's what I would do to achieve this:

1) Make a new image by taking an unmodified Windows and integrating the windows updates you want, then process the image without any other tweaking (do not add your preset or anything else whatsoever).

2) Edit your XML file and remove the windows updates from it by deleting the lines between the <Packages> code.

3) Once the first image has finished processing, load it into NTLite again and now import your edited preset, then process that. Do not add any post-setup stuff you mentioned previously (registry tweaks outside of NTLite, install scripts, etcetera) as we need to rule those out.

4) Install this second image which has only your windows updates and NTLite preset, and see if the PIN issues persist.
 
Hammer of the Gods said:
Alright. Setting that up now then building and loading to VM.
Click to expand...
Just an idea.
If license is machinebound try make some space on another partition and install your NTLited version here instead of VM for testing.
Not sure it'll work - but maybe a try worth if HELLO demant a licenced version - and of couse if Windows licensing method is working on 2 separate installed Win installs on the same license machinebounded PC/ laptop.
Normally a PC come with a license bound and you can't update to a never WIN version without upgrading a already installed/ PC born WIN version, ie. from 8-8.1-10-11.
To say - if installed 10 and trying to install 11 as new install - your license won't work - you're bound to updating/ upgrading and you license will still work.
Or to say - if buyed a W10 PC with license and want to install a W11 clean is not possible - you can upgrade to W11 and keep the license.
If upgrading on a liveinstall - and use NTL on the liveinstall (take a backup before try just in case) - as said just an idea for a solution.
 
Sorry for the delay, I needed a break from all this Windows crap. I'm back to testing. Before going around troubleshooting my preset, I first tried installing my base unmodified Win11 image. It has the same issue, so the preset is not the culprit, or at least not the only culprit. Have not tried installing on baremetal yet. Don't really have a good place on my drives to do that yet.

Edit: Found a video saying Hyper-V enhanced session could be the culprit and switching to basic session could fix it. Tested on unmodified image as well as my own. This was the issue. Switching to basic session fixed the issue, which means it should not be a problem once I install it on baremetal.
 
Last edited:
You must log in or register to reply here.
Back
Top