Windows Live OneCare 2.5 Beta

Another update at connect

For a company as large as MS, there lack of support for a beta, nevermind a release is appaling.

 

I will hang on for another day. If an update isn't issued by then I will revert back to 2.0

 

Don't betas update at the same rate as the version they will eventually replace?

 

You would think so but according to the logs it is not happening. If it wasn't for reldel's post I wouldn't have known about it. I had seen the "create support log" button before never did see what it did.

 

According to Microsoft malware protection centre the definition database is up to v1.31.9265.0 whilst the beta version is still at v1.31.9148.0 now 4 days since an update.

The connect feedback forum seems like a waste of time as there would appear to be very little activity from microsoft.
Maybe they would have been better to have had a feedback forum on the live onecare forums.

It looks as though i am going to have to drop onecare beta if things do not improve after today.

 

I keep posting about it in Connect, but I sense whoever is in charge of the beta, the updates and the Connect web site, all must have a very long weekend.

Without a response soon, I'm dumping the program, even though it seems to work well.

Just dumb that someone is not watching the ship.

Can't wait to see Yahoo if Microsoft buys it.

 

Since it is Sunday I decided to leave it on for another day. If there isn't an update by the time I get home from work tomorrow, I will reinstall 2.0. I hate to do so since it has been running well here.

 

I have uninstalled onecare.
4 days is long enough even if you count the weekend.
Very poor customer relations from microsoft.

 

Avira detects most (if not all) of these quite well. Yes I know... I look at all teh spammed Pr0n sites.

 

I went ahead and went back to 2.0. These are the signature versions which are more recent than it was in 2.5:

AV Delta: (1.31.9269.0), AV Base: (1.31.8400.0), AS Delta: (1.31.9269.0), AS Base: (1.31.8400.0) AM Engine: (1.1.3408.0), AM Product: (1.5.1944.0)

 

An odd situation. I've never seen a situation where the beta definition update schedule was different. Then again my experience with Av betas is limited.

 

It is odd. If the beta program was so radically different where it had to use different sigs I would understand it having it's own servers. But there is little difference between 2.0 and 2.5 so you would think it would use the same servers.

 

Update today to 1.31.9287.0 at 3PM EDT.

As close as i can tell, OC went about 124 hours without an update of Virus and Spyware definations.

 

I think I will just stick with 2.0 for now. As soon as I booted up this evening the sigs were updated. I don't want to wonder every day if my AV is up to date or not. I was hoping for at least a explanation but it doesn't look like one is forthcoming.

I will just wait like the others for 2.5 final.

Excuse me but OC just informed me that it was time for a tuneup so off to the laptop I go, lol.

 

So how is the beta coming so far? Any word on when it will be final?

 

It has been running fast, quiet and clean for me on Vista sp1 and xp sp3 machines.

Scanning times are fast.

This build has run smoother for me than Avira Suite or Eset Smart Security. Opening multiple tabs in both Opera and IE7 are faster with fewer "hangs" and either Avira or Eset.

What I don't like is the inconsistant updates of definations. Both my machines are reporting to be up to date BUT Microsoft last updated definations to .9637 on 5/14. Seems far to long without a change. This is the second time I have seen the beta go 4 or more days with being updated.

 

The four day lag (I don't use the program) in updates might be acceptable if the program had excellent heuristics- but it doesn't which makes it unacceptable if you are correct on update frequency. But remember, there are risks to Beta builds.

 

I can´t agree. OneCare is updating the signatures daily.

 

Is that the beta 2.5 or the current release 2.0 though??

 

Oh, sorry - that´s the current 2.0.
I did not read carefully.

 

I saw your new post in Connect, reldel. I don't understand why they are having this much trouble with just the updating.

Also strange is the lack of info on this beta. Even the OneCare blog has no mention of it though when you look at past posts it mentions 2.0-back betas. In fact it hasn't been updated since November. All you know is that the beta exists but no changelog or any more info about it.

If they ever get this update thing fixed it will be nice.

EDIT: BTW, I finally found me a green "1"