PDA

View Full Version : Windows 7 Event ID 35 Side by Side errors


thezzapper
October 25th, 2009, 06:31 PM
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.

cssoz
October 25th, 2009, 10:59 PM
-{ Quote: "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." }-

- 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 )

Marcos
October 26th, 2009, 02:28 AM
Uninstalling ESS and downloading / installing the latest version from the web should resolve this small problem.

ccomputertek
October 26th, 2009, 06:46 AM
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.

thezzapper
October 28th, 2009, 06:55 PM
-{ Quote: "Uninstalling ESS and downloading / installing the latest version from the web should resolve this small problem." }-
Marcos, I am still experiencing the same problem.

ccomputertek
October 28th, 2009, 07:02 PM
-{ Quote: "Marcos, I am still experiencing the same problem." }-

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.

Gelangweilt
October 28th, 2009, 07:30 PM
i have the same error.
just tried fresh download and reinstall:
problem still there.
???

ccomputertek
October 28th, 2009, 07:32 PM
Download and install this:

http://www.microsoft.com/downloads/details.aspx?familyID=32bc1bee-a3f9-4c13-9c99-220b62a191ee&displaylang=en

Gelangweilt
October 29th, 2009, 03:11 AM
still there
i have the 2005 and 2008 package installed

ccomputertek
October 29th, 2009, 10:00 AM
Uninstall the 2008 package and put the 2005 package on only, not 2008 on top of the 2005 package.

Gelangweilt
October 29th, 2009, 10:45 AM
Installing the 64bit C++ 2005 redist kit solved the problem.
(running Windows 7 64bit, but didnt know there is also a 64bit version of that package)

Found it here:
http://www.microsoft.com/downloads/details.aspx?displaylang=de&FamilyID=90548130-4468-4bbc-9673-d6acabd5d13b

ccomputertek
October 29th, 2009, 11:20 AM
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.

Gelangweilt
October 29th, 2009, 12:21 PM
http://www.wilderssecurity.com/showthread.php?t=256864
;)
here i did ;)
nvm though. it is solved. thanks.

i dodnt know there were also 64bit libraries for this.....

HSChronic
November 1st, 2009, 08:22 AM
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.

Marcos
November 1st, 2009, 08:39 AM
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).

Gelangweilt
November 1st, 2009, 09:24 AM
-{ Quote: "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)." }-

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.

Marcos
November 1st, 2009, 10:22 AM
When did you actually download the ESET installer? Are you installing the latest build 4.0.467?

ccomputertek
November 1st, 2009, 11:00 AM
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.

Gelangweilt
November 1st, 2009, 12:59 PM
-{ Quote: "When did you actually download the ESET installer? Are you installing the latest build 4.0.467?" }-

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

c0ncept
November 4th, 2009, 10:23 PM
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?

Gelangweilt
November 6th, 2009, 07:16 AM
download the 2005 / 2008 C++ redistributable installers.
lots of links for them in the thread.
this should do the trick for you.

pjb
November 6th, 2009, 09:39 AM
-{ Quote: "download the 2005 / 2008 C++ redistributable installers.
lots of links for them in the thread.
this should do the trick for you." }-

I can confirm that the above has worked for me on *64 Windows 7..

thezzapper
November 12th, 2009, 11:40 AM
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.

HSChronic
November 12th, 2009, 12:33 PM
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.

Marcos
November 12th, 2009, 12:35 PM
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.

thezzapper
November 12th, 2009, 01:01 PM
-{ Quote: "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." }-

Ok. I have installed the c++ for 2008 & installed the necessary update through windows update. I am still receiving the same error.

Marcus, can you please explain further how to "Check the MD5 of microsoft.vc80.mfcloc.manifest". Also, if it is a problem with system dlls, is it fixable?

Thank you.

stcraig
November 18th, 2009, 08:08 PM
-{ Quote: "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." }-

I have to disagree with Marcos. The MD5 hash on two different x64 computers I have is different than his post - 560CB69547098499E839061ED7B6CDBE. Both have v 4.0.467 downloaded from the ESET website within the last few days (at separate times from different computers) and Win7 Home Premium - clean install.

On both it was necessary to download and install the VC++ 2005 Redistributable.

I agree with Gelangweilt ... there must be something missing from the ESET install package.