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?
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
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.
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
See attachments
I wonder if it is related to this programme and this error :
VirtualCloneDrive
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
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.
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)
Contact Avast and see if they can give you an answer:
http://support.avast.com/support/tickets/new