Avast is crashed and the system won't take my ticket

General Topics
1

I’m having trobles subbmitting a ticket so I will try one more time.
Please see attached files for screen shot of avast error. I was having problems with National Instruments software and had to do a restore. I found last night avast would not start. Please advise ASAP.

If I uninstalled can I reinstall with of registration information.

see system info below

OS Name Microsoft Windows 7 Home Premium
Version 6.1.7600 Build 7600
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name BURKE-PC
System Manufacturer Hewlett-Packard
System Model HP Pavilion dv7 Notebook PC
System Type x64-based PC
Processor AMD Turion™ X2 Dual-Core Mobile RM-74, 2200 Mhz, 2 Core(s), 2 Logical Processor(s)
BIOS Version/Date Hewlett-Packard F.49, 8/17/2009
SMBIOS Version 2.4
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = “6.1.7600.16385”
User Name Burke-PC\Burke
Time Zone Eastern Daylight Time
Installed Physical Memory (RAM) 4.00 GB
Total Physical Memory 3.75 GB
Available Physical Memory 1.98 GB
Total Virtual Memory 7.49 GB
Available Virtual Memory 5.23 GB
Page File Space 3.75 GB
Page File C:\pagefile.sys

Burke

2

Can you try to repair your installation?
Go to Control Panel > Add/Remove programs > avast! antivirus > Remove. Then choose Repair function in the popup window (Repair).
If this does not help, can you uninstall / boot / install / boot again?

3

You can do a clean reinstall if you have saved your license.avastlic file that was emailed to you, as that will be required to register.

However before doing that - Have (or did) you another Anti-Virus installed in this system, if so what was it and how did you get rid of it ?

If you did have another AV other than avast 4.8 for instance, then reinstalling may not resolve that problem.

  • Download the latest version of Avast! IS 5.0.507 http://files.avast.com/iavs5x/setup_ais.exe and save it to your HDD, somewhere you can find it again (if you didn’t save your last download). Use that when you reinstall.

  • Download the avast! Uninstall Utility, aswClear5.exe find it here and save it to your HDD (it has uninstall tools for both 4.8 and 5.0).

    1. Now uninstall (using add remove programs, if you can’t do that start from the next step), reboot.- 2. run the avast! Uninstall Utility from safe mode, first for 4.8 if previously installed and then for 5.0, once complete reboot into normal mode.- 3. install the latest version, reboot.

  • Avast! Internet Security Quick Start Guide http://files.avast.com/files/documentation/quick-start-guide-is-en-ww.pdf

4

Thanks all.

I removed and did a clean install. Doing a full scan as we speak. I was fretting earlier as I was anticipating a multiday ordeal like when using Norton. Avast=painless

Thanks
Burke

5

Well if Norton was on this system it might be worth running this too to ensure all remnants are gone.

A link worth looking at, which is a program removal tool that can remove the remnants of a number of different Norton Programs:
Removing your Norton program using SymNRT
Or ftp://ftp.symantec.com/public/english_us_canada/removal_tools/Norton_Removal_Tool.exe

6

No Norton here. Let me clarify. Avast has been the only AV program on this box and this weekend was the 1st issue I ever had with Avast. It was solved very easily with your and this forums help. In the past when I used Norton this would not have been the case. I would have spent several hours with very little or no support.

7

Understood ;D

8

Don’t reload it at all, get rid of it! It crashed my boot drive completely and tech support does not respond. Forget you even heard of this program!

9

Clearly not the case for burkeam, in Reply #3 having done a clean reinstall all appears to be working as it should.

System Restore when used appears to be having an impact on avast (what started this particular issue if you read the first post) when going back (why I don’t know) but a clean reinstall seems to resolve that.