i just thought i'd let someone know that after spending 2 days now.. loading, unloading, and restoring my brand new 1500 dollar hp tx2z 1300 laptop with biometrics built into it.. i finally.. at long last finally.. found out PRECISELY what was causing my fingerprint reader to fail to work on boot up for windows login.. then fail to be usable once inside windows as well.. until i killed the application that runs my password management software tied to my AuthenTec AES1610 biometric scanner that's built into my BRAND NEW laptop... then opened services.msc.. found the biometric authentication service, restarted the service.. logged off the pc.. and then the scanner was fully functional and useable. turns out.. it's the craptacular firewall that's been added to ESS... i remove the firewall or completely disable it.. and my scanner works PERFECTLY.. i attempt to add rules to the firewall or put it in learning mode or anything else.. if i turn the firewall on PERIOD.. it kills my scanner again.. now i've been an eset fan for many years as i've seen it kill/clean things that NOTHING else will... but this is simply unacceptible. i didn't drop 1500 bucks on a laptop with biometrics for ess to decide to muck up the mix bc either it's windows 7 home premium, or bc eset hasn't updated their software to be completely compatible w/ 7 w/o it screwing things up or bc eset simply can't design a decently working firewall. and i say the last thing bc this isn't the first unit i've had issues with eset's firewall on.. both on vista home premium and vista pro systems as well. just to make sure i'm not accusing the wrong program, i've now restored a laptop i've had all of a week.. 3 times.. each time replicating the problem by simply installing ESS.. so sadly, i've had to resort down to a trial of standard nod32 antivirus bc it' doesn't have the craptacular firewall that is mucking up my new laptop. i've also attempted authentec driver updates, digital persona software updates, and etc etc etc.. it all comes down to ESS's crappy firewall. i was considering going and simply ordering a 2yr ESS license to renew the existing to go with the new laptop.. but after the headache and hassle this has caused, until you guys decide to actually FIX this issue.. you won't be seeing another dime of my money as this is simply unacceptible. and to those nay sayers out there who wanna blame hp... blame the other software or drivers that hp is using.. etc etc etc.. sorry, been down that road.. explored the options.. and this is neither hp or microsoft's fault. this is all on you guys.