Upgrade went smoothly. I decided to try re-enabling the web shield and putting the standard shield down from high to normal. But web pages wouldn’t load so I put things back the way they were. So the upgrade works just as well for me as the previous version.
So far no problems. Everything seems to be in order.
This morning I downloaded 4.8.1330 beta & rebooted. Everything is fine except Windows Defender showed up in my taskbar with a yellow apostrophe. I clicked on the WD icon in the taskbar & it said I haven’t run a scan in ten days. I have WD running in realtime & scheduled scanning. It wanted to run a scan, so I let WD scan my system. Today after work I booted up my computer and again WD showed up in my taskbar saying I haven’t run a scan in ten days! ??? In fact this morning before I downloaded 1330 it had run the scheduled scan. I have never had this problem until 1330. Is this a bug in 1330?
See my sig, XP Sp3.
Off the top of my head I can’t see how it is, avast doesn’t have any interaction with it and the setting of the asterisk would be a WD issue and avast scans and alerts to malware, but it most certainly doesn’t change other program settings. That I feel would be a big no no.
I don’t use WD but when unexplained freaky things happen I would suggest a reinstall of WD.
I think it is none other than a co-incidence, avast couldn’t set a last scanned date 10 days early to trigger this 10 day warning, so I would first check your system clock.
System clock is right, it is one of the first things I checked plus I use Alphaclock, it uses atomic clock to keep my system time spot on. I think WD & '1330 are somehow conflicting.
I proudly made a thorough scan with this BETA and everything is fine & smooth so far. I very love this product, the one I never had to whine over from years so far. 
I would be surprised if there were a conflict like this as it is like an administrative/housekeeping task, e.g. presumably nothing stopped the WD scan from running were a hooking style conflict might occur.
Of course you could co back to 4.8.1296 and prove or disprove that possibility.
Just installed 1330. Everything is fine so far (see my sig at bottom for os info).
Uninstalled avast! 4.8.1330, rebooted. Uninstalled WD.
Installed avast! 4.8.1296 rebooted, installed WD.
Updated to avast! 4.8.1330.
Now everything is ok so far. 
There had been no recent changes to my system & no problems before I originally updated to 4.8.1330, so the finger still has no where to point except to '1330. ???
I installed the Beta and so far no problems here.
The reason for betas are to find bugs so nobody can whine over the stable releases. 
I report issues I find in betas, maybe the one I found today is a fluke.
Running fine on a Windows 2000 Pro SP4
Sorry but the idea of me suggesting to uninstall 1330 and go back to 1296 was to pin down the cause or exonerate avast. Unfortunately, having uninstalled both at the same time we will never know where the problem lay. Though if it were a bug in 1330 then in theory it should still be present.
When trying to track down a possible conflict in two applications you should really only look at one element at a time.
The download aborts after 38K.
Strange…
(I disabled AVAST altogether to no avail)
0oops! I gave the wrong order. Actually I went back to '1296 before I uninstalled WD. WD was doing the same, I assumed it had been corrupted by the installation of '1330, so I uninstalled WD & reinstalled it.
I wanted to then install '1330 where my system was when I originally installed it.
Well to me that points to a problem with WD, if the same problem occurred with the 1296 build, I really can’t see any logical way an avast update could corrupt another program.
The download ‘aswbeta.exe’ is only 38K (well… 37.3 to be precise).
You need to run it after download.
Don’t forget…
And re-enable it afterwards.
No problems with Windows Defender for me.
By the way it is at v1.51.201.0 available on its portal:
http://www.microsoft.com/security/portal
End it then download and run it.
I don’t know if this already has been in previous versions, but i just noticed that in the splash screen the “stop memory-test”-button in the German version is not correct.
it somehow seems to be cut…
in German it should be “Speichertest beenden” but there is “Speichertest beende” so there is missing the last letter.
yours
onlysomeone
Oops!
Thanks for letting know!
I was expecting something a few megs big.
Maybe that info should be added in this thread’s first post.
Best,
François