Cannot log into Vista after Avast Boot Scan

For some reason, I cannot log in to Vista (meaning cannot type my password) after completing a boot time scan. The computer starts normally & I can type using a Ubuntu Live CD, but not my password. Any advice?

Matt

What reason do you mean?

George I am not sure. All I did was complete a boot scan with nothing being detected and the system was restarted. Upon trying to enter in my password I could not and not even in safe mode. I can type just perfectly fine from a Ubuntu Live CD.

My thinking is, even though it is a different OS, wouldn’t it also be not able to type since it would not in vista?

The connection to the keyboard is intact and seems placed in the slot well.

I assume you are using a USB KB -

in the slot well

The live CD will have loaded its own KB drivers?
do you have a PS/2 port on your mobo?

I am not sure. When i meant “in the slot well” I was referring to the keyboard port. Sorry if I confused anyone.

Also could it be that the keyboard just went kaput? I have had the system since around late 07.

But you can type using the KB with the Linux Live CD but not with Windows
The slot is USB
My suggestion was that maybe the windows drivers for the USB keyboard had gone awol
If you have a ps/2 port you might borrow a ps/2 KB and try that

Just to mention that avast 5 does not offer any automatic action on boot time scanning in the moment.
Although nothing was detected, nothing is done automatically either.

David, I can boot this way correct.:slight_smile:

I am not sure if I have a ps/p2 port. I have a lenovo K210 Desktop.

The only drivers I have installed are my lenovo drivers from the lenovo drivers cd
(lenovo drivers pack 1.9 for vista).

This is just a minor inconvenience. I am planning to dual boot Ubuntu Lucid & Vista until I can get a replacement keyboard. The thing to me is, I had figured, since Vista wouldn’t type, I figured it would be the same in linux:) Learn something new every day:)

Is there anything I can think about trying? Nothing real big, just trying to understand how this could have occurred without a warning. I did not think any sort of scan could cause a component to fail :slight_smile:

The component still works with Linux

http://www.retrevo.com/search?q=Lenovo+K210&rt=sp&modelid=18794776

…Keyboard Interface PS/2

It does seem as different os’s are handling things differently. As soon as I can grab a new keyboard, I will update my other thread.

(Just glad it’s not a more expensive fix!)

Matt