ERROR: Fingerprint Software Error (No Longer Working)

Passwords can be forgotten (less likely but probable); biometrics can never be forgotten. This is obvious and although subject to debate and arguments, techie folks prefer to use technology and its features. Afterall, this is your money's worth. Fingerprint credentials are often deployed. This used to be prevalent to notebooks and laptops, but now even the smartphones have it.

This is the case for me. But then again, technology can fail too. And I have experienced this firsthand on my company issued Lenovo T420. The fingerprint sensor did not light up, and I could no longer use it. The error is saved on a screenshot below and I will share how this got resolved as well.

Error Code: E7210001

The Error Code is "E7210001" (The service cannot be started, either because it is disabled or because it has no enabled devices associated with it). Scouring the web for solutions didn't produce much results.

One of the results from the web indicated to check that the service "Credential Manager" is started and its Startup Type needs to be set to "Automatic". A few people indicated the service was stopped and manually running it resolved their issues. This was the first thing I checked and it was on the recommended setting -- which is a dead end.

Since the error message did not mention a particular service it is looking for, the trial and error starts. Lucky for you that will no longer be the case.

There is another service that needs to be running in order for the biometrics to work. And just as the name states, the service also contains that string as a hint -- Biometrics. It is the "Windows Biometric Service".

Windows Biometric Service

Check that both the "Credential Manager" and the "Windows Biometric Service" are running (or Started). This will return the functionality of using fingerprint credentials or biometrics for logins. I did not go as far as finding out what caused the services to be Disabled. That would be interesting but I simply don't have the time.


INFO: Sickbeard Torrent Fork on PCH-C200 (Update)

It has been a while since I last composed an article in this blog. I have been busy planning, travelling and implementing infrastructure changes in my secular job. Time seems to have flown quite fast.

Regardless, I have had a few hours to myself and decided to tinker with my aging yet still functional Popcorn Hour C-200. I can't believe it has been in service for over ~5 years. The mods I did on the original heatsink really paid off.

If you have noticed, the development on the "bricky" fork of Sickbeard has discontinued and its git repo has been taken down. Time to update the sickbeard application on my C-200. I still prefer to use a torrent fork of the original code.

The previously written article on the sickbeard "bricky" fork still applies. However, a few tweaks are needed.

The initial steps to follow are the same:

[1] Open a terminal connection via KiTTY or another utility. Browse the directory /share/Apps/sickbeard. All the other steps below will discuss about changes to files and directories relative to this path.

[2] Remove the directory .git. Do this so the bricky fork will not conflict with the original midgetspy version of sickbeard. I also removed the file .gitignore but this seems irrelevant. You may opt to remove it in this step.

[3] On the same directory /share/Apps/sickbeard, is the file Look for the line:
git clone git:// SB
.. change it to this line:
git clone git:// SB

(The rest of the procedure is similar and I still included them below.)

[4] Remove the directory autoProcessTV under /share/Apps/sickbeard. If you don't want to remove it, you may choose to rename it instead. Any arbitrary name aside from the original name will do.

[5] Execute on the command line. Either of these commands will work:
/share/Apps/sickbeard/ install
.. or
cd /share/Apps/sickbeard; ./ install

[6] Once the git clone is complete, run this:
/share/Apps/AppInit/appinit.cgi start sickbeard

The end result was not as I expected it to be. What I thought was a seamless update resulted in errors. The error is in the screenshot below.

ImportError: No module named _cpcompat

ImportError: No module named _cpcompat

As it turns out, the old directory where sickbeard was installed contained a folder named "cherrypy" that comes in conflict with the version the current version of sickbeard. The solution is to remove the "cherrypy" folder and the errors go away. This is the only other step to add.

Those who still have a working C-200 will enjoy this new version of the torrent fork of sickbeard.


Subscribe for Latest Update

Popular Posts

Post Labels

100gb (1) acceleration (1) acrobat (1) adblock (1) advanced (1) ahci (1) airdrop (2) aix (14) angry birds (1) article (21) aster (1) audiodg.exe (1) automatic (2) autorun.inf (1) bartpe (1) battery (2) bigboss (1) binance (1) biometrics (1) bitcoin (3) blackberry (1) book (1) boot-repair (2) calendar (1) ccleaner (3) chrome (5) cloud (1) cluster (1) compatibility (3) CPAN (1) crypto (3) cydia (1) data (3) ddos (1) disable (1) discount (1) DLNA (1) dmidecode (1) dns (7) dracut (1) driver (1) error (10) esxi5 (2) excel (1) facebook (1) faq (36) faucet (1) firefox (17) firewall (2) flash (5) free (3) fun (1) gadgets (4) games (1) garmin (5) gmail (3) google (4) google+ (2) gps (5) grub (2) guide (1) hardware (6) how (1) how-to (45) huawei (1) icloud (1) info (4) iphone (7) IPMP (2) IPV6 (1) iscsi (1) jailbreak (1) java (3) kodi (1) linux (28) locate (1) lshw (1) luci (1) mafia wars (1) malware (1) mapsource (1) memory (2) mikrotik (5) missing (1) mods (10) mouse (1) multipath (1) multitasking (1) NAT (1) netapp (1) nouveau (1) nvidia (1) osmc (1) outlook (2) p2v (2) patch (1) performance (19) perl (1) philippines (1) php (1) pimp-my-rig (9) pldthomedsl (1) plugin (1) popcorn hour (10) power shell (1) process (1) proxy (2) pyspark (1) python (13) qos (1) raspberry pi (7) readyboost (2) reboot (2) recall (1) recovery mode (1) registry (2) rename (1) repository (1) rescue mode (1) review (15) right-click (1) RSS (2) s3cmd (1) salary (1) sanity check (1) security (15) sendmail (1) sickgear (3) software (10) solaris (17) squid (3) SSD (3) SSH (9) swap (1) tip (4) tips (42) top list (3) torrent (5) transmission (1) treewalk (2) tunnel (1) tweak (4) tweaks (41) ubuntu (4) udemy (6) unknown device (1) updates (12) upgrade (1) usb (12) utf8 (1) utility (2) V2V (1) virtual machine (4) VirtualBox (1) vmware (14) vsphere (1) wannacry (1) wifi (4) windows (54) winpe (2) xymon (1) yum (1) zombie (1)