Avast broke down Win 7! Need help!

Hi folks!
I need your help. I scheduled hard scan by avast in next boot. Then i restart my computer, avast started its scanning. It found 3 dangerous files, unfortunately I “told” avast to quarantine to all such files. When I realised what I have done I click immediately “esc”, but system didint start. So, whats next? I need to restore these files via cmd in lunch startup repair center. But: I dont remember what are these files, and most important where are these files. Could anyone help me?

Try to boot in safe-mode.
If you succeed, start avast and you can restore the files from there.
But why do want to restore “dangerous” files?
What is your real problem?

If you can boot you will find the files in the virus chest.
GUI>Scan>lower right corner you will find “Virus Chest”>click to open>right click on the file>click “restore” :slight_smile:

Can you access the command line using safe mode, tapping F8 repeatedly, during reboot?

Word of warning…boot scan should only be done if avast recommends running one.
I haven’t ran a boot scan in years.

  1. They might be either important or vital.
  2. That is what we are trying to figure out.

Well guys now I know that boot scan is not a good idea:) My win does not even start in safe mode:/ I can only:

  • automaticly fix problem
  • restore system
  • restore iso of system (menu is in polish I have to translate it for you)
  • memory diagnostic
  • cmd - command line, or sth like that - similar to console in linux
  • dell data safe restore and emergency back up

This is girlfriend’s computer so I have no backup of working system.
I can not even start avast - so restore is not possible - for now, for me…

I dont know what were these files - I only know, that after quarantine system broke down and it doesnt cooperate. So I suppose that restoring of these files will fix my problem, am I right?

You might be looking at a complete reformat. Sorry.

edit: Did you by any chance make a rescue disk? If you did you should be able to reboot using a rescue disk.
Making a rescue disk is the first thing anyone should do when using a “fresh” computer.

Well I do know that but the owner… :slight_smile:
Gf is just using. Really? No chance? Format?
Do you know where avast separate infected files?

I finally found awsBoot.txt which is avast report from that scan. It contains reports from two las scans. Important info is:

  • an OLE archive is damaged
  • an CAB archive is damaged
  • files from c:\Program Files (x86)\MagniPic were put under quarantine

Is this could be a reason of break down?

The boot scan function is provided as an option without any warnings, so a user is entitled to expect to be able to use it the same as any of the other scan types. There is no warning in the description about not using the function unless directed to do so by Avast.

Yeah, I know that. The boot scan is provided if any user needs to run such a scan.
Normally a user will find a weekly “quick scan” and a monthly “full scan” is sufficient.
If after a scan avast recommends the user run a boot scan it’s a good idea to do so.

Personally I would like to see avast add something to the effect, “a boot scan should only be run if avast recommends it”.

Did a “Google” search and found these…
http://www.justanswer.com/computer/13u7t-does-ole-archive-corrupted-mean-also.html
http://forums.techguy.org/all-other-software/988948-how-fix-corrupted-archives.html
http://erroranswers.com/installer-error/how-to-fix-a-cab-error-so-you-can-install-programs/
http://en.wikipedia.org/wiki/Object_Linking_and_Embedding

MagniPic:
This infection is designed specifically to make money. It generates web traffic, collects sales leads for other dubious sites, and will display advertisements and sponsored links within your web browser. MagniPic it’s technically not a virus, but it does exhibit plenty of malicious traits, such as rootkit capabilities to hook deep into the operating system, browser hijacking, and in general just interfering with the user experience.

I would first try the “automatic fix problem”, if that works you can boot the system normally (or in safe mode) again and take on problems from there.