mandiato

at the bottom of screen you got "action after scan" and you need to select what you want to do, as you can see it is selected "No Action". Edit: sorry yes, I've got the same problem here, action after scan reffers to action in sense shutdown/sleep etc. When I select from popup menu "scan file" on infected file I got only information tah threats are found, but no options to select cleaning it in any way.

You need to switch to advanced panel and add attachement there, and after that you can add link to it to your post. I've got the same problem some months ago, because this is really not intuitive, and by default you get simple panel when you answer to mail. [edit] I just noticed that it finally changed to new form which allow to attach files, maybe try to <ctrl>+<r> to reload page with all content, sometimes old buffered pages could did some troubles like that

I only want to confirm that this "bug" still exists in ESS... Baza sygnatur wirusów: 14666 (20161226) Moduł szybkiego reagowania: 9238 (20161225) Aktualizacja: 1009 (20161205) Skaner antywirusowy i antyspyware: 1507 (20161209) Zaawansowana heurystyka: 1175 (20161110) Obsługa archiwów: 1258 (20161117) Leczenie: 1128 (20161025) Technologia Anti-Stealth: 1106 (20161017) Zapora osobista: 1328.1 (20161206) Moduł programu ESET SysInspector: 1264 (20161108) Moduł obsługi tłumaczeń: 1565 (20161219) Moduł obsługi systemu HIPS: 1259 (20161213) Moduł ochrony internetowej: 1289 (20161202) Moduł filtrowania zawartości WWW: 1052 (20160620) Zaawansowany moduł ochrony przed spamem: 4832 (20161226) Moduł bazy danych: 1087 (20161107) Moduł konfiguracji (33): 1368.7 (20161214) Moduł komunikacji LiveGrid: 1022 (20160401) Specjalistyczny moduł czyszczący: 1012 (20160405) Moduł ochrony operacji bankowych i płatności: 1092 (20161130) Moduł wykrywania programów typu rootkit oraz leczenia: 1006 (20160715) Moduł ochrony sieci: 1335 (20161223) Moduł skanera luk w zabezpieczeniach routera: 1024 (20161201) Moduł skanera skryptów: 1010 (20161205)

To update drivers itself you need to Device manager and click on devices, wchir reports by ESET that they have updates, and select "Up[date driver". It will find updated file and install it from Windows Download servers. This is a little bit confusing that system in one place reports that update is available, but in place where everybody tries to find it, it won't show up, but this is "good" design by Microsoft last years. Everything is not where it belongs. And system reports it correctly, but built-in tools are won't do what it supposed to do, and don't detect that updates. Fast navigation to get it sorted out: press <windows> + <x> press <y> from opened window select "Device manager" (first option in left panel) on list find device which need to be updated, right click on its name and select first option from pop-up menu "Update driver" [edit] given above link also explain it in details, with screenshots

Maybe source of infection is another machine whioch has got access to NAS files, if so, as long as you don't clean infected machines those files will appear again. It could be virtually anything - including OS on NAS itself.

Those two are different ones. ESS is no longer available to purchase, as in that place came up less featured EIS (it's lack of AntiTheft feature) and richer one ESSP (which has additionally to ESS PasswordManager and Drive/Folder Encryption modules). Details you can find here:hxxp://support.eset.com/kb3753. You still can download and use ESS 10, which is still available as download but only for people who has valid license for it, and you will be able to extend your licence for example for anouther year, two or three, but you simply cannot buy new one (only those available as physical boxes which is on the market are still available and still can be activated). If you cannot download ESS from some department - report it here, as it should be available to download. And about upgrading to ESSP - probably there will be some paid upgrade, but I don't know how much it will costs.

I'm using Pro version, and in work I can check default settings under Enterprise, but this place is by default empty and Policy hive is for changed policies from default settings, so by default and by design this one is empty.

And strange thing happened, when I tried to disable scanning of SSL/TLS it gives me error that I'm not allowed to do so, so to upgrade my Windows Insider build (14942) the only option for me was uninstall ESSP (10.0.174.0) to do Windows Update.

But on my Windows 1607 x64 those registry entry also is not available, so this is no Home version problem only. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Policies] This is registry hive dump from my machine, and as you see there's no EarlyLaunch policy at all.

