rugk

Yeah and I can understand that they can't take this feedback over such quickly. And yes, good luck with your ECS (Pro) Feedback!

...and it should be fixed yes! @Pentode Is your problem solved now with an upgrade to Windows XP Service Pack 3?

Ok . Think a moderator can help ( you) ------------- My recommendation again ( wait until A moderator Can help you (whoever you PMed) ) This forum ====> very good support in any case ESET ===> good company in any case I&Arakasi&more users ===== > try to help you without choppy sentenses So your issue only happens with Windows 8.1? And as I said maybe the moderator you PMed can help.

If it makes sense you can use wildcards (? and *) in the exclusions. Maybe you can use them to specify your locations with less exclusions.

Try installing SP3, uninstall NOD32 (in safe mode with the special Uninstaller) and reinstall it again. If you're worried you could be infected you can run the ESET Online Scanner or download Malwarebytes Anti-Malware. And about the specialised cleaner: What means it doesn't run? Does it just don't detect any infections or does it displays an error message or what else?

Do you haven't it or don't you want to share it?

Thanks for your answer.

Okay thanks for your answer! That's a good explanation for the two questions.

So we are really 0.0.001 versions away from this bug... Oh no... And will you release another v7 built (7.0.326) with this fixed built?

OK, more simple: I recommend: Install the new version of NOD32 - version 8. After ESET released v8 they still released a new v7 - 7.0.325.x and here. This release was surprising (for me), because there was already v8 out and users can upgrade to v8. It's also surprising for me that the new v7 wasn't released as a PCU (via the GUI-internal "updater"). - That is what you experienced. A reason for this could be that they can only set one version number as the newest version number (e.g. 8.0.304). I thought they want to do this later and because of this they don't want to set the newest version to "7.0.325", because then users have to upgrade to 7.0.325 and (maybe only a few days later) to v 8.0.304. This are only my assumptions. Maybe ESET has a different explanation for this. Related: Changelog for v 7.0.325 @Marcos Okay, so you wanted to release the latest version 7 with fully-up-to-date modules, so if there are users who install the v7 instead of v8, they don't have to update so much (VSDs) and they are already quite up-to-date. Is this right? And there are even some bug fixes in this version. (Changelog linked above) So you wanted to care about v7 although you released v8 already. Is this correct?

And?

There is a new plugin for the Kaseya Virtual System Administrator. hxxp://www.virtual-strategy.com/2014/09/25/eset-launches-plug-kaseya-virtual-system-administrator You can download the plugin at the ESET website.

Of course I would just recommend to install v8. It was already strange that they release a new v7-version and you're right it's strange too that they don't release this v7 update as a PCU. However it can be that they can only register one version (number) as the newest version and ESET wants to do this with v8 later (as I highly assume), so it wouldn't be useful to do this with the "new" v7 before. This are only my assumptions. Maybe ESET has different reasons for this.

Okay, so maybe it will stay in BETA until the far future.

I have experienced something new. You can easily access the ESET (main) site (eset.com) through HTTPS. Just add the s to HTTP and it goes. E.g. you can go to: https://www.eset.com/int/home/products/antivirus-linux/ and you will have a valid SSL connection. Or here: https://www.eset.com/int/about/technology/ But unfortunately you can't download a file (.exe or a .linux executable) through HTTPS. You will be redirected to HTTP and if you try to add the S in HTTPS to the download URL the download will fail. That's very sad, because this would be the important thing. (Why? See my post before as an example)

Thanks, planet. However there was no real new version. The only update was a minor update that should contain some bug fixes, but on my device it instead produced a new bug.

It would be nice if someone from ESET could comment this. Are you aware of this bug?

Well... anyway this is now an issue. And that's not good. @planet Yes, they have different versions. But this is older and wasn't changed with this last release. But they changed the category: Before it was "Tools", now it's "Productivity".

@Skier So you are experiencing the issue too? Is this issue new in v8/Does it happened in v7 too? @waledakmal This is the setting for SSL scanning: It allows your ESET product to scan SSL/TSL-encrypted communications for malware. @all Please follow Arakasis instructions and PM a moderator.

Yeah, thanks to @foneil and @Aryeh Goretsky and thanks to all other people behind ESET! Very thanks for this gift (although I still don't know what exactly it is ), but especially thanks for all the nice products you created! Stick to your principles and enjoy safer technology! Related: ESET Ranks Among Fastest Growing Big Tech Companies in Central Europe for More than a Decade And... @foneil In your first post in this topic, you wrote @SweX's name a bit wrong... And in some of the other names there are missing some letters too.

And if it exists try to load this XML file in the stand-alone version of SysInspector. Edit: FYI the directory where the SysInspector XMLs (from the built-in version) are saved is this dir: %ProgramData%\ESET\ESET Smart Security\SysInspector for ESS (for NOD32 you of course have to use the NOD32 dir).

Now I found the article from WeLiveSecurity about the issue: Tor users targeted with exit node malware

Ok interesting to know. Thanks for your answer Marcos[/member]

SSL scanning? It would be nice if you could provide a bit more information. Proxy? VPN? Anything else important?

Yes like I said I only mentioned it as an alternative for burning. And even it of course has less features and yes it's not such easy to handle. And I didn't compared them. The one who compares it now are you.