This error happened two or three days every time I started a scan (I tried again before I asked for help). But I checked again to see if I missed anything like maybe something I did, and it has now stopped. I hope this means I will not need help with this problem for now. If anyone was looking for a solution to this problem, I thank you very much.
.
.
A few seconds or less after I start a scan of my hard drive, this message appears:
Unknown Error
Scan completed with error
2147446784:Error0x7FFF7000
I have been using avast 4.7 Pro just over a month now with no problems other than the known splash screen one. That stopped with no action by me and this one started. I looked for a solution but was unable to find one.
avast! 4.7.844, formerly used Norton Internet Security 2005 (uninstalled), winMe (another problem, I know), AdAware, Spybot S&D, Outpost firewall
Let me know what other info is needed. I have limited computer knowledge and sometimes need more detailed instructions, sometimes not.
I am having the same problem. I have Avast home 4.7 and am running on Windows ME. I have never had problems before a couple of days ago. Now a few seconds or less after I start a scan of my hard drive, this message appears:
Unknown Error
Scan completed with error
2147446784:Error0x7FFF7000
I don’t recall exactly what I did after I noticed that problem, but I think it may have been a repair of avast. Add/Remove programs, select “avast! anti-virus,” click the Change/Remove button (or is it called ‘uninstall’?), scroll down to “Repair” and click “next.” You have to be online when you do this.
I also had previously uninstalled Norton Internet Security using both “Uninstall” and SymNRT from Symantec’s website, and at about this time, I manually removed a few left-overs, after this problem and a few others appeared, using “Search” to find Norton and Symantec entries.
I really am uncertain as to what solved the problem, or whether I had done something to temporarily cause the problem, but I did not see it again after that time, and avast! worked perfectly from then on. I do not mean to suggest that anything I did should be a solution, only giving more information about what was going on with my computer at that time. (WinME, 128 MB RAM then)