Hi,
after going back to an image from july my Avast GUI does not start, see attachment.
Any idea for help?
Perform a clean installation of the latest avast version.
Clean Install of Avast:
https://goo.gl/4Ptzkf
If you need additional help with the Clean Install, watch this:
https://youtu.be/p-h3myRD51A
Well, I tried this Clean Install.
Download of the new version run up over 150 MBytes … ?
Avast Uninstall Utility (http://www.avast.com/en-gb/uninstall-utility killed my system - it only starts in safe mode, even when I went back to a clean image.
What ist this? How can I start my system normal?
You start it in regular mode and then allow it to finish doing it’s job in safe mode.
Did you watch the video ???
What operating System are you running ???
Bob,
I clicked at Clean Install and the PC did someting, then went down. OS is Win7.
This marvellous tool pimped the boot manager which alsways starts in safe mode.
I think I try something better than this overloaded and unstable program.
The deinstall routine changed the BCDedit code so that it’s impossible to start in a normal way.
Ist that normal >:(
Why is it impossible ??? What are you seeing ???
Bob, I wrote it above - The deinstall routine from your “clean install” link pimped the Windows boot manager which now alsways starts in safe mode.
Which means Restricted services and minimal screen resolution. And as this is injected inside the boot code this works permanent.
As most people I have problems here & there in the past, but this tops all of them: not even back to a clean system image solves the problem.
End of my relationship with Avast.
Still don’t know your OS.
Use the run command and open msconfig. From there you can fix your boot option to
restart normally.
http://screencast-o-matic.com/screenshots/u/Lh/1508236230060-67845.png
see answer #5 … Win7
winkey + R > type “msconfig” > go to boot tab> select normal boot > apply then okay.
Thx.
But ther remains an enormous problem - the safety software orat least it’s deinstall tool changes the bootcode and a normal work is impossible.
No software besides the OS vendor has to do anything in my boot code. Never!
That works like a virus for me.
You gave it permission to make that change and then didn’t allow it to follow through.
Correct it by following the corrections outlined.
No, Bob.
I Kwow you tend to excuse a lot of Avast’s behaviour.
But a deinstall routine has nothing to do with changes at my boot code. Absolutely nothing.
It’s malicious like any kind of malware. A malware program that destroys a basic computer function?
No-go…
I don’t excuse anything. This however isn’t what you claim.
Your computer, your choice. If you aren’t happy, it’s up to you to make a change.
My computer, my choice? That’s your answer to a very serious problem?
And nothing from the guys who write often here … Pondus, Lisandro, DavidR ??
No statement frm the Avast team?
Ok - my choice: I change my AV software.
No, it just send a command to NEXT reboot on Safe Mode.
Which program are you using to make/restore images? Did you restore your MBR/Boot info?
No, Lisandro - Safe Mode came about 5 or 6 times, and didn’t stop.
My image Did not restore the MBR.
And I restored the image only after several Resets.
But there is light at the horizon. This routine changes from normal to safe mode. And not once but permanent.
Tis is the connection 
So nobody here does something against this severe behaviour?
Nice …