Problem with latest Fingerprint s/w update (to version 5.5)

[christopher_wolf]

Hi, thanks for replying! It's ashame that the software installer or the system update 2 can't help to solve this problem. Guess I will have to email Microsof to have them send me the hotfix.

This is because of licensing... the fix isn't available online via Microsoft.com either. Because it's not released...it's only given when asked for, and you have the problem it fixes. It hasn't been "fully tested". I'm 99.999987% sure it's more Microsoft not willing, than IBM/Lenovo.

It is a Microsoft problem; awhile back, there was also a discussion here about hotfix that you had to call up Microsoft and get. Their excuses have ranged from "Licensing" (a weak one since Licensing is a tricky business and simply calling in for a easy hotfix is no way around or through any License problems they may have) to "Un-tested hotfix." Which doesn't make sense either since they have tutorials on how to edit your registry with regedit (far more dangerous) as well as their own little untested software that is far more unstable; except now you can get away with putting out flashy, but buggy and unstable software by tagging "Beta" onto the name and keeping it for several years.

[DIGITALgimpus]

The issue is they won't send the fix until you aknowledge their warning that it's untested and shouldn't be used on production systems (essentially a verbal end user agreement).

They don't want wide distribution because it hasn't had full testing... from my IT Dept friends, these patches do occasionally conflict with other software... so it's possible.

The main reason, is so that the only people who use them, are people who need them, not the patch-o-holics who apply every download they can find.... then complain when things blow up.

It's no big deal to obtain... took me a couple minutes. 800 number. No big deal. Friendly rep, very efficient.

And yes, I run a fair amount of beta, alpha and even untested software... so I have this inate ability to detect small changes in how my system performs. It's like a 6th sense.

[Nick Y]

The issue is they won't send the fix until you aknowledge their warning that it's untested and shouldn't be used on production systems (essentially a verbal end user agreement).

Interestingly, there was no mention of it being untested when I phoned yesterday; but it is in their email.

It's no big deal to obtain... took me a couple minutes. 800 number. No big deal. Friendly rep, very efficient.

Agree with friendly, efficient reps, but had to speak to 2; first allocated case reference, second could use email. Couple minutes with you was 27 (UK National Rate) minutes with me!

[christopher_wolf]

The main reason, is so that the only people who use them, are people who need them, not the patch-o-holics who apply every download they can find.... then complain when things blow up.

So....You mean the majority of Users, correct?

And I know what that 6th sense feels like; it borders on paranoia when something I can't explain starts happening although it later turns out to be quite simple.

I have called Microsoft before for such hotfixes on other systems; can't complain about the process but I did note they ssemingly wanted to make sure you knew exactly what the patch you were getting did. I suppose so you couldn't go back and whine at them saying that the patch blew your ability to login to your system correctly.

As for interfering with other software; a good example of this was when I went to install VMware and an IBM CSS message box popped up that would allow me to change the secure password for the CSS logon that was different from the Windows logon password. What the box did say, took a while reading through it though, was that if it was triggered by software that was getting installed and not because you were changing the Windows password to something different than the CSS logon password, then you should hit cancel in the box at that point. It then repeated it on big text on the bottom. Now that is what I call a good plan against software conflicts.

[DIGITALgimpus]

General rule of thumb for these unreleased hotfixes is: don't use it unless you need it.

For this one, I'd say it's worthwhile, and minimum risk (since it really just disabled that dialog).

I still don't trust the one for > 1GB RAM hibernation (though I *really* want that patch)... that IMHO isn't worth the risk.

[t43er]

Hi guys, just ran the software installer and a hotfix has been found. After installing the hotfix, the pop up message when starting the laptop has been solved.