SweX

Well well well, look who's back. Welcome back mate, long time no seen. I hope life is getting better and that things improve. We have all missed you, the ESET staff is forced to work over time when you're not around the forum with your technical expertise and longtime experience But you have had more important things to take care of so I'm sure they'll understand.

FYI, you have two alternative downloads on this page: hxxp://www.piriform.com/ccleaner/builds Slim = has noting bundled in the installer. And a portable version. Personally I use the Slim.

Very detailed report as always, nice job by AV-C. Hehe, going by AV-C:s experience with Kromtech/Mackeeper. It seems they haven't changed at all since I read this last year: hxxp://www.thesafemac.com/ongoing-mackeeper-fraud/

But Marcos said "v9 doesn't distinguish between regular and pre-release updates during the beta phase." https://forum.eset.com/topic/5409-v9-compatibility-with-windows-10/?p=30217

October 2015 Wow, must be the first time ever I see an ESET rep mention a release date/month (approximate?) in public Times they are a-changin'. Look at Microsoft, all open and humble. Yeah sure, but I am not saying that its only positive. If ESET needs to move the release date forward....there is always a few people that might react like "but you said it was going to be released now buuuuu" By keeping the release info secret until a few days before they plan to release it they prevent these people from feeling let down and disappointed and post their anger on social media or whatever. But personally I don't complain, I know how this works, even if they say October right now, I know that no date is set in stone I don't know about open and humble. I think they seem to think that they do everything right all the time, and if they get some negative feedback, they only come up with a bad excuse. It will be very interesting to see how their automatic WU system works out with Win10 if MS plan to keep the current "high" quality on their updates. WU works fine on 10 already had 2 security updates and 2 updates for windows defender Yes, I am sure the actual update system works as intended I was referring to the quality of some of the past updates that MS have released for Win7 for example.

October 2015 Wow, must be the first time ever I see an ESET rep mention a release date/month (approximate?) in public Times they are a-changin'. Look at Microsoft, all open and humble. Yeah sure, but I am not saying that its only positive. If ESET needs to move the release date forward....there is always a few people that might react like "but you said it was going to be released now buuuuu" By keeping the release info secret until a few days before they plan to release it they prevent these people from feeling let down and disappointed and post their anger on social media or whatever. But personally I don't complain, I know how this works, even if they say October right now, I know that no date is set in stone I don't know about open and humble. I think they seem to think that they do everything right all the time, and if they get some negative feedback, they only come up with a bad excuse. It will be very interesting to see how their automatic WU system works out with Win10 if MS plan to keep the current "high" quality on their updates. The Windows 10, You get what we give and you will do it Now, update policy is a deal breaker for me. Given the stellar updates I've seen and some of the recommended updates that would have, had I actually installed them, turned my system in to a brick. Along with my 5 GB data cap that I have mentioned in another post. I do critical updates ASAP, the rest I manage when the downloads will occur to avoid exceeding my data cap. Sooner or later I get them done but mostly later. @cyberhash: 4 updates is a short Track record. Yeppers , it's those updates I had in mind when I said "high" quality updates. Waiting a week or so is a good idea until MS improve the QC of the WUs. Indeed, 4 updates is nothing compared to how many updates MS will push out during a year, and there will be many millions of computers running Win10 a while after the release that could potentially receive one of those "high" quality updates whether they want it or not. Which means that if something goes wrong it will probably result in a lot of angry customers. "I didn't do anything, what happened!?!"...."ah sorry about that, we just released an update that were supposed to "fix" a problem"

October 2015 Wow, must be the first time ever I see an ESET rep mention a release date/month (approximate?) in public Martin must not have received the memo about giving "release dates". I said you can "expect" the release, I didn't confirm anything , there's no official release date announced yet, but at least two previous versions have been release at that time, so you can "expect" there will be something new released at that time . I didn't confirmed anything officially and I'm not gonna do that before an official PR announcement. No you didn't confirm anything, but I think it's good you point this out as some users tend to take information coming from ESET reps/mods as "official" information. So, without mentioning any details we can say that the final will for sure be out some time in Q4 2015

