Event Viewer Errors from NOD32 4.0.467

Discussion in 'ESET NOD32 Antivirus' started by nrms, Nov 20, 2009.

Thread Status:
Not open for further replies.
  1. nrms

    nrms Registered Member

    Joined:
    Jun 22, 2008
    Posts:
    72
    I get 7 or 8 of these "SideBySide" Event ID 35 errors in my Win7 Windows Event Log everytime I restart Windows. WHat is causing it & how do I fix it?

    Activation context generation failed for "C:\Program Files\ESET\ESET NOD32 Antivirus\MFC80U.DLL".Error in manifest or policy file "C:\Program Files\ESET\ESET NOD32 Antivirus\Microsoft.VC80.MFCLOC.MANIFEST" on line 5. Component identity found in manifest does not match the identity of the component requested. Reference is Microsoft.VC80.MFCLOC,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50608.0". Definition is Microsoft.VC80.MFCLOC,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.4053". Please use sxstrace.exe for detailed diagnosis.

    Thanks
    NigelS
     
  2. ccomputertek

    ccomputertek Registered Member

    Joined:
    Jul 27, 2009
    Posts:
    371
    This has been talked about a 1000 times here already.you need Microsoft Visual C++ 2005 Redistributable.
     
  3. nrms

    nrms Registered Member

    Joined:
    Jun 22, 2008
    Posts:
    72
    Thanks I'll do a search (as I should have done before posting!)

    N
     
  4. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,376
    I assume you downloaded 4.0.467 a couple of weeks ago as the current installers have a correct manifest in question embedded.
     
  5. ccomputertek

    ccomputertek Registered Member

    Joined:
    Jul 27, 2009
    Posts:
    371
    You guys @ Eset really need to start catching these idiosyncrasies before the software goes public.Makes us all look like beta testers helping you get it right and does not look good to bystanders looking for an antivirus program.

    Lets try to catch these things before the software even gets let out the door.... ok ? I know it's not possible to catch everything, but try a little harder and be more aggressive.Even big names like symantec are constantly pushing out software / program updates for fixes for little issues that come up regularly, so it's inevitable to happen.But simple things like this should have been corrected before the software leaves your company to get on customers computers.
     
  6. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,376
    I'm sorry but simple things like this would no one expect and no one would regularly check event logs during the testing if there are no apparent problems with the program. What's more, this is not a critical issue whatsoever and has absolutely no impact on system's functionality.
     
  7. nrms

    nrms Registered Member

    Joined:
    Jun 22, 2008
    Posts:
    72
    No I downloaded a fresh copy from your dl site yesterday.

    NigelS
     
  8. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,376
    Could you please post here the exact link from which you downloaded the file?
     
  9. nrms

    nrms Registered Member

    Joined:
    Jun 22, 2008
    Posts:
    72
  10. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,376
    The manifest in the installer you downloaded is correct. Please create a screenshot like this from SysInspector showing details about egui.exe and post it here:
     

    Attached Files:

  11. siljaline

    siljaline Former Poster

    Joined:
    Jun 29, 2003
    Posts:
    6,619
  12. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,376
    If the error appears after uninstalling EAV and downloading & installing the latest 4.0.467 build from the download page, post here the screenshot from your ESI log mentioned above which will shed more light.
     
  13. siljaline

    siljaline Former Poster

    Joined:
    Jun 29, 2003
    Posts:
    6,619
    Not a problem, is there a Sol # for generating SysInspector Log, Marcos ?
    As I'm not quite familiar.

    Regards,
     
  14. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,376
    If you run SysInspector, a log is created automatically. Alternatively, you can create a SysInspector snapshot in Tools -> SysInspector -> Create. In the Running processes section
    - look up egui.exe in the Running processes section and select it
    - in the right-hand pane look up mfc80*.dll and select it
    - right-click in the lower pane with file details and select Copy all to clipboard
    - paste here the information from clipboard
     
  15. nrms

    nrms Registered Member

    Joined:
    Jun 22, 2008
    Posts:
    72
    "Module" = "c:\program files\eset\eset nod32 antivirus\mfc80u.dll" ( 5: Unknown ) ; MFCDLL Shared Library - Retail Version ; Microsoft Corporation ;
    "Internal Name" = "MFC80U.DLL"
    "Product Name" = "Microsoft® Visual Studio® 2005"
    "File Version" = "8.00.50727.4053"
    "Company Name" = "Microsoft Corporation"
    "File Description" = "MFCDLL Shared Library - Retail Version"
    "File Size" = "1093120"
    "SHA1" = "684EE9F018FBB0BBF6FFA590F3782BA49D5D096C"
    "Creation Time" = "2009/07/11 21:46"
    "Last Write Time" = "2009/07/11 21:46"
    "Linked to" = "Running Processes -> sysinspector.exe -> c:\program files\eset\eset nod32 antivirus\mfc80u.dll"
    "Linked to" = "Running Processes -> egui.exe -> c:\program files\eset\eset nod32 antivirus\mfc80u.dll"


    AND FURTHER DOWN THE SAME PANEL:

    "Module" = "c:\windows\winsxs\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.42_none_0e9c2a8d74fd3ce6\mfc80enu.dll" ( 5: Unknown ) ; MFC Language Specific Resources ; Microsoft Corporation ;
    "Internal Name" = "MFC80ENU.DLL"
    "Product Name" = "Microsoft® Visual Studio® 2005"
    "File Version" = "8.00.50727.42"
    "Company Name" = "Microsoft Corporation"
    "File Description" = "MFC Language Specific Resources"
    "File Size" = "57344"
    "SHA1" = "1449AA9080FA8A61F2232580DCDB63F486731DB7"
    "Creation Time" = "2009/11/22 11:26"
    "Last Write Time" = "2009/11/22 11:26"
    "Linked to" = "Running Processes -> sysinspector.exe -> c:\windows\winsxs\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.42_none_0e9c2a8d74fd3ce6\mfc80enu.dll"
    "Linked to" = "Running Processes -> egui.exe -> c:\windows\winsxs\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.42_none_0e9c2a8d74fd3ce6\mfc80enu.dll"
     
  16. siljaline

    siljaline Former Poster

    Joined:
    Jun 29, 2003
    Posts:
    6,619
    Noted, though I did not accomplish this quite the same way, attached are my findings, as I mentioned earlier, forever able to see in event viewer
    Is egui.exe erroneously locking on to an MS DLL file?

    Thank you for your time in this as I think myself and others would like this clarified.
     

    Attached Files:

    Last edited: Nov 22, 2009
Thread Status:
Not open for further replies.