OS boot problem after Boot scan....

Hello everyone,

Today i ran a full scan and found 2 root kits and 1 corrupted music file that i removed off of my pc using the free version. After the completed deletion it told me i must restart and run a boot scan to make sure the root kits were removed. Ok well after about 3 hours of the boot scan 7 more files were found corrupted and deleted.

After it finished deleting it restarted the PC, (i forgot to add this but windows installed many new updates before the scan and needed to restart but i never restarted before i did the full scan) and now it will boot the OS, then say Configuring update step 3/3 0% complete…but after about 2-3 minutes it will restart my pc…going right back to Configuring update step 3/3 0% complete. I have let it do this like 10 times now and it seems i broke my computer. D:

So my question is…must i wipe if clean and start over or is there something i can do?

Edit: running Vista 32 bit if that helps.

Edit#2: after browsing some Microsoft forums others have had this problem… I just reverted back to before the updates and got logged in. feel free to let me know if i fubar’d something in the process :wink: im about to say F-it and install XP on the pc as i have not had issues with XP.

EDIT#3: Ok now that i reverted back idk if those viruses got back on my pc but it is running like a tortoise now…guess im gonna go with the xp plan if no one can help me by tomorrow when i get done with work.

Thank you for the help,

Trevor

you could start with telling us what avast detected…and the name and location on the file(s)

any other security programs installed?

Yea I just ended up wiping vista, also i would have posted the logs but i couldn’t even get to my desktop. Thanks for the reply.

Hi Trevor :slight_smile:

I know this is not a popular piece of advice…but windows auto updates can cause more harm than
good. Too many times and too many needless problems over the years, I finally advised folks to
turn OFF auto updates for windows and learn to do manual updates if necessary.

Some Microsoft updates end up costing people in more ways than one, with most thinking that
they are harmless, but I can tell you from experience, they are not always ‘harmless’ and can end up costing
for repair service, etc. Do NOT disable auto updates based upon my experience, I am just sharing how many times
I have seen updates from M$ go bad, and render stable systems corrupt. This costs most folks money to get back
up running stable, and often it can require a full re-install of the OS. Good news is you were able to revert back before
the update mess, and you got your system back…if you used system restore and the restore point you used had any
malware within it, then it is likely you became re-infected, which if your system is running like a tortoise, it may be
the case, unfortunately.

Many of the M$ updates are simply not necessary for a securely functioning computer, although some security
updates considered ‘critical’ should be considered, remember there is always potential set backs because some updates
may break other applications. In computing, there is often trade offs in choosing a stable system, or feeling the need to
install everything M$ throws at you during an update. It is wise to choose only updates that are considered ‘critical’ and leave the
rest alone.

Bottom line: the goal is to have a secure stable system, using quality security products such as Avast! and at the very least,
using the windows firewall, or a better choice would be a more featured firewall along with Avast! free. Then learn about
the latest M$ updates and which are considered ‘critical’, then check to see if they are causing any issues for users before
downloading and installing them. I have found this approach takes more effort from users, but it also has assisted many to maintain
a stable system while getting users MORE involved in the update process instead of blindly allowing any updates offered that are
not considered ‘critical’ security related “patches”.

I hope you can get the system cleaned up, if not, the same advice goes for XP. If you reverted back to XP, I advise installing service
packs, SP2 then SP3…if your copy of XP already has SP2 integrated and it should if the XP install disk is newer than August 2004, then
you can download the full XP SP3 service pack, install it while XP is still “clean”…then after reboot, if things appear stable, then proceed
to install the necessary software you generally use. Then image your freshly installed and updated XP. Then, install your security apps.
If you run into any problems, you will have a clean image to restore to without having to reinstall windows.

Just some thoughts to try and maintain system stability and reduce tech service costs in the long run.

Best wishes to you!

All my best!
Jim

I agree with jim1cor13. I remember one update that MS put out a while back that crashed your network use if you used any firewall but the built in MS one. I also remember norton AV crashing (version was very buggy to begin with) after SP1 was installed on XP. that was more of a norton problem, but never arose until SP1 was installed at the time, but it still was a result of MS changing things in the service pack… I have seen so many complaints that it is not funny, and even happened to me, where the anti piracy crap said that my system install was using hacked software. happened on XP after the system crashed and had to reinstall to get rid of it… I believe that was on an compaq computer using the serial that was on the sticker on the bottom of the laptop. I could go on and on, but they all happened after updates were installed. As for vista… maybe I should say vista beta since it never worked any better then beta software… well, I have told everyone that I have met to stay away from it. In my opinion, that had to be one of the worst OS’s that MS has ever put out. I loved XP and 7 but vista… well lets just say when you see person after person saying that they upgraded to XP from vista… and this was from tech’s, that should tell you something about vista… In any case, back to the original statement, I just saying that just because it is an update from MS, dont take that it is always going to go fine. Most install fine, but I have seen so many times that systems have crashed after installing updates, it may have been an update that crashed your system… guess we will never know…