Pete12

I just dont understand why ESET is still offering a "buggy" update , while we all know about the bugs of 12.2.29 , ESET must know also by now...........

12.2.30 still not available on the official ESET-site.............why not !! Why this buggy 12.2.29 still offerted............!!!!!!!!!

Yes, everything ok again , just as it was in 12.2.23 !

Just installed 12.2.30 over version 12.2.23 , went fine , did not encounter the bugs we had in 12.2.29......!

Thanks Marcos , for this good news and , please , accept my excuses for my annoying messages , I just need more patience ! Im a 100% customer of ESET , for years , so Im sure all problems will be solved , next week ! Again , thanks a lot for the good work in the forum , have a good weekend !!

I think its a beta-release , not fully tested...............so, for being accurate ; better wait for the final , which will be offered on the ESET-site . Other reason , why you should wait ; when updating your existing EIS ( 12.2.23 or 12.2. 29 ) , you wont get the 12.2.30 , coz its not final yet ........... However , when it is final , you can easily update to latest version , by using your existing ESET ! Anyway , the fact of an available beta-version , proves ESET is working/testing and is aware of the bugs /problems with 12.2.29 ........

Will see how it behaves next days ( updating, etc.) , you installed it over the 12.2.29 ?

Better wait for the real final , to avoid any bugs ...................! Besides, 12.2.23 works very good , Im not in a hury

The "official " ESET-site keeps giving us the buggy 12.2.29 .........why ?? So , when updating the program , inside 12.2.23 , we still get 12.2.29........!!

OK, will make a backup first , then update in 12.2.23 , hopefully it will take the new 12.2.30 !

" with fixes "..........Marcos , how to install this update ; 1 . just in the program 12.2.23 , update 2. using the new 12.2.30 set-up 3. uninstall 12.2.23 first , then using new set-up ??

" A lot of people , and so am I, are very , deeply dissapointed in the reactions of ESET ,according to all these bugs as described in these forums ( 12.2.29 ) .....................no reactions at all !!!! I do hope they will finally DO SOMETHING about it ...........thinking of ending my ( paid) subscription..........

Yes, its a well known bug by now ..........it appeared with this buggy update to 12.2.29 . Rolled back to previous version 12.2.23 , with NO BUGS at all !! I dont understand why (!) ESET still did not react .............WHEN WILL THESE TROUBLES GET FIXED !!! I contacted support already , they want to look in my PC , but whats the use without a new update , its not our OS , this is an ESET-problem ...................!!

Still no answer anymore ................I understand , there is only one (1) good answer ; a new update from ESET , this time without a red eventlog and keeping your settings in Windows Defender..............!!

" Posts: 16200 Kudos: 2941 Joined: February 8, 2013 Location: Slovakia Report post Posted 10 hours ago Let's try it with the next version when available "..............yes, and , please , dont let us wait too long..........!! btw; found another failure of the 12.2 29 ; bootime needing a few seconds more then the 12.2.23 .........so , all these faults together , its real time for getting 12.2.29 straight ........correct it , or update it better ( soon !).......

" I went through the hassle of uninstalling 12.2.29 and then reinstalling it "...............yes, re-installed twice , same results ! I stay on my conclusion ; this 12.2.29 is a "no good " update !! Reverted to good 12.2.23-version , NO PROBLEMS at all with this version , will stay with it , untill a final good ( !) update will appear , with none of all the problems , I described in my last posts . Just dont understand WHY (!) they keep pushing people to this buggy version ( )still ................when will ESET wake up and stop with 12.2.29 , they should know by now about all these troubles ............! They blame MS , but 12.2.23 has no problems at all , while its in the same OS.................

" Posts: 16184 Kudos: 2940 Joined: February 8, 2013 Location: Slovakia Report post Posted 5 hours ago "First of all, I have no clue what issues you mean. Are any issues visible after installing v12.2.29? "..............did you read previous posts ? Have you seen my txt-files ? Will explain again some issues ; 1. The Windows Defender option for periodic scanning ( on/off) , always set to "off" , after every reboot . 2. Our eventlog is turning red ( with errors , id=18 and id=19 ) , not very funny , if you try to keep your eventlog clean ! 3. No repair-function in the new 12.2.29-installer , only "remove"is still present . 4 . four (4) ! ,providers in the Security Center ( key in regedit ) , you blame MS , which I think could be right, but a fact is ; version 12.2.23 has NO PROBLEMS AT ALL , all problems started with this 12.2.29 !! 5. I dont understand why ESET still keeps pushing this 12.2.29 to the people , isnt ESET still not aware of all the facts I mentioned above ............?? !! Why not pulling out this nasty update , untill problems are fixed , with the help of MS ?

" soon after the tests are finished "...………..sorry to say ( excuse me !) but we may assume ESET does some severe testing first , before giving to the public ( updating version) We wonder if this severe testing has done on 12.2.29 (?) ………..if so , then we never had these troubles in the first place……..!! Costed us all a lot of time ( reverting to previous version, with uninstalling , etc.) searching for solution , checking OS , reporting support, etc, etc...………….. Lets hope ESET will be very carefull with next updates in the future………...

I see , so problems with 12.2.29 still not solved……………..!

So you have not the id=18 and id=19 in your eventlog ?? If not , the problems are fixed by ESET................??!

" No errors in event viewer, related with Eset. But I'm using Eset from yesterday :D. For now all works perfect. "...............?? You must be the only one ! Which version are you using now ; 12.2.23 or 12.2.29 ??

Big mistake ; removing the " repair-function" in the 12.2.29-installer , its , fortunatly, still present in 12.2.23 ! This mistake is one of the many bugs in this 12.2.29-version , would be very ( !!) welcome when are these bugs/mistakes are repaired with a new solid, good update !! Come on, ESET , dont let us wait too long...............!!!

Just totally uninstalled this buggy 12.2.29 and installed version 12.2.23 .......works awsome ! No more " blody red " eventlog ( full with id=18/19 ) and .....it stays on the settings in the Windows Defender ...................thinking of keeping this version , untill a good working new update appears !

" it don't use the key "...............you mean , dont activate and turn off app.update ?? Problem is ; you dont get the time to import your settings , immediately reboot and .............beng ( ! ) 12.2.29 again .......

" I'm seeing these Windows Defender related entries only after upgrading to 12.2.29.0. "..........this is another proofe of a buggy , faulty update ! Eset should give us a possibility to STAY ON 12.2.23 ( !!) , untill a solution appears ! Still no answer on my question ; HOW to stay on 12.2.23 , without being pushed to this buggy 12.2.29 ............. Any idea would be very welcome !