ESS hangs Lenovo Client Services/TPM

[kwg]

I'm experiencing the issue quoted below, first reported in the Beta forum. It prevents me from logging on to my Lenovo Thinkpad T62. For me, though, the situation is even worse than it was for SutterCane, because I can't even log on in normal Safe Mode in order to remove ESS. The problem began with a reboot following the installation of ESS 3.0.560.

In an attempt to circumvent the problem, I disabled the the embedded security chip in BIOS. However, I am still unable to log on to my computer at all, even in Safe Mode.

-{ Quote: "Had an issue with Beta 1a on my Lenovo Thinkpad T60, which has a Trusted Platform Module (TPM 1.2) Security Chip.

After the second reboot following installation of Beta 1a the Lenovo Client Services Solution software (which works with the TPM chip and fingerprint reader for authentication) would hang on the standard message "Checking the status of the embedded security chip". This had the effect of locking me out of the computer completely in both normal and safe mode with networking. I believe it was due to firewall component blocking local loopback connection between the software and services (or something like that). Yuck :/

Booting into standard safe mode worked, but normally you can't uninstall the software in safe mode since the Windows Installer service isn't running (brilliant). Simply disabling Eset service and startup didn't help either--still hung on reboot. Ultimately found and used this solution to enable the service:

http://channel9.msdn.com/ShowPost.aspx?PostID=194828

Once that was done, I was able to uninstall the Eset suite in safe mode then reboot and log in normally." }-

[ashishtx]

I had the same kind of problem back in 2006


http://www.wilderssecurity.com/showthread.php?t=116743

If you just "exclude" the encrypted folder from the antivirus scanning things should work out.

I hope, I am addressing your issue.

[kwg]

-{ Quote: "I had the same kind of problem back in 2006" }-

I've been running NOD32 without issue for the last two years. Like SutterCane, I think the current problem is a consequence of Eset firewall misbehavior. At present, my major problem is that I cannot even log on to my computer, even in Safe Mode.

[ashishtx]

Oops !!

[kwg]

-{ Quote: "Oops !!" }-

It's OK. :) Your suggestion was a good guess (since I hadn't given you more information).

[kwg]

I've managed to recover from the problem I described in the initial post. Here's what I did:

1. Booted from the Windows XP installation CD.

2. Used Recovery Console to rename the eset folder to _eset.

3. Rebooted normally into Windows. I experienced no problem this time (except, of course, that ESS didn't load).

4. Renamed the _eset folder back to eset.

5. Uninstalled ESS 3.0.560.

6. Rebooted normally into Windows.

7. Installed ESS 3.0.563.

8. Rebooted normally into Windows.

So far the problem has not recurred.

[kwg]

I've had a recurrence of this problem: Thinkpad T42 hangs during boot while "Checking the status of the embedded security chip." The only way to get the computer to boot completely was, once again, to use Recovery Console to rename the eset directory to _eset and then reinstall ESS.