I also can confirm that. On every boot on windows security log there's 4 entires with info that eelam verification failed becaus hash of file is wrong, so file was modified or corrupted. Here it is part from my log from last boot. And this is SHA256 hash for it: Nazwa dziennika:Security Źródło: Microsoft-Windows-Security-Auditing Data: 01.11.2016 10:39:18 Identyfikator zdarzenia:5038 Kategoria zadania:Integralność systemu Poziom: Informacje Słowa kluczowe:Niepowodzenie inspekcji Użytkownik: Nie dotyczy Komputer: MonsterXXL Opis: Funkcja sprawdzania integralności kodu wykryła, że skrót obrazu pliku jest nieprawidłowy. Plik mógł zostać uszkodzony z powodu nieautoryzowanej modyfikacji. Nieprawidłowy skrót może wskazywać potencjalny problem z urządzeniem dyskowym. Nazwa pliku: \Device\HarddiskVolume9\Windows\System32\drivers\eelam.sys Kod XML zdarzenia: <Event xmlns="hxxp://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" /> <EventID>5038</EventID> <Version>0</Version> <Level>0</Level> <Task>12290</Task> <Opcode>0</Opcode> <Keywords>0x8010000000000000</Keywords> <TimeCreated SystemTime="2016-11-01T09:39:18.931652900Z" /> <EventRecordID>173381</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="320" /> <Channel>Security</Channel> <Computer>MonsterXXL</Computer> <Security /> </System> <EventData> <Data Name="param1">\Device\HarddiskVolume9\Windows\System32\drivers\eelam.sys</Data> </EventData> </Event> Nazwa dziennika:Security Źródło: Microsoft-Windows-Security-Auditing Data: 01.11.2016 10:39:18 Identyfikator zdarzenia:5038 Kategoria zadania:Integralność systemu Poziom: Informacje Słowa kluczowe:Niepowodzenie inspekcji Użytkownik: Nie dotyczy Komputer: MonsterXXL Opis: Funkcja sprawdzania integralności kodu wykryła, że skrót obrazu pliku jest nieprawidłowy. Plik mógł zostać uszkodzony z powodu nieautoryzowanej modyfikacji. Nieprawidłowy skrót może wskazywać potencjalny problem z urządzeniem dyskowym. It says that eelam.sys integration checks failed. Nazwa pliku: \Device\HarddiskVolume9\Windows\System32\drivers\eelam.sys Kod XML zdarzenia: <Event xmlns="hxxp://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" /> <EventID>5038</EventID> <Version>0</Version> <Level>0</Level> <Task>12290</Task> <Opcode>0</Opcode> <Keywords>0x8010000000000000</Keywords> <TimeCreated SystemTime="2016-11-01T09:39:18.929951300Z" /> <EventRecordID>173380</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="320" /> <Channel>Security</Channel> <Computer>MonsterXXL</Computer> <Security /> </System> <EventData> <Data Name="param1">\Device\HarddiskVolume9\Windows\System32\drivers\eelam.sys</Data> </EventData> </Event> Nazwa dziennika:Security Źródło: Microsoft-Windows-Security-Auditing Data: 01.11.2016 10:39:18 Identyfikator zdarzenia:5038 Kategoria zadania:Integralność systemu Poziom: Informacje Słowa kluczowe:Niepowodzenie inspekcji Użytkownik: Nie dotyczy Komputer: MonsterXXL Opis: Funkcja sprawdzania integralności kodu wykryła, że skrót obrazu pliku jest nieprawidłowy. Plik mógł zostać uszkodzony z powodu nieautoryzowanej modyfikacji. Nieprawidłowy skrót może wskazywać potencjalny problem z urządzeniem dyskowym. Nazwa pliku: \Device\HarddiskVolume9\Program Files\ESET\ESET Smart Security Premium\Drivers\eelam\eelam.sys Kod XML zdarzenia: <Event xmlns="hxxp://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" /> <EventID>5038</EventID> <Version>0</Version> <Level>0</Level> <Task>12290</Task> <Opcode>0</Opcode> <Keywords>0x8010000000000000</Keywords> <TimeCreated SystemTime="2016-11-01T09:39:18.928035800Z" /> <EventRecordID>173379</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="320" /> <Channel>Security</Channel> <Computer>MonsterXXL</Computer> <Security /> </System> <EventData> <Data Name="param1">\Device\HarddiskVolume9\Program Files\ESET\ESET Smart Security Premium\Drivers\eelam\eelam.sys</Data> </EventData> </Event> Nazwa dziennika:Security Źródło: Microsoft-Windows-Security-Auditing Data: 01.11.2016 10:39:18 Identyfikator zdarzenia:5038 Kategoria zadania:Integralność systemu Poziom: Informacje Słowa kluczowe:Niepowodzenie inspekcji Użytkownik: Nie dotyczy Komputer: MonsterXXL Opis: Funkcja sprawdzania integralności kodu wykryła, że skrót obrazu pliku jest nieprawidłowy. Plik mógł zostać uszkodzony z powodu nieautoryzowanej modyfikacji. Nieprawidłowy skrót może wskazywać potencjalny problem z urządzeniem dyskowym. Nazwa pliku: \Device\HarddiskVolume9\Program Files\ESET\ESET Smart Security Premium\Drivers\eelam\eelam.sys Kod XML zdarzenia: <Event xmlns="hxxp://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" /> <EventID>5038</EventID> <Version>0</Version> <Level>0</Level> <Task>12290</Task> <Opcode>0</Opcode> <Keywords>0x8010000000000000</Keywords> <TimeCreated SystemTime="2016-11-01T09:39:18.913446400Z" /> <EventRecordID>173378</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="320" /> <Channel>Security</Channel> <Computer>MonsterXXL</Computer> <Security /> </System> <EventData> <Data Name="param1">\Device\HarddiskVolume9\Program Files\ESET\ESET Smart Security Premium\Drivers\eelam\eelam.sys</Data> </EventData> </Event>

