cluberti, on May 17 2008, 09:12 PM, said:
Well, technically you wouldn't remove it, per se, but you could conceivably replace the file(s) on the SP3 disk with SP2 versions.
Yes I think that's the way

...but how?
cluberti, on May 17 2008, 09:12 PM, said:
Does this happen if you install XP (either RTM or SP2) and upgrade to SP3?
I have regoular XP-SP2 cd (Home and Pro) without the patch KB923191 (got them before the release of KB923191).
So if I don't install KB923191, the bug doesn't occour. If I install the hotfix, the bug usually happens.
It happens also if I install Xp-sp3 from setup (obvious, the patch is included in xp-sp3).
Well, the only thing I've not still tried is to do a clean install with xp-sp2 cd slipstreamed to xp-sp3 (integration).
But I don't think that will work, because at
http://support.micro...kb/917556/en-us the issue is still "to patch" and not fir e.g. "patched with Xp-Sp3"
angrypenguin, on May 17 2008, 10:11 PM, said:
In the meantime you could use the workaround, namely use the classic login. Either just <Ctrl><Alt><Del> twice each time, or to set XP to use the classic login window by default
Yes, thank you anyway! There are also other solutions (regsvr32 shgina.dll ecc.), I've tried them all, but doesn't work.
The fact is that I'm not the only user of the 3 Pcs, and the other people are very very newbies and they don't know how to do with ctrl+alt+canc and so on...
So I prefer to uninstall (or not install) the update, rather than hearing everytime "Hey! this Pc is locked! I cannot type my password!"
thank you all for the answers... still waiting for some other solution...