howardagoldberg

@Marcos @Peter Randziak Splash screen still displays on boot up, despite the fact that the option is turned off in settings. Win7 x 64 11.1.42.1

If the issue does not effect those using the "Antivirus" product, why push out an update that forces the user to reboot? Are there any known issues for those who had a fresh install of 11.1.42.0 who just got upgraded to 11.1.42.1? I am hoping to not have to uninstall and reinstall again as with the last update. Thank you for any guidance you can provide.

@Peter Randziak @Marcos Version 11.1.42.1 was just pushed out via automatic updates, but there is no change log. What is new?

@Marcos @Peter Randziak FYI ... on my Win7 computer, I saw the splash screen flash on the monitor for a moment this morning (didn't notice it yesterday, but I am not necessarily staring at the monitor during boot up) - even though the setting was to turn the splash screen off! I checked to make sure the setting had not reverted, and it was indeed set to off. Unfortunately, that does make me wonder what other settings are not actually being honored. Again, this is a QA issue. I realize the splash screen issue in and of itself is not a security issue and is simply a personal preference ... but if that user defined setting does not function properly one can logically wonder what else is not functioning properly (and for which there would be no visual clues one way or the other)? EDIT: It is possible the issue is also on my Win10 system ... but my Win10 system has a SSD drive and boots pretty fast, so it is entirely possible I just missed it, or perhaps it's a Win7 only issue.

Yes! Thank you for the reminder. On both my systems, the splash screen setting of "off" did not migrate through the in-app update process. I had to turn it back off again.

@Marcos All I can tell you is that when I first responded above, the last successful check for updates was at 8:03 Eastern. Now, the last successful check was at 8:33 Eastern. Seems like 30 minutes to me. I did nothing in between to manually force a check, so this was all the ESET client. The other settings that I reported as not having transferred over - it is what it is, and I am not making it up. They didn't migrate. As others have reported similar issues, this seems like another instance of tests being run only on those receiving pre-release updates or installing from scratch (of course - in that case, there would be not settings to migrate). UPDATE: @Marcos Just to confirm ... successful update checks at 9:03, 9:33, and 10:03. 30 minutes. It clearly works.

@Marcos This is simply wrong. I was easily able to set the interval to 30 minutes, and checking the "last successful check for updates" clearly shows that ESET is checking every 30 minutes, as I have set it to do from within the scheduler settings. I am using ESET Anti-Virus, 11.1.42.0 on both Win7 x64 and Win10 x64.

@Peter Randziak Thank you for this update, it is very much appreciated. I have probably been using ESET for over a decade now, and really do have high regard for the platform overall. Just FYI, I also lost several settings even during the initial in-application upgrade yesterday. Specifically: I had changed the update check frequency from 60 to 30 minutes. During the update, that was reset to 60 minutes. I also had changed the first TLS/SSL setting for certificates from "ask" to "block." That also reverted back to "ask" on the Windows 10 computer (but not the Win7 computer). In addition, on the Win10 system, I moved from regular to pre-release updates twice (before deciding to reinstall). On the second switch to pre-release, ESET threw up warnings that I did not have a valid password, etc. Bottom line is ... there were a number of issues with the in-line install which is why I ultimately uninstalled on both systems, and reinstalled "fresh."

@Marcos It is great that there is no issue with a fresh install (which I can now confirm on a Win10 and Win7 system - since short of any other information earlier today, there was no way to know that a module update was going to be pushed out to more easily correct the situation), and no issue with those on pre-release updates. That makes up the vast minority of users. This update should never have been pushed out without testing on your target audience -- pre-installed with regular updates. That is the issue. No more, no less. This had the potential to cause significant damage to user systems (as was the case for an unlucky few), and by your own account, that configuration was not tested? Short of testing the target configuration before releasing through the auto-update channel (which implies pre-installed and regular update channel!), an immediate notification to users asking them to "wait" on changing settings, reinstalling, etc. as an update was coming would also have saved many of us hours of frustration. That notification came via this forum and via an email - but only after enough time had passed that I and others had gone through a number of steps trying to resolve, which for me ended in uninstalling and reinstalling on two computers and a wasted morning for which I now have to make up that time. As with the Windows Update issue - ESET did not fully test, and did not respond in an appropriate time frame to address the issue. I am pleased that this was resolved relatively quickly, but given how simple the fix was, it should not have taken so many hours with so little communication to correct and inform. Really, it should not have happened. When security software does not function as expected, it understandably makes people nervous. Especially those of us in IT who are responsible for and take security seriously. This and the earlier Windows Update issue (on Windows 10) is honestly giving this very long-time ESET user pause. I am sincerely sharing these thoughts to be constructive. I think ESET is a great product, and these forums have been tremendously helpful. But, I cannot continue to use a product that is going to have these types of issues on a regular basis. I hope the past few months are a blip, and not a pattern.

The quickest and 100% working solution is to not roll out an update that causes more problems than it solves. If ESET only tested the product with machines set to "pre-release," then quality control failed. I have literally spent three hours of my work day trying to resolve this, which is unacceptable. The guidance from the beginning should have been to uninstall and reinstall. I did not need to do so in safe mode, by the way.

I spoke too soon ... the initial scan is running, it is so far scanned 0 objects for 00:00 even though it has been running for 10 minutes. And ... you cannot stop or pause the scan. UPDATE: Issue was only on Win10 system. Win7 initial scan worked as expected. Rebooted Win10 computer (for the 7th or 8th time today now!), and all seems well. This was the most botched update I have ever had to deal with from ESET. I hope they are taking notes. :-)

Yes, well, I just uninstalled 11.0.159 as trying to go back to pre-release caused an invalidation of my username/license key (as with other users) and I finally gave up trying to make it work. On my Win10 system with a SSD, it took less time to start over than to try and fix this mess as it was. The fresh install went smoothly. Still, this kind of error really speaks to poor quality control. This should never have happened.

This is more than an inconvenience. I have spent the past two hours of my work day trying to untangle this. I did not sign up to be a beta tester. How does the new configuration engine not get migrated into the new build if it is an essential component of new functionality?

What if I already reverted back to regular releases? The message is gone. This is really not acceptable.

Ok, FYI. I rebooted. ESET worked normally ... from what I can tell, with the pre-release updates in place. The message is now gone after hitting "accept." I switched pack to regular updates, no issue thus far. Should I wait for a proper update for my other computer (Win7, not Win10 in this case), or also do this pre-release dance?

So what do I do now? It is unresponsive. I cannot stop the task. Should I reboot. Should I wait?

Well, now what? It was frozen. I tried to restart. ESET GUI is not re-loading. I cannot stop the task/process. It is just stuck. I am afraid to reboot the computer because I have a feeling this has really screwed things up.

And now ESET is completely frozen ...

Clicking on "Cancel Update" does nothing ... it is still stuck on "updating product." This is madness. I have work to do!

I switched to pre-release against my better judgement -- it is stuck on "updating product." Now what?

Where? I do not see anything called "Cloud-based protection."

No. I do not run pre-release updates, and should not have to do so in order for ESET to function properly. This is obviously an issue affecting most if not all users.

I am seeing this in the event viewer, which I believe correlates with every time I have clicked "accept" and Windows asks if ESET can make changes to the system: The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

Also ... there are no longer settings for LiveGrid under "Tools."

Same issue here. Click "allow," Windows asks for permission to change settings, but the message remains (Win10, 1709, x64). I do not know what update @BabyMoseN is referring to. After rebooting, I checked for updates and nothing new is coming down after 11.1.42.0.