I'm stuck in a boot loop. Can't even get into safe mode. More on the situation here and here. This happened when I reinstalled Avast.

I want to now uninstall Avast.

This is how I'm thinking of doing it...

  • Install Avast in another computer.

  • See what files were added and their path.

  • Boot in first computer through a Linux live disk (Xubuntu 18.04 LTS live USB), or HirenBootCD.

  • Go to those files and delete them one by one.

What do you think of the plan? Any easier way of doing it?

Also, the computer I'll be installing Avast in is 32 bit. The computer I'm working on is 64 bit. Will there be any difference in the amount of files Avast will install or where it'll install them? If so, how to get around that without having to look for a 64 bit computer?

[Windows 7 | 64 ]

  • 1
    XY problem. Your goal is to fix your computer after Avast installation that prevented it from booting, but you're asking a completely different question that focuses on an approach which is overcomplicated and probably ineffective. Have you tried to use System restore?
    – gronostaj
    Nov 6, 2020 at 11:41
  • 2
    Your not going to successfully remove Avast the way you describe. Furthermore, the simple fact is, there are not good tools on Linux to make changes to the Windows registry hive. The fact your unable to boot into Safe Mode suggests there are more problems than just the file it’s getting stuck on.
    – Ramhound
    Nov 6, 2020 at 12:01
  • 1
    You're right, I should've looked at your links first. Anyway, your approach won't work. Start by taking a full disk backup now with Clonezilla, DISM or whatever, you may want to restore this system state later. Then I'd swap entire registry for a new copy (not empty, just non-customized), manually extract last good registry from last System Restore point, load it manually and try to perform the restore. I did it once on XP years ago, it's possible. Reinstalling could be way easier though.
    – gronostaj
    Nov 6, 2020 at 12:19
  • 1
    That's what backups are for.
    – Tetsujin
    Nov 6, 2020 at 12:55
  • 1
    @JW0914 It was introduced in Vista apparently and disabled in Windows 10 version 1803, so that could be a good idea!
    – gronostaj
    Nov 6, 2020 at 13:12


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.