Marcos
-
Posts
36,489 -
Joined
-
Last visited
-
Days Won
1,452
Posts posted by Marcos
-
-
6 minutes ago, Marius said:
No error with EIS, seems to work just fine, no warnings.
That's good to hear
I assume that after uninstalling EIS and installing ESET NOD32 Antivirus it should work alright then as well.
You can do it through the product -> Change product but don't forger to change the license key for your own afterwards:
-
I see now. Perhaps you could use "Schedule once" as a trigger and then define a random delay for triggering the task:
-
The issue is not related to v12. What fixed it was an overhaul of a several years old code in the firewall module.
Modules on pre-release update servers are typically those that are later released for all users since not many users update from the pre-release channel. We generally recommend using pre-release updates for technically savvy users on non-critical systems. I for one can hardly remember severe issues caused by using modules from the pre-release channel. By using the pre-release channel, you get early access to fixes and improvements with the possibility to switch to regular updates in case of an issue which is not possible when using regular updates.
-
11 minutes ago, Marius said:
I've been away for a couple of days, sorry for the delay. I hope I did everything right this time,
Are you getting the error also with ESET Internet Security installed? I'm asking because there's no error logged in the event log and all drivers are loaded as well. I will get the diagnostic logs checked by developers but I don't see any obvious issue there either.
-
Just for clarification, by "trigger for update" you mean the Update modules option?
-
Does switching to pre-release updates in the advanced setup and downloading the latest modules make a difference?
If possible, try temporarily uninstalling EIS and installing ESET NOD32 Antivirus. It would be valuable for us to know if that makes a difference in terms of the network speed or not.
-
Is the computer connected to the Internet? How much time has passed since you marked the device as "not missing" in the Anti-Theft portal? Do you have the latest version of EIS 12.1.34 installed?
-
Do you use an htttp proxy? It sounds like each client downloaded updates directly from ESET's update servers.
-
Yes. Especially trivial detections are replaced with more sophisticated ones that can cover many more variants of the malware.
-
I was unable to find a license by the email address you used to register in this forum so I assume you used a different registration address for your license.
First of all, do you have a license for Endpoint and server products or for consumer version? While my.eset.com serves for home users, ELA and the new EBA portal are intended for managing business licenses.
If you have an EBA account created but no license added there, you could change your password to a temporary one and provide me with the email address and the password so that I could try it myself. Anyways, the best course of action would be raising a support ticket so that the case is properly handled and tracked.
-
7 hours ago, sollysolutions said:
Error code also popped up in Chrome
Resolved with a machine reboot
Thanks
Most likely you had to reboot after an upgrade to the latest version 12.1.34 which has brought a fix for the issue.
-
I would suggest raising a support ticket for customer care since further logs will be needed and to have the case properly handled and tracked.
-
I'm sorry to hear about the issues you encountered, however, ESET's products are popular and highly awarded worldwide. I for one haven't heard about issues connected with our products that would cause disruption of user's workflow. I would strongly recommend customer care first since it sounds you are having bigger problems with your system and that are not caused by ESET that would not most likely be sorted by getting a refund and uninstalling it. Of course, a refund is possible within 30 days since the purchase if I remember correctly.
-
I'm afraid you fell victim of a scam since you most likely didn't contact ESET through the official website www.eset.com/us that is maintained by ESET, LLC from San Diego. Firstly, ESET still supports Windows 7 and will continue to support it for the next few years. We even still offer v9 which officially supports Windows XP. Secondly, the price for ESET's products is much lower. The price for ESET NOD32 Antivirus for new customers is below $40 and even less if you are purchasing a renewal:
-
1, Since it was found in the WinSxS\temp\PendingRenames folder, judging from the name of the executable I assume it was created during a Windows update.
2, Probably because Windows update attempted to download and install it again and again.
3, Windows update should install it alright once it's not detected / blocked. Still, it's just a hunch that it was Windows update that generated the file.
-
Problem je, ze ste po instalacii prepli firewall do uciaceho sa rezimu, v ktorom je standardne 2 tyzdne. Pocas tejto doby sa automaticky vytvaraju povolovacie pravidla pre vsetku komunikaciu. Po ukonceni uciaceho sa rezimu ste prepli firewall do administratorskeho rezimu, teda nove pravidla sa uz dalej nevytvarali, ale aplikovali sa existujuce. Vzhladom na to, ze napr. pre utorrent sa vytvarali velmi specificke pravidla pre konkretny vzdialeny port a IP adresu, po zmene do administratorskeho rezimu prestal komunikovat, ak sa neaplikovalo ziadne z existujucich pravidiel.
Odporucal by som zmazat vsetky pravidla a pouzivat automaticky rezim. Ak chcete pouzivat uciaci sa rezim, v pripade blokovanej komunikace tento vyzaduje reviziu pravidiel a pripadne ich zovseobecnenie, tj. napriklad zrusenie vzdialeneho portu a IP adresy v pravidle a ponechanie iba 1 pravidla pre konkretnu aplikaciu.
-
We don't know yet. If you don't want to use pre-release updates, stay on regular updates and the module will be updated automatically after some time.
-
Dodajte nam, prosim, logy zozbierane nastrojom ESET Log Collector, aby sme mohli skontrolovat konfiguraciu a firewallove pravidla, ktore mate vytvorene.
-
Please check if C:\Windows\Temp isn't full of redundant temporary files. If it is, delete them.
If that's not an issue, enable advanced network protection and update engine logging in the advanced setup -> tools -> diagnostics, run update, then disable logging and gather logs with ESET Log Collector for perusal. You can upload the generated archive here.
-
Product: ESET Security -- Error 1923. Service 'ESET Service' (ekrn) could not be installed. Verify that you have sufficient privileges to install system services.
A Procmon log from a failed install might shed more light. I'd suggest raising a ticket for customer care and providing them with both the Procmon log and fresh ELC logs gathered after the failed install. You can provide me with a download link to the logs as well but it's important that the case is properly handled and tracked by customer care.
-
If you uninstall the KB does the icon re-appear? Have you tried uninstalling ESET and installing the latest version 12.1.34 from scratch?
-
1 hour ago, Zen11t said:
When PCU will be enabled on ESET servers?
If I remember correctly, it should happen after the next service release in 1-2 months. By the way, it will be uPCU, not PCU.
- Peter Randziak and karlisi
-
2
-
9 minutes ago, Ferdin said:
Also had the same issue, the activation key has not been received yet
Please contact the seller from whom you purchased your license. Since you are from the US, I assume you purchased it from ESET, LLC.
-
What do you mean by "flash memory"? A USB stick? What version of Windows do you use? What threat was detected by ESET? Please post the appropriate record from the Detection log.
I assume that after uninstalling EIS and installing ESET NOD32 Antivirus it should work alright then as well.
12.1.34.0 + Windows 1809 = Extreme upload speed degradation bug
in ESET Internet Security & ESET Smart Security Premium
Posted
We know but that was a very old code that had to be rewritten. Probably recent Windows updates have caused the issue to manifest since users hadn't reported it until recently.