aswSNX failed to load error ID 7020 [Solved]

Avast 120629-2 version.

The computer tripped and rebooted by itself looking in events I had aswSNX failed to load error ID 7020.
Reading an old post somewhere here I followed the instructions given.

In CMD prompt I typed fltmc load aswsnx and I got-:

Load failed with error: 0x8007007f
Specified procedure could not be found

The Mini dump file was empty when checked, thanks Dave

Avast 120629-2 version
That is not the version......but the virus definition ;). http://www.avast.com/virus-update-history

Yep, thanks Pondus… that is what I meant. It’s there again after a check disc scan.

Dave

This bug was already fixed in our internal build – I wasn’t too fast to fix it in our latest program version (1451).
The problem is you’re using XP SP2 and driver calls one function which, unfortunately, exists from SP3+.

Thanks for the info pk, so whats the answer?

Will it be fixed or is one being forced to upgrade to SP3+, which I would like to avoid… downgrade Avast perhaps or change AV’s?

You gave the impression it was fixed internally, are you saying this fix is scheduled for ‘external’ release shortly, appreciate some clarification please, I’m not requesting an exact date.

Dave

you can:

  • apply patch version: disable self-protection (settings → troubleshooting → enable self-defense module), download http://public.avast.com/~kurtin/aswSnx.sys and copy this file to \windows\system32\drivers folder, reboot
  • or wait for new program update: I think it’ll be ready next week, there’re several bugs in 1451 which should be fixed quite fast
  • or install SP3 ;D or Vista/Win7

@ pk
If this is the case then I would say that the System Requirements (on the avast web site) should state XP SP3 and not XP SP2.

Or would the forthcoming avast program update you talk of negate the requirement for SP3 ?

Personally I can’t see why someone with XP wouldn’t have SP3, as it also means that XP hasn’t had a security update since April last year. Which makes their system more vulnerable to exploit.

Sorry to say the error is still there.

I’ve downloaded the file and put it in System 32 folder, cleared the log files out in event viewer rebooted and the error is still showing, I rebooted again just to make sure and it still pops up.

DavidR
And if I don’t wanna upgrade to SP3?

Davy

Ooops sorry pk I’ll try again… I didn’t disable protection - my bad

Dave

Nope, still same the error is still there.

I cleared the events logs, put the file in the Win. 32 folder after turning defense off (it didn’t make any difference whether it was ON or OFF), I ensured the file was sitting neatly in Win 32 even after rebooting but the error is still there as described initially.

Maybe better waiting until next week and see what happens, my license is due to expire shortly so I’ll ‘hang fire’.

Dave

Then you have got to expect things like this to happen (not just in avast!), programs advance and as they advance the feature set will require minimal OS features.

please verify how you replaced the file. I installed Pro version and did following steps:

http://public.avast.com/~kurtin/patch.png

Nope didn’t do it like that, I copied it into the said folder… I’ll give this method a try though, will get back on the results.

Thanks for your patience pk, Dave

I’ll leave it until later on in the week for the update… might have another bash later.

I kept getting ‘can’t find file’ when using CMD prompt I tried the drivers folder within the Systems 32 folder as well remembering to reboot … all good fun, give me PCB cad work anytime!!

Thanks for your co-operation pk I much appreciate it, I will report back and close the thread should I solve it beforehand.

DavidR
Yep I appreciate I’m running on candle wax… do well to remember not everyone ‘may not’ have a super fast machine… or may not want to upgrade their service pack for some reason or other, yes times do change and some improvements are for the better and yet are some not… I would like to retain my options thanks rather than to be forced.

Dave

I well remember my time on dial-up as it isn’t that long ago (just over 18 months) I was still using it and I still consider those on dial-up.

I was still on dial-up when SP3 came out and I had to get a friend to download it for me and save it to USB, I was having to do the same for the larger windows updates and selectively install the smaller ones first or my 2 hour connection limit would also kick in. So I’m well aware of the difficulties of dial-up.

If you don’t have a friend on broadband some public/government libraries, etc. have connections that may possibly be free to use.

For me keeping my OS up to date was a high priority, the danger of exploit on a very out of date OS is great and the resultant downtime to resolve it is great, you only have to browse the viruses and worms forum to see that.

Your system obviously your choice.

I don’t get it, them gremlins are sure playing funny.

I did everything you said the first time round to no joy, running cmd I got ‘No file found’… yet this afternoon I simply dragged the aswSnx file into the system 32 driver folder as before… and presto the error’s gone at every boot up.

Just can’t think what I’ve done different, apart from downloading the file again, certainly no errors in Events now.
Thanks for putting up with me pk, I do appreciate the time you spent.

Best wishes, Dave