Windows 7 Event ID 35 Side by Side errors

Discussion in 'ESET Smart Security' started by thezzapper, Oct 25, 2009.

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

    thezzapper Registered Member

    Joined:
    Apr 8, 2007
    Posts:
    27
    Location:
    New York City
    I recently did a clean install to Windows 7 Home Premium. All seems well with ESS 4.0.467.0 except for the following errors in the event log when booting up:

    Activation context generation failed for "C:\Program Files\ESET\ESET Smart Security\MFC80U.DLL".Error in manifest or policy file "C:\Program Files\ESET\ESET Smart Security\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.

    Any ideas as to what the problem could be? Whenever i boot up, I receive this error about a dozen tomes per boot.

    Thanks in advance.
     
  2. cssoz

    cssoz Registered Member

    Joined:
    Apr 11, 2009
    Posts:
    79
    - try uninstalling NOD32 completely!
    - RESTART!
    - download another set-up file off the internet http://www.eset.com/download/index.php
    - install NOD32 EES
    - update (if no error or problems during installation)
    - restart (if no error or problems during installation )
     
  3. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,330
    Uninstalling ESS and downloading / installing the latest version from the web should resolve this small problem.
     
  4. ccomputertek

    ccomputertek Registered Member

    Joined:
    Jul 27, 2009
    Posts:
    371
    No, this has been talked about allready.An update from microsoft will fix this, but it doesn't hurt NOD32 if you don't, but you'll get these SxS errors unless you do.

    Microsoft Visual C++ 2008 Redistributable Package

    OR

    Microsoft Visual C++ 2008 SP1 Redistributable Package


    Ok maybe not, I am getting the error and I have the latest Microsoft Visual C++ 2008 SP1 Redistributable Package, so mabe you need the earlier Microsoft Visual C++ 2005 Redistributable Package

    Seems like in this case, Eset needs to update something, instead of microsoft, if the older Microsoft Visual C++ 2005 Redistributable is necessary.
     
    Last edited: Oct 26, 2009
  5. thezzapper

    thezzapper Registered Member

    Joined:
    Apr 8, 2007
    Posts:
    27
    Location:
    New York City
    Marcos, I am still experiencing the same problem.
     
  6. ccomputertek

    ccomputertek Registered Member

    Joined:
    Jul 27, 2009
    Posts:
    371
    No, this has been talked about allready.An update from microsoft will fix this, but it doesn't hurt NOD32 if you don't, but you'll get these SxS errors unless you do.

    Microsoft Visual C++ 2008 Redistributable Package

    OR

    Microsoft Visual C++ 2008 SP1 Redistributable Package


    Ok maybe not, I am getting the error and I have the latest Microsoft Visual C++ 2008 SP1 Redistributable Package, so mabe you need the earlier Microsoft Visual C++ 2005 Redistributable Package

    Seems like in this case, Eset needs to update something, instead of microsoft, if the older Microsoft Visual C++ 2005 Redistributable is necessary.
     
  7. Gelangweilt

    Gelangweilt Registered Member

    Joined:
    Oct 26, 2009
    Posts:
    15
    i have the same error.
    just tried fresh download and reinstall:
    problem still there.
    o_O
     
  8. ccomputertek

    ccomputertek Registered Member

    Joined:
    Jul 27, 2009
    Posts:
    371
  9. Gelangweilt

    Gelangweilt Registered Member

    Joined:
    Oct 26, 2009
    Posts:
    15
    still there
    i have the 2005 and 2008 package installed
     
  10. ccomputertek

    ccomputertek Registered Member

    Joined:
    Jul 27, 2009
    Posts:
    371
    Uninstall the 2008 package and put the 2005 package on only, not 2008 on top of the 2005 package.
     
  11. Gelangweilt

    Gelangweilt Registered Member

    Joined:
    Oct 26, 2009
    Posts:
    15
  12. ccomputertek

    ccomputertek Registered Member

    Joined:
    Jul 27, 2009
    Posts:
    371
    Well, yeah...... if your using a 64 bit OS then you need the 64 bit version, I did not see anywhere you posted you were on 64bit windows, prior to this.
     
  13. Gelangweilt

    Gelangweilt Registered Member

    Joined:
    Oct 26, 2009
    Posts:
    15
  14. HSChronic

    HSChronic Registered Member

    Joined:
    Feb 22, 2007
    Posts:
    10
    well this is a good fix for one single box... too bad it is happening on all my boxes running Win7 or 2008 R2. I don't feel like scripting a package into SCCM just so I can apply something that I shouldn't need on my boxes. So deploying this to 30+ boxes is only going to cause more SxS needs, which my SxS folder is big enough thanks.
     
  15. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,330
    The current installers on the web have a correct manifest embedded so this warning shouldn't appear in logs unless there's a problem with system Side by Side libraries or their registration in the OS (an issue not related to ESET installers).
     
  16. Gelangweilt

    Gelangweilt Registered Member

    Joined:
    Oct 26, 2009
    Posts:
    15
    i made a fresh install of win 7 ultimate.
    how could be anything wrong with that?
    EAV was the 2nd thing to be installed after drivers.
    so there muste be somethign missing in the ESET package.
     
  17. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,330
    When did you actually download the ESET installer? Are you installing the latest build 4.0.467?
     
  18. ccomputertek

    ccomputertek Registered Member

    Joined:
    Jul 27, 2009
    Posts:
    371
    Marcos, what is the digital signature date stamp on the files that supposidly have this fixed ? v3 and v4 both I presume ?

    Tuesday, September 01, 2009 5:01:24 AM is the latest version of 3.0 that I see.
     
    Last edited: Nov 1, 2009
  19. Gelangweilt

    Gelangweilt Registered Member

    Joined:
    Oct 26, 2009
    Posts:
    15
    i have 4.0.467 yes.
    i have one verison downloaded end of september.
    but i also downloaded another time last week when i installed Win 7
     
  20. c0ncept

    c0ncept Registered Member

    Joined:
    Oct 28, 2009
    Posts:
    2
    Same as me here, Fresh full install of Windows7 32bit, ESET V4 4.0.467, downloaded the installer from the website as instructed. Those errors show in the logs. Any luck on this subject or what steps I should take?
     
  21. Gelangweilt

    Gelangweilt Registered Member

    Joined:
    Oct 26, 2009
    Posts:
    15
    download the 2005 / 2008 C++ redistributable installers.
    lots of links for them in the thread.
    this should do the trick for you.
     
  22. pbmcmlxxi

    pbmcmlxxi Registered Member

    Joined:
    Oct 28, 2006
    Posts:
    131
    Location:
    Hants, UK
    I can confirm that the above has worked for me on *64 Windows 7..
     
  23. thezzapper

    thezzapper Registered Member

    Joined:
    Apr 8, 2007
    Posts:
    27
    Location:
    New York City
    I am still getting the side by side errors on my 32 bit windows 7 home premium. The Microsoft page for installing the 2008 C++ Redistribution Package does not say it is compatible with Windows 7, so I am reluctant to install it.
     
  24. HSChronic

    HSChronic Registered Member

    Joined:
    Feb 22, 2007
    Posts:
    10
    the C++ 2008 Redistributable installs with App-V 4.6 which is certified to work on Windows 7, so if it didn't work MS wouldn't bundle it with a client certified to work on 7.
     
  25. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,330
    Check the MD5 of microsoft.vc80.mfcloc.manifest on the ESET installation folder. If it's equal to 526c8811d11c65f7ebca8d5f38421188, the problem is not caused by ESET but there's a problem with system dlls or the way they are registered in the OS.
     
Thread Status:
Not open for further replies.