Are there any files called \data\log\unpXXXX (where XXXX is a random number)?
If so, send them to vlk (at) avast (dot) com
They may contain more information about the problem (maybe a link to this thread).
No, there are no recent “unp*” files. The only one there is 0 bytes and dated 26-Mar, some time before I updated to 4.8. I have another Thinkpad, an X300 running Vista Business and that has no issues. It’s almost quicker to shutdown the T42 that to “sleep” it! Any other ideas?
I’ve only recently (about two months ago) flattened and rebuilt the T42 and it’s been perfectly behaved since then. Rebuild was an annual MS entropy reduction exercise. Is there a way to back out to 4.7? Can I manually pull the package down?
I have to say that given the level of noise on here about 4.8, and especially one about Dell’s, I think for the moment I’ll stick with 4.7 on my Dell desktop and servers. I’ve advised one of my hedge fund clients, where we’ve installed c. 70 servers and c. 90 desktops to hold fire via ADNM on moving to 4.8 for the moment. It’s a shame, as Avast is about as “lights out” as you can get for corporate AV solutions.
No joy I’m afraid Tech. Once 4.7 is installed, if I then put in my Pro license key it insists on updating to 4.8. There seems to be no way of stopping it. So I’ve still not been able to isolate 4.8 at the cause of the “resume from sleep” issues.
You evidently have avast! 4.7 set to automatically update the program – and not just the virus database. To prevent an automatic update, you can isolate yourself form the internet (engage interlock on firewall or unplug internet cable), then either before or after entering your license key, ‘right-click’ on avast 4.7 blue ball, ‘left-click’ ‘program settings’; ‘left-click’ ‘update basic’; then you’ll see update settings for virus data base and program. Set program update to ‘manual’ so it won’t update to 4.8 if that’s what you want to do.
Nope. I did that straight away. I then re-ran the program and entered my reg key. No questions asked, no prisoners, it just updates to 4.8. Try it yourself. Offline seems to be the answer.
The issue is (probably) that the link you gave me was to “setupeng”, and with my key for “pro” it tries to upgrade to the latest/greatest, i.e. 4.8. Any link to a 4.7 “setupengpro”??