To Vlk to check

Vlk,

I understand you have post about the v4.1.412 and it has got bugs, I am asking for some understand on what been happening and I have never seen this before.

Everything was find since I had the v4.1.396 cause it never show this before, when I did a full thorough scan with the archive turn on v4.1.412 is this the bug your talking about???

“The jpeg link has been removed”

Can you please explain. I am sure other people has got the same problem.

Please don’t delete the post just until I have responded.

Thank you.

The first part (the Sbybot S&D) files are normal. These are password protected file.

The second bunch of files (starting with aswIdle[AsPack]) is related to the build 412 bug.

If you’ve widened the ‘Result’ column you’d see the reason.

Thanks Vlk that explain I couldn’t understand when you post about the v4.1.412 has got bugs, when I did a for scan I never had this many files before. Lucky I kept the v4.1.396 software just in case if there were bugs in the new version.

If you could please remove the v4.1.412 from your website page to stop people download the bugs version, it would be better to put back the v4.1.396 on the web page and explain to the people on the web page about the bug until it fix by some one who can test it.

PS. I have remove the jpeg file from the link to show Vlk to explain.

Actually it seems to be problematic only on a minority of computers so we’re not removing anything…

No problems here, in fact if anything I thought my local drives standard scan (no archives though) was a bit quicker at just over 8 mins.

Vlk,

When I uninstall the bug version and went back to 4.1.396, I am getting the same the problem as the 4.1.412 when I did a full thorough scan with the archive file tick as well.

Where do I go from here my mind tell me to reinstall my HD again from scratch.

Well as I said, with v396 you WILL be seeing the Spybot S&D ‘Unable to Test’ stuff but you shouldn’t be seeing the [AsPack] stuff. Or you are?

Yes. I am seeing seeing the [AsPack] stuff when I went back to the v4.1.396, I understand avast cannot scan the Spybot S&D ‘Unable to Test’ which is normal.

Any ideas???

Then you hardly have the 396 files, really. Hasn’t avast updated?

What is the time stamp of e.g. file aswEngin.dll in the avast folder?

Thanks
Vlk

Sending a jpeg link wait about 10mins

Vlk here is your request you ask me to check

The link has been remove

That’s odd, really. The files seem to be authentic (version 4.1.396). Are you positive that you’re still getting the AsPack errors? It just doesn’t make any sense… ???

Vlk,

I am not joking still having the same problem, and this is what i am going to do just about now.

  1. Uninstall the v4.1.396

  2. Clean out the Register file related to Avast

  3. Reboot and reinstall v4.1.396 again

  4. Do a full thorough scan with the archive file tick on

  5. Then I will let you know. I hope

Vlk,

It works all I had to do is clean out the register files related to Avast, and reinstall v4.1.396 no more problems.

Bloody strange ???

Maybe its related to Beta release. I didn’t installed it and 4.1.412 is working just fine. Has anyone of you installed beta version of this nev release?

I don’t know,there’s been quite a few threads started in this forum about this subject.
I saw it posted in the Verizon Newsgroups also.
It may be a “minority of computers”,but it sounds like a large minority. ;D
Keep in mind a lot of folks might not have gotten the program updates yet and even if they have,they may not have run scans.
By the way, I’m one of the minority.

I’d agree with that. I run a forum elsewhere for an e-zine I run and I’d say that 99% of my readers don’t e-mail or post in the forum to let you know if there’s a problem, those posting here will probably be in the very small minority. And comparatively few people know enough to be able to report a computer problem accurately to the right people and work out what’s causing it, they’ll probably just give up or think their computer’s got a virus.

i agree cause this is the first time ive ever used a forum and im using it now so this slow scanning problem can b fixed.

I have the “AsPack” problem as well on two home PC’s running the latest 4.1.412 build.

Douglas

Please see here: http://forum.avast.com/index.php?board=2;action=display;threadid=5140;start=msg37721#msg37721