Thanks for your time. I try Mandiato's method and nothing happend. Is there maybe a tool to see that hidden folder? Maybe this is a some UTF-8 character used in name which looks like " ", in that case after attrib -h -s -r please push tab key so many times until it shows you " " itself. And dont't forget to ren command, also instead of " " try to use tab key until it shows you " ". Regards

And additionally to that what Marcos said, you have got also some links (not directories) on that pendrive which points to somewhere else (literally "My Download", "My Pictures", "My Videos"). If you put them here intentionally it is not a good idea, but there is also possibility that under that links you have got some links to malware source, so better check where that links points out. [edit] And to unhide that folder in your case in probably fastest way: Right click on WIndows menu and select "Command prompt (administrator)" In opened command prompt type in: f: and press enter And now type in: attrib -h -s -r " " exactly with quotes and one space between them and press enter, this will unhide your folder And now you can easily change name of it by ren " " "foldername" (please replace foldername by name you want) and press enter

If there will be available some kind of upgrade for current ESS Pack to ESSP Pack without waiting to ESS license pass away? That is confusing, no infos abou that, only promoting new product, but no clear path for current licenses to get to higher level. But anyway personally for me ESS is enought :-)

@zfactor I can't say exactly what our product offering will be in the future, but you will continue to be able to activate ESS licenses from boxes. Right now, you can use ESS v10. In the future, there will be an equitable product that the ESS license will activate. I was able to activate EIS with a current ESS License Key. I just can't say 100% that that ability will exist forever. But EIS is less featured product than ESS, and people who bought ESS to get some features, cannot download product which match their licenses, so that is a problem. , and difference between ESS and ESSP is so small (PW Manager and Encryption Storage) that making this as another line product is a littlke bit confusing for users. Maybe a good solution will be migrate all ESS users to ESSP to do not make artificial products, and selling three products: EAV, EIS, ESS. And what I should do? I own ESS pack (3 coomputers + 3 phones for 3 years). And what to do next? In next licence extending. It makes much more noise as it should, especially taking back from sale other product and in that place putting 2 others.

Yes, reported drivers mainly are available thru Automatic Updates in Computer Management / Device manager, and you need to select component and select from pop-up menu (under right mouse key) update driver and next to it select automatic from Windows Update. And it will download latest package which was reported by system to ESET from Microsoft servers and update outdated drivers.

That's not actually 100% correct. Each version has its lifetime which you can see at hxxp://support.eset.com/kb3678/ with information what kind of support is provided for particular versions. Yup, now it's a little bit restricted, but stil users now could get back to v6 and still get definitions update, when 10 will shows up, lowest supported version will be v7. But when I bought my first license for ESET to my home usage it was v3, and nobody forced me to upgrade to v4 and so on, I decided to do it, as new versions gives more security and flexibility, and all of that was without any additional costs. Right now continuing support for all of that versions probably won't be possible due to too big changes in threats itslef and in general in internal works of ESET products.

The most beautiful thing in ESET licensing is that, that when you buy even ESET Smart Security v3, you still have got possibility to install ESS v10, as the key is the same for all versions and subscriptions is for virus definitions and license for using any version of that product, so if you prefer v5, v7 or v9 interface, you could stick with it, but remember that with that versions you won't get new features, only new virus definition files. If anything will be broken in v10, you always could get back to v9, v8 or earlier. Nobody will push you to use latest version - this only ups to you what you choose, but I choose to use v10 after long time spent in betatests, this update is worth of your attention.

I'm in :-)

Is this possible to make available 9.0.141 beta installer? I cannot activate nor update 9.0.117 on latest Windows Pro Insider Preview (10532). ESS 9.0.117 works for me until I uninstalled it, but on that built all tries to install an update by internal mechanisms causes indefined error, so I uninstall 9.0.117 and try to reinstall it, and I cannot any longer activate nor update it. And yes, I know, I know, taht ESET is Beta and Windows is Beta, and I try to test both of them.

Temporary solution - in advanced settings disable SSL/TLS filtering and ESS 9.0.117 will start working for you, but without full functionality, we need to wait to next update which will resolve issues with that. It looks like Win 10 will be one big hell for external developers due to instant changes in internal APIs (HIPS, FW, SSL/TLS and so on so on).