October 2015 Wow, must be the first time ever I see an ESET rep mention a release date/month (approximate?) in public Times they are a-changin'. Look at Microsoft, all open and humble. Yeah sure, but I am not saying that its only positive. If ESET needs to move the release date forward....there is always a few people that might react like "but you said it was going to be released now buuuuu" By keeping the release info secret until a few days before they plan to release it they prevent these people from feeling let down and disappointed and post their anger on social media or whatever. But personally I don't complain, I know how this works, even if they say October right now, I know that no date is set in stone I don't know about open and humble. I think they seem to think that they do everything right all the time, and if they get some negative feedback, they only come up with a bad excuse. It will be very interesting to see how their automatic WU system works out with Win10 if MS plan to keep the current "high" quality on their updates.

October 2015 Wow, must be the first time ever I see an ESET rep mention a release date/month (approximate?) in public

ESET usually post on the forum when new installers/builds are released. The BETA have only got one automatic software update since install so far, but I have no info about what it fixed.

Before you send the dump you have to compress it (if you haven't done that already). You could use wetransfer.com to send the file. https://www.wetransfer.com/ When the upload is done, copy the download link and send the link in a PM to Marcos on the forum.

Online chart: hxxp://chart.av-comparatives.org/chart1.php?chart=chart2&year=2015&month=7&sort=0&zoom=2 PDF: hxxp://www.av-comparatives.org/real-world-protection-test-march-june-2015/

https://www.nsslabs.com/reports/categories/end-point-protection See separate reports/pdf:s for the 9 tested products on the link above.

https://blog.malwarebytes.org/news/2015/07/introducing-malwarebytes-anti-malware-for-mac/ https://www.malwarebytes.org/antimalware/mac/ https://forums.malwarebytes.org/index.php?/topic/170518-malwarebytes-launches-on-the-mac-with-acquisition-of-adwaremedic/

PDF: hxxp://www.av-comparatives.org/wp-content/uploads/2015/07/avc_anniversary_2015.pdf

Thank you SweX. I have two concerns which is why I asked. The first is my miserably small data allowance and the second is recreating all the rules I have. I appreciate your time to respond. I will be going for the beta on my new computer, the other will be fine till Eset SS is out of beta. I don't think there should be any issues exporting and importing the hips and firewall rules that I have heard of, but if we talk about the settings it may be a bit different, lets say one would import settings from v5 into v8, that may not work to 100% since there is new features in v8 that is not found in v5 so manual tweaking may be needed in those cases. Not that you use v5, but just that the features can differ between each version release depending on what one use and plan to upgrade from. I don't plan on importing my V8.x settings and rules in to v9. But rather import the new settings and rules created in v9 beta to v9 final if that makes sense. In other words redo it all in the beta and import in to final. I just redid them all with an install of v8 on my new computer a month or so ago. So it's pretty clear in my mind what is involved. I finally convinced my wife that she needed my computer and that I needed a newer one and retired the 13 year old XP. You know safety, security and faster computer for her and all that stuff... {whispers .. shhhhh.... it worked for me } Yes that should work fine, if you want to use the beta and not wait until the final is released. Haha oh yes...I'm sure she will understand

Win 10 hasn't been released yet. If it will work or not right now depends on which build of Win 10 you install.

https://www.wilderssecurity.com/threads/analysis-and-exploitation-of-an-eset-vulnerability.377379/#post-2505218 I only post this quote by itman here incase anyone from ESET actually wants to respond....

Thank you SweX. I have two concerns which is why I asked. The first is my miserably small data allowance and the second is recreating all the rules I have. I appreciate your time to respond. I will be going for the beta on my new computer, the other will be fine till Eset SS is out of beta. I don't think there should be any issues exporting and importing the hips and firewall rules that I have heard of, but if we talk about the settings it may be a bit different, lets say one would import settings from v5 into v8, that may not work to 100% since there is new features in v8 that is not found in v5 so manual tweaking may be needed in those cases. Not that you use v5, but just that the features can differ between each version release depending on what one use and plan to upgrade from.

I always recommend a fresh install of the final release, as in uninstalling the beta and install the final. (even if it may official be supported) And I assume that exporting and importing should work fine as usual, at least from v9 beta to final.

It has already been fixed, your URL loads fine here.

Don't think so, but both V8 and V9 Beta will most likely be fully compatible by then, or earlier.

Hello Puffy, 1. I can confirm that I too got IPM 1206B now. 2. Thanks to MMx for clarifying the stable Vs PR updates for the Beta, that explains why we didn't get it earlier

Hi Puffy, I just want to confirm that I am also on 1204B using PR updates. I assume 1206B hasn't been released yet.

No you should not need to restart, I don't know how long time it normally should take for the renewal to sync with the license server and the product, but it could take between 10min to a few hours. It will sync eventually during one of the hourly VSD update checks.