Jump to content

autobotranger

Members
  • Posts

    51
  • Joined

  • Last visited

Everything posted by autobotranger

  1. I'm just using Nod 32 Antivirus and not the other versions, but I'm also seeing some strange behaviour after I was upgraded to version 12.2.29.0. After rebooting to complete the update I got a notification from the Windows action center that said something aloung the lines of "neither Eset or Windows Defender is turned on", even though Eset was all green in the Windows Security Center and running in the taskmanager. I have not been able to recreate that though, it only appeared after upgrading to 12.2.29.0 and rebooting to finish it. Now whenever I turn on my computer it would seem that Windows Defender is doing something in the taskmanager for a couple of minutes and then goes away. It's worth pointing out that I do not have periodic scanning for WD turned on in settings and never have. Screenshots attached. Should I be worried about this? Also I forgot to mention that there also seems to be a few errors related to this in the Eventviewer. A new one seems to appear after every reboot since upgrading to 12.2.29.0. Translation: "The service Windows Securitycenter could not read occurences of AntiVirusProduct from the datastorage"
  2. Hello again. After Archive module 1283 was installed the "QUICKBATCH" errors no longer appear in scan logs! So it would seem the problem has been corrected. I'd say we can mark this as solved ­čśŐ
  3. Ah I see, then it should be fine. Thank you for the update ­čśâ Would you like me to let you know if any more of these detections starts to appear in the future scan log for files?
  4. Thanks for the reply. Good to hear that these are being looked at.
  5. Hello again. Do we have an update in regards to these "QUICKBATCH" detections? It's worth noting that I have checked all the files in question on VirusTotal and they all came out green. I have always used HitmanPro to check them and the rest of the PC and it doesn't pick up anything either. Thanks in advance.
  6. I've PM'd you the download link for the various files. If they don't work let me know and I'll upload them elsewhere. Also it would seem that I missed 2 "QUICKBATCH" entries in the prior scan log: It turns out there is also 2 entries for "QUICKBATCH" for the two Windows10.0-KB4480116x64.cab detections. Pretty sure that one is from yesterdays patch Tuesday update. Sorry for missing it in my first post.
  7. Hello everyone. Since updating Windows 10 to version 1809 and Eset Nod32 Antivirus to version 12.0.31.0 I've noticed some interesting results in the log after performing a full system scan. I'm fully aware that all results that show up in yellow text is currently in use by the OS or other programs, and should be safe, but these particular entries I'm a little suspicious about due to Eset's description of them: The results I've marked translate from Danish to English as follows: "QUICKBATCH - error - unknown compression method." What's interesting is that prior to yesterdays Windows 10 patch Tuesday update bringing my OS to version 17763.253, Nod32 only showed 2 of these entries in the scan logs, but now it shows 4 of them. While results shown in yellow text should be safe, it's the classification as QUICKBATCH I'm concerned about https://www.virusradar.com/en/search/all/quickbatch Are these just harmless Windows 10 system files, hence why Eset doesn't show them in red, or is this something we should take a look at? Thanks in advance. BUMP* Turns out there was 2 other detections in the same scan log. Sorry for missing them:
  8. Ah I see. I will edit my original post then. And good to hear that my version of Nod32 AV is compatible. Sounds good! Thank you guys.
  9. Hello. I see that Windows Update is now offering the new Windows 10 October 2018 Update (Redstone 5) and I'm simply wondering if Eset Nod32 Antivirus 11.2.63.0 is ready for and fully compatible with the new W10 version? Thanks in advance.
  10. Hey guys. Seems like something similar is happening on my end, though I'm using Eset Nod32 Antivirus. I ran a manual update in Eset and noticed that it took quite a few minutes for it to finish. Usually it only takes a few seconds. Being curious, after the update had finished, I clicked update again to see if it would act the same way this time. It kept hanging for a while and eventually came with an error in red text "Product was not updated. Transfer was interrupted" (translated from Danish). Screenshots attached: As you can see the first update went through, even though it took several minutes. Choosing to manually look for updates again resulted in this error after several minutes of hanging.
  11. Okay, so at least it isn't just on my end then. Forgive me, but what exactly do you mean by "your Eset HIPS protection status is not affected by these error messages."? Does this mean that I in theory can't trust the Green status for my HIPS because of errors and that it may in fact not be working as intended, even though the Eset UI shows everything as "on"? So far they have only appeared once, yes. I have powered down my computer many times, since installing Nod32 again, as I always turn off my computer when I'm not at home. But I'd really like to know if my Nod 32 and HIPS is actually working as intended, so perhaps it would be for the best to simply send you a memory dumb and ESET Log Collector log anyway? I would just need instructions on what exactly to do.
  12. Hello again. I finally decided to upgrade to Windows 10 Spring Creators Update 1803 (build 17134.112). My W10 version is Windows 10 Home 64-bit edition. Before doing so I completely uninstalled Eset Nod32 Antivirus 11.1.54.0 from the machine to avoid potential conflicts doing the W10 upgrade. Yesterday I did a clean reinstall of Eset Nod32 Antivirus using the Live-Installer from the official website. Now I've noticed 2 HIPS related errors in the Nod32 event log. Translation from Danish to English: "Communication with the driver failed. HIPS is inactive." and "The module wasn't read/loaded. Changing of HIPS-settings doesn't work correctly." Judging by the time stamps of the events, this appears to be about right after I reinstalled Eset Nod32 Antivirus on my system. Can't say I've ever noticed any errors regarding HIPS in the 6+ years I've been using your program, so this is quite concerning to me. As you can see by the two other screenshots I have attached, Eset claims that HIPS is very much running and everything is green. And here are the current module versions for the sake of it. So any ideas as to why those 2 HIPS errors have shown up in my Eset Nod32 Antivirus event log? Should I be concerned for my computers safety? I have never seen anything marked in yellow/gold appear in my event log related to HIPS until now. Please respond and thanks in advance.
  13. Hello. I finally decided to upgrade my Windows 10 machine to Spring Creators Update bringing my OS to version 1803 build 17134.112. Before doing the upgrade from W10 version 1709 I decided to uninstall my Eset Nod32 Antivirus version 11.1.54.0 to avoid any potential conflicts and issues doing the Windows 10 upgrade. So far everything seems smooth (fingers crossed). I have now reinstalled Eset Nod32 Antivirus version 11.1.54.0 using the official Live-Installer from the website and the installation was a succes. However, I have now noticed something new in the Task Manager. Under services I now see that an additional service next to ekrn is running named ekrnEpfw described as "Eset Firewall Helper". Screenshot attached to this post. This appears to be something new as this additional service was not showing when I was running Eset Nod32 Antivirus version 11.1.54.0 on Windows 10 version 1709. My question is, what exactly does it do and why didn't it appear in the task manager on OS version 1709, despite being the same version of Eset Nod32 Antivirus? Is this something newly added for the new W10 Spring Creators Update? I'm especially curious about this since I believe the Antivirus version of Nod32 has never contained anything related to Firewall before? I also should add that I am running the standard Windows 10 Firewall built into the OS. Hopefully someone from the Eset team can answer this. Thanks in advance.
  14. All of this doesn't sound very good. I think I'll just try an stay on version 1709 for a while longer. Thankfully my system was actually able to receive and install the May 8th cumulative update (KB4103727) and not install Creators Update 1803 aloung with it. Of course it keeps nagging me to update to 1803, but that's Windows 10 for you..
  15. Oh dear that doesn't sound so good. Any chance one of the people working at Eset could respond to this thread? Is Nod32 AV v 11.1.54. fully compatible with Windows 10 Spring Creators Update 1803? Aside from maybe this ui issue MrWrighty mentions.
  16. Greetings. Is Eset Nod32 Antivirus version 11.1.54. fully compatible with the new Windows 10 Spring Creators Update 1803? Thanks in advance.
  17. Greetings. It would seem that Windows Update wants to download a new update for the Windows 10 in the form of KB4093112 bringing the OS version to Build 16299.371. I was simply wondering if Eset Nod32 Antivirus version 11.0.159.9 is fully compatible with this new update? I haven't upgraded to version 11.1.42.1 yet due to some of the problems I've read about for that version (I do believe that is the latest version?) Thanks in advance.
  18. I see. Thank you for the answers, Planet and Marcos
  19. Hello Eset crew. My Eset Nod32 Antivirus just automatically updated from version 11.0.154.0 to version 11.0.159.0 I've noticed that the installed modules appear to be the same version numbers as they were in version 11.0.154.0. Is this intentional with the new version that just installed on my machine? Here's the list of the installed modules (Danish UI) : Registreringsprogram: 16605 (20171220) Modulet Hurtigt svar: 11289 (20171220) Opdateringsmodul: 1010 (20170621) Antivirus- og antispywarescannermodul: 1533.2 (20171205) Avanceret heuristikmodul: 1184.1 (20171212) Arkivunderst├Şttelsesmodul: 1270 (20171113) Rensemodul: 1152 (20171127) Anti-Stealthsupportmodul: 1118 (20171108) Firewallmodul: 1371 (20171013) ESET SysInspector-modul: 1270 (20170808) Modul til overs├Žttelsessupport: 1638 (20171018) HIPS-supportmodul: 1306 (20171127) Internetbeskyttelsesmodul: 1319 (20171024) Modul til webindholdsfilter: 1058 (20170406) Avanceret antispammodul: 6384 (20171102) Databasemodul: 1095 (20171206) Konfigurationsmodul (33): 1565 (20170919) LiveGrid-kommunikationsmodul: 1041 (20171107) S├Žrligt renseprogram: 1012 (20160405) Beskyttelsesmodul for bank og betaling: 1114 (20171018) Registrering af rods├Žt og rensningsmodul: 1019 (20170825) Modul for netv├Žrksbeskyttelse: 1581 (20171218) Modul til scanning af routers s├ąrbarhed: 1041 (20170925) Scriptscannermodul: 1026 (20171205) Tilsluttet hjemmenetv├Žrksmodul: 1017.1 (20171018) Modul til kryptografisk protokolsupport: 1025 (20171106) Thanks in advance.
  20. My Eset Nod32 Antivirus just updated to version 11.0.154.0, but I can't seem to find a change log for this new version anywhere. Any ideas?
  21. Okay. I thought it looked strange so that would explain it. Thanks for the swift reply
  22. I finally decided to upgrade my Windows 10 to the new Fall Creators Update and before doing so I uninstalled Eset NOD32 Antivirus version 10.1.235.1 in order to prevent any potential conflicts doing the W10 update. When I concluded that everything seemed in order with the OS after the update, aside from my screen brightness going haywire, I went ahead and installed the new Eset NOD32 Antivirus version 11.0.149.0 (danish UI) using the Live Installer. The installation was a succes and I went on with my daily routines. Though I've noticed something rather odd regarding v.11 and I'm wondering if this is now intended? In any of the previous versions of NOD32, these results, that are files currently used by the OS or other programs ("kunne ikke ├ąbne" means "could not be opened"), where not outlined in red text. For some reason, in version 11 all the results are now marked with red text in the scan logs. Is this intended or is this some sort of an error? It seems odd that all the results would suddenly be outlined in red, usually indicating a warning, when they all used to be simple black (or was it blue? I already can't remember..) text in the previous versions of NOD32. So yeah, in short. Is the new red text intended for all scan results, and not just absolute warnings, or is this some sort of error?
  23. This exact same "bug" also occurs for me, but I'm currently still on NOD32 Antivirus version 10.1.235.1 Never saw this happen in the previous version of version 10. It started after the automatic update to the current version of v10. It sometimes happens when refreshing Live Grid and then it goes back to normal after another refresh.
  24. Hello again. Sorry for the late reply, but life got in the way as it sometimes does. I have now attempted all of your suggestions from the post above, without success unfortunately. This post will be rather long as I have documented the entire run through: I already had my file explorer set to show hidden folders and files. Despite this, GAC_MSIL can still not be found under the specific directory. I even attempted to find it while in safe-mode. I uninstalled the game via the Steam client and ran Ccleaner afterwards followed by a reboot of the system. Unfortunately, the problem still persists, plus a couple of new additions. Though I'm not certain if those are caused from an update I cancelled for the game Team Fortress 2. MBR-sektor for 2. fysisk disk - fejl ved ├ąbning af C:\hiberfil.sys - fejl ved ├ąbning af C:\pagefile.sys - fejl ved ├ąbning af C:\System Volume Information\{069313ea-095d-11e7-8a6f-d8cb8ac74018}{3808876b-c176-4e48-b7ae-04046e6cc752} - fejl ved ├ąbning af C:\System Volume Information\{06931447-095d-11e7-8a6f-d8cb8ac74018}{3808876b-c176-4e48-b7ae-04046e6cc752} - fejl ved ├ąbning af C:\System Volume Information\{3808876b-c176-4e48-b7ae-04046e6cc752} - fejl ved ├ąbning af C:\System Volume Information\{4cf8617d-13a4-11e7-a2de-d8cb8ac74018}{3808876b-c176-4e48-b7ae-04046e6cc752} - fejl ved ├ąbning af C:\System Volume Information\{5bffe9fc-fdcd-11e6-a182-d8cb8ac74018}{3808876b-c176-4e48-b7ae-04046e6cc752} - fejl ved ├ąbning af C:\System Volume Information\{7f9dd97d-0e3b-11e7-aff8-d8cb8ac74018}{3808876b-c176-4e48-b7ae-04046e6cc752} - fejl ved ├ąbning af C:\System Volume Information\{b67727fd-10a5-11e7-a9b9-d8cb8ac74018}{3808876b-c176-4e48-b7ae-04046e6cc752} - fejl ved ├ąbning af C:\System Volume Information\{b78b23fc-0347-11e7-b497-d8cb8ac74018}{3808876b-c176-4e48-b7ae-04046e6cc752} - fejl ved ├ąbning af C:\Windows\assembly\GAC_MSIL\System.Data.SqlXml\2.0.0.0__b77a5c561934e089\System.Data.SqlXml.dll ┬╗ SMARTASSEMBLY ┬╗ deobfuscated.exe - handlingen kan ikke udf├Şres C:\Windows\Installer\25e0a.msi ┬╗ MSI ┬╗ media1.cab ┬╗ CAB - fejl ved l├Žsning af arkiv C:\Windows\Microsoft.NET\Framework\v2.0.50727\System.Data.SqlXml.dll ┬╗ SMARTASSEMBLY ┬╗ deobfuscated.exe - handlingen kan ikke udf├Şres C:\Windows\Microsoft.NET\Framework64\v2.0.50727\System.Data.SqlXml.dll ┬╗ SMARTASSEMBLY ┬╗ deobfuscated.exe - handlingen kan ikke udf├Şres C:\Windows\winsxs\amd64_netfx-system.data.sqlxml_b03f5f7f11d50a3a_6.1.7601.17514_none_141b1b1223b1ada7\System.Data.SqlXml.dll ┬╗ SMARTASSEMBLY ┬╗ deobfuscated.exe - handlingen kan ikke udf├Şres C:\Windows\winsxs\amd64_netfx-system.data.sqlxml_b03f5f7f11d50a3a_6.1.7601.18523_none_141c340a23b0aa84\System.Data.SqlXml.dll ┬╗ SMARTASSEMBLY ┬╗ deobfuscated.exe - handlingen kan ikke udf├Şres C:\Windows\winsxs\amd64_netfx-system.data.sqlxml_b03f5f7f11d50a3a_6.1.7601.18529_none_141bab5a23b1444a\System.Data.SqlXml.dll ┬╗ SMARTASSEMBLY ┬╗ deobfuscated.exe - handlingen kan ikke udf├Şres C:\Windows\winsxs\amd64_netfx-system.data.sqlxml_b03f5f7f11d50a3a_6.1.7601.19091_none_1423663a23aa2435\System.Data.SqlXml.dll ┬╗ SMARTASSEMBLY ┬╗ deobfuscated.exe - handlingen kan ikke udf├Şres C:\Windows\winsxs\amd64_netfx-system.data.sqlxml_b03f5f7f11d50a3a_6.1.7601.22733_none_fd4f8d703d572432\System.Data.SqlXml.dll ┬╗ SMARTASSEMBLY ┬╗ deobfuscated.exe - handlingen kan ikke udf├Şres C:\Windows\winsxs\amd64_netfx-system.data.sqlxml_b03f5f7f11d50a3a_6.1.7601.22740_none_fd50d2123d55f0a6\System.Data.SqlXml.dll ┬╗ SMARTASSEMBLY ┬╗ deobfuscated.exe - handlingen kan ikke udf├Şres C:\Windows\winsxs\amd64_netfx-system.data.sqlxml_b03f5f7f11d50a3a_6.1.7601.23290_none_fd55d61e3d516aeb\System.Data.SqlXml.dll ┬╗ SMARTASSEMBLY ┬╗ deobfuscated.exe - handlingen kan ikke udf├Şres C:\Windows\winsxs\msil_system.data.sqlxml_b77a5c561934e089_6.1.7601.17514_none_05d4965a61a326fa\System.Data.SqlXml.dll ┬╗ SMARTASSEMBLY ┬╗ deobfuscated.exe - handlingen kan ikke udf├Şres C:\Windows\winsxs\msil_system.data.sqlxml_b77a5c561934e089_6.1.7601.18523_none_05d5af5261a223d7\System.Data.SqlXml.dll ┬╗ SMARTASSEMBLY ┬╗ deobfuscated.exe - handlingen kan ikke udf├Şres C:\Windows\winsxs\msil_system.data.sqlxml_b77a5c561934e089_6.1.7601.18529_none_05d526a261a2bd9d\System.Data.SqlXml.dll ┬╗ SMARTASSEMBLY ┬╗ deobfuscated.exe - handlingen kan ikke udf├Şres C:\Windows\winsxs\msil_system.data.sqlxml_b77a5c561934e089_6.1.7601.19091_none_05dce182619b9d88\System.Data.SqlXml.dll ┬╗ SMARTASSEMBLY ┬╗ deobfuscated.exe - handlingen kan ikke udf├Şres C:\Windows\winsxs\msil_system.data.sqlxml_b77a5c561934e089_6.1.7601.22733_none_ef0908b87b489d85\System.Data.SqlXml.dll ┬╗ SMARTASSEMBLY ┬╗ deobfuscated.exe - handlingen kan ikke udf├Şres C:\Windows\winsxs\msil_system.data.sqlxml_b77a5c561934e089_6.1.7601.22740_none_ef0a4d5a7b4769f9\System.Data.SqlXml.dll ┬╗ SMARTASSEMBLY ┬╗ deobfuscated.exe - handlingen kan ikke udf├Şres C:\Windows\winsxs\msil_system.data.sqlxml_b77a5c561934e089_6.1.7601.23290_none_ef0f51667b42e43e\System.Data.SqlXml.dll ┬╗ SMARTASSEMBLY ┬╗ deobfuscated.exe - handlingen kan ikke udf├Şres Bootsektor for disk D: - fejl ved ├ąbning af D:\ - fejl ved ├ąbning af E:\Video Games\Steam 2\steamapps\downloading\440\_CommonRedist\DirectX\Jun2010\JUN2008_d3dx9_38_x64.cab ┬╗ CAB ┬╗ d3dx9_38.dll - arkivet er beskadiget - filen kunne ikke pakkes ud. E:\Video Games\Steam 2\steamapps\downloading\440\_CommonRedist\DirectX\Jun2010\JUN2008_d3dx9_38_x64.cab ┬╗ CAB ┬╗ d3dx9_38_x64.cat - arkivet er beskadiget - filen kunne ikke pakkes ud. E:\Video Games\Steam 2\steamapps\downloading\440\_CommonRedist\DirectX\Jun2010\JUN2008_d3dx9_38_x64.cab ┬╗ CAB ┬╗ d3dx9_38_x64.inf - arkivet er beskadiget - filen kunne ikke pakkes ud. E:\Video Games\Steam 2\steamapps\downloading\440\_CommonRedist\DirectX\Jun2010\JUN2008_d3dx9_38_x64.cab ┬╗ CAB ┬╗ d3dx9_38_x64_xp.inf - arkivet er beskadiget - filen kunne ikke pakkes ud. E:\Video Games\Steam 2\steamapps\downloading\440\_CommonRedist\DirectX\Jun2010\JUN2008_d3dx9_38_x64.cab ┬╗ CAB ┬╗ Jun2008_d3dx9_38_x64.inf - arkivet er beskadiget - filen kunne ikke pakkes ud. E:\Video Games\Steam 2\steamapps\downloading\440\_CommonRedist\DirectX\Jun2010\JUN2008_d3dx9_38_x64.cab ┬╗ CAB ┬╗ infinst.exe - arkivet er beskadiget - filen kunne ikke pakkes ud. E:\Video Games\Steam 2\steamapps\downloading\440\_CommonRedist\DirectX\Jun2010\Nov2008_d3dx9_40_x64.cab ┬╗ CAB ┬╗ d3dx9_40.dll - arkivet er beskadiget - filen kunne ikke pakkes ud. E:\Video Games\Steam 2\steamapps\downloading\440\_CommonRedist\DirectX\Jun2010\Nov2008_d3dx9_40_x64.cab ┬╗ CAB ┬╗ d3dx9_40_x64.cat - arkivet er beskadiget - filen kunne ikke pakkes ud. E:\Video Games\Steam 2\steamapps\downloading\440\_CommonRedist\DirectX\Jun2010\Nov2008_d3dx9_40_x64.cab ┬╗ CAB ┬╗ d3dx9_40_x64.inf - arkivet er beskadiget - filen kunne ikke pakkes ud. E:\Video Games\Steam 2\steamapps\downloading\440\_CommonRedist\DirectX\Jun2010\Nov2008_d3dx9_40_x64.cab ┬╗ CAB ┬╗ d3dx9_40_x64_xp.inf - arkivet er beskadiget - filen kunne ikke pakkes ud. E:\Video Games\Steam 2\steamapps\downloading\440\_CommonRedist\DirectX\Jun2010\Nov2008_d3dx9_40_x64.cab ┬╗ CAB ┬╗ Nov2008_d3dx9_40_x64.inf - arkivet er beskadiget - filen kunne ikke pakkes ud. E:\Video Games\Steam 2\steamapps\downloading\440\_CommonRedist\DirectX\Jun2010\Nov2008_d3dx9_40_x64.cab ┬╗ CAB ┬╗ infinst.exe - arkivet er beskadiget - filen kunne ikke pakkes ud. Bootsektor for disk G: - fejl ved ├ąbning af G:\ - fejl ved ├ąbning af "Arkivet er beskadiget - filen kunne ikke pakkes ud" can be translated into "The archive is damaged - the file could not be unpacked". I did the following and the system found no errors. Afterwards I scanned with Eset and got the same results as above. This is where things get rather frustrating. I booted into safe-mode and ran system restore as admin as you suggested. Unfortunately I had to try 4 different restore points before Windows stopped giving me the following error message: The text under details basically translates into "Unpacking the file (C:\) from the restore point was not successful. An unspecific error occurred doing system restore." It took until the 4th restore point for the process to be completed successfully. Again, all of this was performed via safe-mode. After the successful system restore point I ran a scan with Eset, but unfortunately the odd entries are still present in the scan log: Log Scanningslog Version af virussignaturdatabase: 15175 (20170330) Dato: 30-03-2017 Klokkesl├Žt: 19:32:20 Scannede diske, mapper og filer: Hukommelse (RAM);Bootsektor;C:\Bootsektor;C:\;D:\Bootsektor;D:\;E:\Bootsektor;E:\;G:\Bootsektor;G:\ MBR-sektor for 2. fysisk disk - fejl ved ├ąbning af [4] C:\hiberfil.sys - fejl ved ├ąbning af [4] C:\pagefile.sys - fejl ved ├ąbning af [4] C:\System Volume Information\{069313ea-095d-11e7-8a6f-d8cb8ac74018}{3808876b-c176-4e48-b7ae-04046e6cc752} - fejl ved ├ąbning af [4] C:\System Volume Information\{06931447-095d-11e7-8a6f-d8cb8ac74018}{3808876b-c176-4e48-b7ae-04046e6cc752} - fejl ved ├ąbning af [4] C:\System Volume Information\{3808876b-c176-4e48-b7ae-04046e6cc752} - fejl ved ├ąbning af [4] C:\System Volume Information\{4cf8617d-13a4-11e7-a2de-d8cb8ac74018}{3808876b-c176-4e48-b7ae-04046e6cc752} - fejl ved ├ąbning af [4] C:\System Volume Information\{5bffe9fc-fdcd-11e6-a182-d8cb8ac74018}{3808876b-c176-4e48-b7ae-04046e6cc752} - fejl ved ├ąbning af [4] C:\System Volume Information\{7f9dd97d-0e3b-11e7-aff8-d8cb8ac74018}{3808876b-c176-4e48-b7ae-04046e6cc752} - fejl ved ├ąbning af [4] C:\System Volume Information\{b67727fd-10a5-11e7-a9b9-d8cb8ac74018}{3808876b-c176-4e48-b7ae-04046e6cc752} - fejl ved ├ąbning af [4] C:\System Volume Information\{b78b23fc-0347-11e7-b497-d8cb8ac74018}{3808876b-c176-4e48-b7ae-04046e6cc752} - fejl ved ├ąbning af [4] C:\Windows\assembly\GAC_MSIL\System.Data.SqlXml\2.0.0.0__b77a5c561934e089\System.Data.SqlXml.dll ┬╗ SMARTASSEMBLY ┬╗ deobfuscated.exe - handlingen kan ikke udf├Şres C:\Windows\Installer\25e0a.msi ┬╗ MSI ┬╗ media1.cab ┬╗ CAB - fejl ved l├Žsning af arkiv C:\Windows\Microsoft.NET\Framework\v2.0.50727\System.Data.SqlXml.dll ┬╗ SMARTASSEMBLY ┬╗ deobfuscated.exe - handlingen kan ikke udf├Şres C:\Windows\Microsoft.NET\Framework64\v2.0.50727\System.Data.SqlXml.dll ┬╗ SMARTASSEMBLY ┬╗ deobfuscated.exe - handlingen kan ikke udf├Şres C:\Windows\winsxs\amd64_netfx-system.data.sqlxml_b03f5f7f11d50a3a_6.1.7601.17514_none_141b1b1223b1ada7\System.Data.SqlXml.dll ┬╗ SMARTASSEMBLY ┬╗ deobfuscated.exe - handlingen kan ikke udf├Şres C:\Windows\winsxs\amd64_netfx-system.data.sqlxml_b03f5f7f11d50a3a_6.1.7601.18523_none_141c340a23b0aa84\System.Data.SqlXml.dll ┬╗ SMARTASSEMBLY ┬╗ deobfuscated.exe - handlingen kan ikke udf├Şres C:\Windows\winsxs\amd64_netfx-system.data.sqlxml_b03f5f7f11d50a3a_6.1.7601.18529_none_141bab5a23b1444a\System.Data.SqlXml.dll ┬╗ SMARTASSEMBLY ┬╗ deobfuscated.exe - handlingen kan ikke udf├Şres C:\Windows\winsxs\amd64_netfx-system.data.sqlxml_b03f5f7f11d50a3a_6.1.7601.19091_none_1423663a23aa2435\System.Data.SqlXml.dll ┬╗ SMARTASSEMBLY ┬╗ deobfuscated.exe - handlingen kan ikke udf├Şres C:\Windows\winsxs\amd64_netfx-system.data.sqlxml_b03f5f7f11d50a3a_6.1.7601.22733_none_fd4f8d703d572432\System.Data.SqlXml.dll ┬╗ SMARTASSEMBLY ┬╗ deobfuscated.exe - handlingen kan ikke udf├Şres C:\Windows\winsxs\amd64_netfx-system.data.sqlxml_b03f5f7f11d50a3a_6.1.7601.22740_none_fd50d2123d55f0a6\System.Data.SqlXml.dll ┬╗ SMARTASSEMBLY ┬╗ deobfuscated.exe - handlingen kan ikke udf├Şres C:\Windows\winsxs\amd64_netfx-system.data.sqlxml_b03f5f7f11d50a3a_6.1.7601.23290_none_fd55d61e3d516aeb\System.Data.SqlXml.dll ┬╗ SMARTASSEMBLY ┬╗ deobfuscated.exe - handlingen kan ikke udf├Şres C:\Windows\winsxs\msil_system.data.sqlxml_b77a5c561934e089_6.1.7601.17514_none_05d4965a61a326fa\System.Data.SqlXml.dll ┬╗ SMARTASSEMBLY ┬╗ deobfuscated.exe - handlingen kan ikke udf├Şres C:\Windows\winsxs\msil_system.data.sqlxml_b77a5c561934e089_6.1.7601.18523_none_05d5af5261a223d7\System.Data.SqlXml.dll ┬╗ SMARTASSEMBLY ┬╗ deobfuscated.exe - handlingen kan ikke udf├Şres C:\Windows\winsxs\msil_system.data.sqlxml_b77a5c561934e089_6.1.7601.18529_none_05d526a261a2bd9d\System.Data.SqlXml.dll ┬╗ SMARTASSEMBLY ┬╗ deobfuscated.exe - handlingen kan ikke udf├Şres C:\Windows\winsxs\msil_system.data.sqlxml_b77a5c561934e089_6.1.7601.19091_none_05dce182619b9d88\System.Data.SqlXml.dll ┬╗ SMARTASSEMBLY ┬╗ deobfuscated.exe - handlingen kan ikke udf├Şres C:\Windows\winsxs\msil_system.data.sqlxml_b77a5c561934e089_6.1.7601.22733_none_ef0908b87b489d85\System.Data.SqlXml.dll ┬╗ SMARTASSEMBLY ┬╗ deobfuscated.exe - handlingen kan ikke udf├Şres C:\Windows\winsxs\msil_system.data.sqlxml_b77a5c561934e089_6.1.7601.22740_none_ef0a4d5a7b4769f9\System.Data.SqlXml.dll ┬╗ SMARTASSEMBLY ┬╗ deobfuscated.exe - handlingen kan ikke udf├Şres C:\Windows\winsxs\msil_system.data.sqlxml_b77a5c561934e089_6.1.7601.23290_none_ef0f51667b42e43e\System.Data.SqlXml.dll ┬╗ SMARTASSEMBLY ┬╗ deobfuscated.exe - handlingen kan ikke udf├Şres Bootsektor for disk D: - fejl ved ├ąbning af [4] D:\ - fejl ved ├ąbning af [4] E:\Video Games\Steam 2\steamapps\downloading\440\_CommonRedist\DirectX\Jun2010\JUN2008_d3dx9_38_x64.cab ┬╗ CAB ┬╗ d3dx9_38.dll - arkivet er beskadiget - filen kunne ikke pakkes ud. E:\Video Games\Steam 2\steamapps\downloading\440\_CommonRedist\DirectX\Jun2010\JUN2008_d3dx9_38_x64.cab ┬╗ CAB ┬╗ d3dx9_38_x64.cat - arkivet er beskadiget - filen kunne ikke pakkes ud. E:\Video Games\Steam 2\steamapps\downloading\440\_CommonRedist\DirectX\Jun2010\JUN2008_d3dx9_38_x64.cab ┬╗ CAB ┬╗ d3dx9_38_x64.inf - arkivet er beskadiget - filen kunne ikke pakkes ud. E:\Video Games\Steam 2\steamapps\downloading\440\_CommonRedist\DirectX\Jun2010\JUN2008_d3dx9_38_x64.cab ┬╗ CAB ┬╗ d3dx9_38_x64_xp.inf - arkivet er beskadiget - filen kunne ikke pakkes ud. E:\Video Games\Steam 2\steamapps\downloading\440\_CommonRedist\DirectX\Jun2010\JUN2008_d3dx9_38_x64.cab ┬╗ CAB ┬╗ Jun2008_d3dx9_38_x64.inf - arkivet er beskadiget - filen kunne ikke pakkes ud. E:\Video Games\Steam 2\steamapps\downloading\440\_CommonRedist\DirectX\Jun2010\JUN2008_d3dx9_38_x64.cab ┬╗ CAB ┬╗ infinst.exe - arkivet er beskadiget - filen kunne ikke pakkes ud. E:\Video Games\Steam 2\steamapps\downloading\440\_CommonRedist\DirectX\Jun2010\Nov2008_d3dx9_40_x64.cab ┬╗ CAB ┬╗ d3dx9_40.dll - arkivet er beskadiget - filen kunne ikke pakkes ud. E:\Video Games\Steam 2\steamapps\downloading\440\_CommonRedist\DirectX\Jun2010\Nov2008_d3dx9_40_x64.cab ┬╗ CAB ┬╗ d3dx9_40_x64.cat - arkivet er beskadiget - filen kunne ikke pakkes ud. E:\Video Games\Steam 2\steamapps\downloading\440\_CommonRedist\DirectX\Jun2010\Nov2008_d3dx9_40_x64.cab ┬╗ CAB ┬╗ d3dx9_40_x64.inf - arkivet er beskadiget - filen kunne ikke pakkes ud. E:\Video Games\Steam 2\steamapps\downloading\440\_CommonRedist\DirectX\Jun2010\Nov2008_d3dx9_40_x64.cab ┬╗ CAB ┬╗ d3dx9_40_x64_xp.inf - arkivet er beskadiget - filen kunne ikke pakkes ud. E:\Video Games\Steam 2\steamapps\downloading\440\_CommonRedist\DirectX\Jun2010\Nov2008_d3dx9_40_x64.cab ┬╗ CAB ┬╗ Nov2008_d3dx9_40_x64.inf - arkivet er beskadiget - filen kunne ikke pakkes ud. E:\Video Games\Steam 2\steamapps\downloading\440\_CommonRedist\DirectX\Jun2010\Nov2008_d3dx9_40_x64.cab ┬╗ CAB ┬╗ infinst.exe - arkivet er beskadiget - filen kunne ikke pakkes ud. Bootsektor for disk G: - fejl ved ├ąbning af [4] G:\ - fejl ved ├ąbning af [4] Antal scannede objekter: 778124 Antal trusler fundet: 0 Tidspunkt for fuldf├Şrelse: 19:54:06 Samlet scanningstid: 1306 sek. (00:21:46) ŃÇÇ Bem├Žrkninger: [4] Objekt kan ikke ├ąbnes. Det er muligvis i brug af et andet program eller operativsystem. In addition to all of this, for some reason, Eset Nod32 Antivirus 9 is now giving me a warning that the program isn't updated The Windows security centre is claiming the same, but the Virus signature database version appears to be the latest? *EDIT* So it looks like the system restoring affected the clock as it suddenly was an hour ahead. We've very recently had to adjust for daylight saving time in my region. The time on my system is now correct once more, but NOD32 still claims that it doesn't have the latest updates . So all of this is rather mystifying and frustrating. At this point I'm very tempted to get this machine professionally formatted by my local PC guy as that would surely be the end of it? Out of curiosity, should I attempt and update Eset Nod32 Antivirus 9 to the latest version of Nod32 Antivirus 10 and see if it still picks up on all of this? *EDIT* I decided to take a look at my profiles for scanning with NOD32 and I now see that the C:\Windows\assembly\GAC_MSIL directory is visible to NOD32 as shown below I still cannot get access to this myself as mentioned earlier, but apparently NOD32 can see it and therefor scan it.
×
×
  • Create New...