not 100% compatible with Windows Security Center

Geeez.... I really love these threads; the WMI corruption issue has been debated with about every AV/FW product out there. The simple answer is that WMI is buggy like hell and this whole Security Center is a plain waste of resources.

 

Does not change the fact this Betas needs major work.

I personally ain't ever has any issues with Security Centre with ESET v3 or testing any other major AV.

I voice my complaints here so hopefully we get them fixed in next build (where is it?).

Got to laugh at the MS bashers, use a Mac or Linsux then.

 

Thanks for advice, I actually use Linux regularly. There's a simple fact that the whole WMI thing has notorious repository corruption issues encountered with about every security product that registers itself in this "security center" nonsense, you can verify this quite simply by Google search or even this forums search. That's no bashing, that's a fact of life.

Relying on something so buggy to provide you with uptodate status of your security applications is rather naive and the whole thing is plain useless. You already get much more reliable status information from the firewall/antivirus applications themselves, both via their own tray icons and their status screen/monitoring.

 

I know Windows ain't perfect but that does not explain why v3 works perfectly with it for me and v4 does not.

WE NEED MORE BETA BUILDS (I'm not bother about issues if we get more builds).

If a French peep can do it for FREE with VLC on a Daily Basic so can ESET as we pay them.


http://img101.imageshack.us/img101/3540/crapez3.jpg


Windows FW and Defender are perm off for me, I can fix this warning by simply clicking on the ESET options nothing else needed.

 

ESET NOD32 Antivirus and ESET Smart Security v4 Beta 1 are unfinished products which contain errors and therefore not recommended for beginners test users. Also, ESET does not guarantee the quality of beta products.

 

I will repeat my self again till I'm blue ion the DAMN FACE.

I KNOW IT's BETA are you all BLIND and cannot read.

All I want is more builds, so why repeat the same old "Its Beta BS" ?

If I am good enough to be on the MS beta team I can test this crap.

It does not take an expert to find a bug, it happens almost immediately if you try update it lol.

Blaming MS or others is lame as even v3 is buggy and unfinished.

 

LOL. So rename the file and you'll have a new build? Seriously, takes time to reproduce and fix bugs properly and there's absolutely no point in releasing something just for the sake of releasing.

As for this, a Windows feature that happily reports an application as running and up-to-date long after it's been uninstalled, or that reports something as not running and/or outdated while it's obviously false is not something that's usable for serious security purposes.

MS needs to fix this junk so that there's actually a working detection of corrupted repository and ability to rebuild and fix it automatically. Until that's done, the thing is a pathetic gimmick eating system resources and doing nothing useful. Once again, the notorious unreliability of WMI and WSC is not ESET-specific issue at all.

 

I myself have not had a corrupted repository with Vista since SP1 was released. In most cases, public betas are released to get feedback on issues so they can be fixed. This is broken in this beta. It is being pointed out so it can be fixed. This is the only product I have loaded in the last 6 months that does not work. When it does work it is reported as version 3.0. This is not Microsoft's fault. I don't understand why there are so many people trying to defend ESET even when there are bugs. I appreciate their enthusiasm, but I believe in ESET enough to point out bugs I know they are capable of fixing, so they can make a better product. I do not expect any product to be perfect, but if I am paying for it, I expect them to try. Version 4.0 is looking good so far, especially for a first beta, and I hope they do not skip fixing some of the bugs because it is convenient to blame Microsoft.

 

Looking good here! Needs to say Version 4 instead of 3 thats all!

Cheers,

TH

 

Well said, it seems we upset the ESET Fanboys.

MS Security Centre works with other major AV and works for me with ESET v3.
IT is not MS's job to make Windows work with other applications, it is the vendor of these applications to make them work with Windows, since the OS is primary and the apps are made for it.

Vista has been out long enough now and all vendors would have been given time and info to get apps to work in Vista.

Give us 1 beta per week and I will happily waste my time with bugs etc if it helps get v4 finalised in a more fit state than v3 ever was launched in.

 

Riiiight... So, I guess all vendors suck and are completely incompetent, of course except for MS. Because I've seen these issues with Avira, Comodo, Dr. Web, ESET, Kaspersky, Norton, PC Tools, ZoneAlarm etc. etc. etc.

So, they are all incompetent and cannot figure this out... sure, very likely. Go Google this and get a clue.

 

Sure thing n00b, because v3 works for me so is this a fluke ESET got it right ?

I have more a clue than you any day.

 

You need to calm down, both of you.

Read up a bit and you will see that someone is using v4 and the Security Center is picking it up fine, just that it SAYS v3, which probably got missed when the dev's were grepping 3.0 > 4.0 in internal code.

This makes it obvious that it isn't an easy problem to solve, it never is when it works for some and doesn't for others. You can't have nightly builds when you haven't figured out the problem to fix it.

Also I'd much rather ESET keep spending their resources on maintaining support and updates on their current live software than spending it on EXTRA beta time.

When a sufficient quantity of bugs are fixed OR a sufficient amount of features are added AND these are tested to work good, the version number is incremented and a build is released. Also, making a build for a security suite is *somewhat* more complicated than a media player.

I look forward to the next build (beta 2 v4.0.??) since that's when I will start participating in the test.

 

Hey it also picks v4 up fine for me, but not every restart (random same as failed updates) and its easy to rectify anyhow but its not MS to blame.

 

Yep, although I think the whole security center thing is a load of bollocks, it isn't MS to blame in this situation, let's just give ESET a chance to look into wtf is going on and fix it, luckily enough they have so many considerate testers to come here and post the problems they are having. Which in turn leads to better software.

 

@Jenee and @jkuk:

Please refrain from raising the temperature in the forums. All participants in a Beta programme are volunteers and bona fide experienced users, in principle able to notice and reproduce bugs as well as provide informative reports. Eset having an open beta programme

a) without users making an application first, stating their experience; and
b) without providing instructions on what to test and how to report the findings

