LesRMed
-
Posts
184 -
Joined
-
Last visited
-
Days Won
1
Posts posted by LesRMed
-
-
Tasks-->New Client Task. Shutdown computer is the command you're looking for and then check restart under Settings. When you create the trigger, you can choose a time for it to kick off.
-
Maybe try turning off Memory integrity under Core isolation in Settings. Just a guess though.
-
If you uninstall ESET, can you then install Adobe?
-
I don't believe this only for ESET. It is my understanding that all AV companies will have the same requirement as this is a Microsoft requirement.
-
Been there, done that. See
-
I updates several of my computers on Friday from the Computers screen by clicking the ones I was ready to update and then selecting Update installed ESET products. I assume it would be the same as from the dashboard like you're doing, but I saw no problems. All computers updated and restarted within a couple of minutes.
-
Will do.
-
Description: Active session doesn't timeout
Detail: Numerous times I've had my session time out and return to the login screen while I was working. It just did it to me again, timing out literally two seconds after I clicked a checkbox to select a computer to push an update. Very frustrating! It appears there is a timeout, which is understandable, but not if I'm actively doing something.
-
24 minutes ago, Ryanthecreator said:
Does this erase any data from my OS
No. It just resets the MBR.
-
4 minutes ago, Marcos said:
but perform a true ACS test instead
Obviously, this is not the case, since the OS does not actually support ACS. If, according to Microsoft, KB5006728 has to be installed to have support for ACS, and the installation fails, then the OS does not support ACS. I'm sorry, but your developer is wrong. As @itman said, at system restart it might, but it doesn't after it's rolled back. And once the registry key is added, ESET thinks everything is good (which it's not). Your developers need to take a closer look at when that test is done or do a test at each boot.
-
14 minutes ago, Marcos said:
This value is created regardless of what updates are installed. It's created when an ACS test is successful and the signature is confirmed to be trusted.
Really? I just showed you that's not the case. It shows no ACS support prior to updating, but shows ACS support after the FAILED update. It looks to me that ESET is adding the key when it sees the update, before it's rolled back, resulting in a false entry.
-
The saga continues. Thank you @Marcos. The passwords should have been the same, but I just went ahead and uninstalled the existing installation (in safe mode) and reinstalled using the AIO installer. Everything installed fine.
Went to the Protect console and it was showing the warning about missing ACS support. I checked the registry and found that the HKEY_LOCAL_MACHINE\SOFTWARE\ESET\ESET Security\CurrentVersion\Info\ACSSupport key does not exist. Knowing it wouldn't work, but just wanting to see when things changed, I installed KB5006728 again. After the install, but before restarting, I again verified that the ACSSupport registry key did not exist. I restarted the server, and on reboot I got the screen about applying updates, but then got Failure configuring updates (as expected) and reverting changes.
After the reboot, the warning went away in the Protect console and the ACSSupport key now exists and is set to 1.
So @Marcos, somebody's lying to you about how it checks for support.
I give up.
-
34 minutes ago, itman said:
Is that that a big deal?
It is right now. We have one server here and four at a client's site, one of which is a SBS2011 domain controller which is also running their Exchange server. For the cost and headaches of moving all of them to Azure, I'd rather wait until next year (after a big conversion we're working on that has to happen before the end of the year) to see about upgrading the OS on all of them. The conversion is eating up a lot of my time as it is and I'm basically a one man show.
-
The only way you can get ESU on 2008 R2 now is to move the server to Azure, and that (ESU) is only good until January of next year. MAKs are no longer available for purchase.
-
@Marcos Were you able to determine anything with the logs I submitted?
-
7 hours ago, LT-SYSadmin said:
I already try to install the 22h2 but i cannot from the Microsoft updates or with the Installing Microsoft Support and Recovery Wizard or via the Microsoft Update Catalog.
I had the same issue on two of my computers that were on 1909. I was able to resolve it by using the media creation tool here: https://www.microsoft.com/en-us/software-download/windows10. Click the Download Now and do the upgrade (you don't actually have to create the media).
-
In my research through all of this fiasco, it looks like ESU actually looks for a MAK to determine if the update is allowed. The MAK, of course, has to be purchased from Microsoft and can no longer be purchased. Thank you Microsoft.
-
@MarcosAttached are logs from two servers.
-
9 minutes ago, Marcos said:
you should have no problems upgrading ESET to the very latest version now or after December.
But that's not the case. See the software-install.log file in my first post.
-
I guess I'll just leave them all on 9.0.12017.0 for now and see what happens. Too many other end-of-year projects to upgrade them right now. Thanks for your help and input @itman!
-
I thought I had checked the certificate, but apparently not, I didn't exist, so I installed it. Unfortunately, it made no difference, KB5006728 still fails, as does an update task.
-
-
16 hours ago, itman said:
Eset upon recognizing KB5006728 was installed, deactivated the ACS warning and very possibly now believes all is well in regards to this issue.
@Marcos I believe @itman may be on to something. I just did an update on a Windows 10 laptop that was on version 1909 (one of the two I mentioned earlier). It was showing the ACS support warning in the console. The update failed, but it is no longer showing the warning in the console.
-
Thanks. I did see that. That's the version they're all on now. But I don't think that's going to help after the end of the year.
Unable to Open Main Window of ESET Smart Security or install a new version of the program in my computer
in ESET Internet Security & ESET Smart Security Premium
Posted
Try running he ESET uninstaller in safe mode. See this link: https://support.eset.com/en/kb2289-uninstall-eset-manually-using-the-eset-uninstaller-tool.