Bruce Wilkinson wrote:
> First, I don't agree that it's a virus infection. That system ran clean
> with 2 different A/V products. The second was installed (yes, the first
> was removed) to verify the system was clean. I was finishing clean up and
> trying to remove adware/spyware when passwords were applied. One of the
> spyware product may be the culprit.
>
> Second, you make assumptions about my professionalism that I find
> offensive. The details of how my client got into this spot are not
> relevant. I'll just say that it's a long story and I'm trying get him
> legal. The rest is none of your business.
>
> Last, just to reiterate, Windows will not cause a lock-out if it's not a
> legal copy?
I'm sorry you were offended by my post. Although I believe you
misinterpreted what I wrote, I do apologize if you were hurt. I made no
assumptions about your professionalism except to assume that you *were* a
professional.
At the risk of offending you again, I will say that if you only scanned with
antivirus programs and not with specialized non-viral malware removal
tools, then the probability that the system is still infected is high.
However, I'm sure that you know best since you are the one working on the
box.
A legal copy of Windows will not cause a lock-out unless there is a Group
Policy set to lock-out after a certain time when an incorrect password is
entered. Even then, an administrator can get in. If no passwords were set
and now passwords are being required, this is a symptom of infection as
quite a few viruses/malware variants will do this, particularly some of the
ones in the ransomware family.
I hope this has clarified my original post and mollified the original
impression you got that I was trying to insult you since that was not the
case.
Malke
--
MS-MVP
Elephant Boy Computers
www.elephantboycomputers.com
Don't Panic!