Author Topic: installation of Avast makes my computer boot in automatic repair modus  (Read 2508 times)

0 Members and 1 Guest are viewing this topic.

Offline goliath

  • Newbie
  • *
  • Posts: 11
The installation of Avast Free/Pro (version 2016.11.2.2262) makes my computer boot in automatic repair modus. I am using a HP Pavilion 550-127nb. What goes wrong here? How can I solve this?

Offline Pondus

  • Probably Bot
  • ****
  • Posts: 36642
Did you remove any preinstalled or previous used Antivirus before installing avast?

Uninstalling a third-party antivirus software  >>  https://www.avast.com/faq.php?article=AVKB11#artTitle

Avast 2016: Using the Uninstall Utility  >>  https://www.avast.com/faq.php?article=AVKB10#artTitle





Offline goliath

  • Newbie
  • *
  • Posts: 11
It was a clean Windows install, so no previous versions or other anti virus programs were installed.
I use a dozen of other computers with this version of Avast running and none of them give problems.

Offline Pondus

  • Probably Bot
  • ****
  • Posts: 36642
can you provide these diagnostic logs

See instructions here  >>  https://forum.avast.com/index.php?topic=53253.0
Scroll down to second picture > Farbar Recovery Scan Tool < Run as instructed and attach the two diagnostic logs


See below the box you write in ... Attachments and other options

When done, Essexboy will have a look


Offline goliath

  • Newbie
  • *
  • Posts: 11
See attachments

Offline essexboy

  • Malware removal instructor
  • Avast Überevangelist
  • Probably Bot
  • *****
  • Posts: 40631
  • Dragons by Sasha
    • Malware fixes
I wonder if it is related to this programme and this error :

VirtualCloneDrive

Quote
Kan Groepsbeleid niet verwerken. Een poging om het bestand \\bisdomhasselt.be\sysvol\bisdomhasselt.be\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini vanaf een domeincontroller te lezen is mislukt. Groepsbeleidinstellingen kunnen pas worden afgedwongen wanneer dit probleem is opgelost. Dit kan een tijdelijke fout zijn die één of meer van de volgende oorzaken kan hebben:
a) Naamomzetting of netwerkverbinding met de huidige domeincontroller.
b) Latentie in File Replication-service (een bestand dat op een andere domeincontroller is gemaakt, is niet gerepliceerd naar de huidige domeincontroller).
c) De DFS-client (Distributed File System) is uitgeschakeld.

Have you installed Avast on other systems with this programme

Offline goliath

  • Newbie
  • *
  • Posts: 11
Yes I did.
I just uninstalled VirtualCloneDrive and tried to reinstall Avast again, but still the same problem. So it is not related to VirtualCloneDrive.

Offline essexboy

  • Malware removal instructor
  • Avast Überevangelist
  • Probably Bot
  • *****
  • Posts: 40631
  • Dragons by Sasha
    • Malware fixes
Looking at the driver installation the only other one I can see is NVidia, there is nothing else evident that would cause this (as far as I know)

Offline bob3160

  • Avast Überevangelist
  • Probably Bot
  • *****
  • Posts: 43574
  • 60 Years of Happiness
    • bob3160 Protecting Yourself, Your Computer and, Your Identity
Contact Avast and see if they can give you an answer:
http://support.avast.com/support/tickets/new
Free avast! Security Seminar: http://bit.ly/2N1eaR2  -  Important: http://www.organdonor.gov/ -- My Web Site: http://bob3160.strikingly.com/ - Win 10 Pro v1909 64bit, 24 Gig Ram, 1TB SSD, AvastOmni 20.3.xxx, How to Successfully Install Avast http://goo.gl/VLXdeRepair & Clean Install https://goo.gl/t7aJGq