I did a boot scan and it keeps going back to the same (Startup Repair) window. It does the scan and reboots and back to the same scan. I have tried safe mood but it will not work. I booted to the windows 7 cd and did a system recover point and that did not work. Please some one help.
Hmm, sounds like something is wrong about the system…
How about the “Last known good configuration” from the boot menu?
Had no problems with it till I installed AVAST and did the boot scan. I did a system restore point and that did not work.
Try booting into Windows Safe Mode → Control Panel → "Add/Remove programs → Avast → repair (or change-> repair, according to Windows version).
I can not get into safe mode.
Then your problem is NOT Avast. The scan problem was just a coincidence.
Under a normal, working Windows system, even if Avast leads your system to some kind of problem or incompatibility, it would NOT be such that you are not able to boot into Windows Safe Mode.
I agree with Igor. It sounds like you have some problem in your system.
I’d ask again - how about the “Last known good configuration”? I believe that should, under normal circumstances, unschedule the boot-time scanner - though I have no idea how the attempt with restore point affected that.
Sounds like critical windows files are damaged.
In the option screen by booting & hitting F8 try command prompt. type C:
chkdsk \f.
reboot. And try sfc.\scannow (may ask for windows cd to repair files)
If fails you will need windows cd to do repair of windows files(NOT RE-INSTAL OPTION)
If you have important files on this the hard drive can be removed and put in a usb caddy to view them on another computer (scan the hard drive first though on the other computer with antivirus etc)
Just developed the same problem on a fresh installation of Avast Free. The laptop was rootkit, malware, virus infected. After running combo fix, stinger, manually updating and running defender and deleting several items I was able to restore basic operations. Finally installed Avast Free and performed a full scan. Within moments it detected a “hidden boot sector” rootkit (or something to that effect). Long story short Avast suggested a boot time scan and since gone into Win 7 Startup Repair boot loop.
I believe that it would be premature for ady4um to state “Then your problem is NOT Avast.” While the problem may no longer be Avast (the problem now is probably a missing boot record), it is quite potentially a by product of Avast incorrectly attempting to fix the issue.
That can be fixed by doing the following
Select repair my computer
Select Command prompt
http://i1224.photobucket.com/albums/ee362/Essexboy3/RepairVista_7277.jpg
At the command prompt type the following
Bootrec.exe /FixMbr
[*]Once finished type Exit
OK, indeed, that may be one possibility. Just to be clear, a boot problem (bad MBR, PBR or boot/system files) might be caused by some malware, or from several other reasons. Avast might had tried to eliminate the malware from files, and leaved some other bad booting component, originally corrupted by the malware.
But I’d like to “be fair” to Avast. Maybe the action that triggered the visual result of not booting was Avast trying to clean some malware, but probably Avast would still be “only the messenger” here. The booting process was probably already affected by some malware before, and if this is the case, I would say that the “real” problem was the malware, and Avast might need to improve the “cleaning” part, if all these assumptions are indeed correct.
Whether assumptions or not, the possibility is still real, and justint215 is correct.