was IMHO a risky move, but I'm sure they have their reasons.

Therefore, I expect there will be a lot of "noise" in the beta forums, but making innuendos about "n00bs" does cross the line. Please everybody try to calm down and respect the standard forum etiquette.

 

I really couldn't have said it better.

 

Hello,

First of all, I would like to thank everyone for testing the beta test version and giving their feedback to ESET.

I would like to remind everyone that ESET Smart Security v4 just entered beta testing a few days ago, and is going to be in beta for a while in order to help find bugs like the issue which has been reported with Windows Security Center, as well to obtain feedback on usability, features, default behavior and so forth.

Now, with that in mind, let's take a look at what it says right on the home page of ESET's Beta Portal at http://beta.eset.com/:

The problem with the Windows Security Center did not turn up during several months of internal and private beta testing, probably because of the limited size of the test environment as well as the fact that many of them probably have more "pristine" environments (freshly-imaged operating systems, little to no third-party applications installed, no tweaks or customizations applied and so forth). When you are trying to determine whether or not a program follows its design documents, you are going to try and install it in the most basic, lowest common denominator environment, and then as you verify the feature set and functionality, start ratcheting things up to approach to approach the more idiosyncratic types of real-world computer operating environments.

At a certain point, all of the environmental testing that can get done is performed, and that's the point where a software company finds out about the things it missed in its "laboratory environment" by releasing a program into the hands (or computers) of the public for beta testing.

That is where we are at now, and I think it should be very clear to everyone that the public beta test cycle has just started. As such, there are going to be a lot of eyes looking at the software on many different computer configurations and, as a result, bugs and crashes are going to be found and feature requests made on things which simply were not seen or thought during the previous tests.

Last year, when ESET started up its beta test cycle for ESET Smart Security v3, new code releases and refreshes occurred every few weeks, and it would not be unreasonable for someone to assume that the beta test cycle for ESET Smart Security v4 will follow a similar path.

I know that there is a tendency to label everything as "beta" these days and make frequent changes to it, but it is a bit different when you are dealing with a web age you access through your web browser and, say, a program that implements file system and network filter drivers and is hardened to prevent attacks from malware.

Building and internal testing of such software takes time, because the consequences of crashing a web browser session are considered different than leaving a computer in such a state that the only recourse is to reformat it. While I have not looked through every message in the section, I do not recall having seen messages about issues like that, so please keep that in mind when thinking about things like the severity and priority of an issue.

Regards,

Aryeh Goretsky

 

Everyone is now calmed down and playing nice BUT YOU have to stir up trouble !

This Beta is a buggy mess period so deal with that.

The MS SC works with v3 so Google that.

 

Funny, it works just fine here... A.k.a. useless generalization. Regardless, if you can't live and deal with beta SW bugs then you shouldn't use it at all, end of story.

Google what? v4 works just fine w/ WSC here on a clean Windows install. Did you follow the troubleshooting procedures for the WMI junk, or are you just feeling like posting a bunch more of unproductive rants here?

 

Listen LAMER why don't you STFU and actually read what I said about acknowledging its a BETA.

Everyone was playing nice again and a few big mouths inc YOU have to STIR up trouble after its all OVER.

The reason you do that is because in real life your pathetic so instead become a Keyboard Rambo.

As to the GOOGLE part, if you were not so DUMB and actually read all the posts here you would see who and why GOOGLE was mentioned.

Peeps like you who come into a thread days after a little heat has went away and talk a lot of bollocks and stir up trouble make me sick.

 

Somebody was banned for good.

Back to the point, have you guys tried updating your Windows OS? I keep my Windows XP up-to-date at all cost. There's no significant problem except it's showing ESS3 instead. This could be explain by ESS4 is beta and not recognize by Microsoft.

 

It is not Microsoft (Windows) that recognises software , it is the software that by itself reports to the Security Center

 

All betas have problems, they are released for us to test them and report the issues, just wait for the next beta release and i bet this problem won't be there anymore.