pbmcmlxxi

I guess Eset uses a different model than 2 other competitive products I use/test. Through all the previous W10 updates upto release there were no major issues, and from release to 10525 I have no issues with current protection provider, it just continued to work as it did before the update. With these type of releases looking to become the norm (MS updating/patching as/when/frequent) the way Eset works currently seems to cause a lot of issues for customers and workload for your devs.

same here. PLEASE fix it! Agree, the old activation system was a lot easier. It just worked An activation system that won't work every update is frustrating for all.

win 10 v10135 is a leaked build. Not officially released by MS. Latest official and 'supported' 10130. Build 10130 is working correctly with Eset latest Beta released the other day.

@Szaby84 just wondered if it is the same error code you get on the message. ECP.4099 FI - When checking for product updates that bit seems to work without any error.

I went into HIPS, put a tick to enable, then the cross to disable Self-Defence. Rebooted, HIPS as Szaby84 mentioned is disabled upon reboot, the cross remained against Self-Defence and activation failed as previous.

Hopefully they will indeed give you what you need. With the estimated release at the end of July it does not give a lot of time for them to do so. As Szaby84 mentioned ESS V8 works/activates ok on W10, guess ESS V9 has had a lot of code rewrite etc.

Activation issue aside, as per your note on ESS 8 the HIPS in V9 beta was not starting up, so have manually turned HIPS off on the beta.

Hopefully they will. Apparently July is sign off on W10 - (hxxp://www.neowin.net/news/windows-10-signoff-is-slated-for-mid-july) A couple of other Security products I test work ok with W10 10122, so hopefully Eset will investigate and the next update to V9 beta will resolve this activation issue.

Hi Marcos, Got them from the link you gave. hxxp://kb.eset.com/esetkb/index?page=content&id=SOLN332- seems that was under mobile security though - could not see these. Thanks. Tested these - results as below. Activation:register.eset.com 91.228.165.81 - ping ok h1-weblb01-v.eset.com 91.228.165.79 - ping ok h3-weblb01-v.eset.com 91.228.167.123 - ping ok edf.eset.com 137.135.12.16 - Ping timed out edfpcs.trafficmanager.net 137.135.12.16 - ping timed out edf-pcs.cloudapp.net 137.135.12.16 - ping timed out edf-pcs2.cloudapp.net 137.117.215.70 - ping timed out

Hi, this is due to incompatible modules with Win10 build 10122. Unfortunatelly v9 beta cannot be activated on Win10 10122. Updated my initial reply: Comes up with Service Temporarily Unavailable The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.

Just loaded 1st ip in browser and it asked for username/pw. Pinged the ip ok ttl 128. Don't particularly plan on doing that on all of the ip's listed in that KB. If there is a particular IP could would like me to ping, please advise. Thanks. Edit- only looked at top - my bad. The activations were way down the list. Done them and come up with: Service Temporarily Unavailable The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.

Hi. can't activate beta. Not tired on my main pc as yet, only a VM. VM currently W10 *64 10122. Admittedly in notes it says W10 10074 supported. Not sure if it is Activation server issue or that it is W10 10122. Thanks,

Well no official response yet. I have downloaded it and installed it on 8.1 VM. Previous beta came up with the not compatible, this beta didn not have any warning and installed ok. Seems to be working well.

I would also like an answer from Eset on this... I believe someone said the next beta would be, but I can't see it in the changelog.