Shoutbox

Ok, will try it, but how do i back up the file?

am sorry for asking too much mate

quote:

---

Originally posted by knuckle555
Ok, will try it, but how do i back up the file?

am sorry for asking too much mate

---

Just copy the file in your MSN folder and then paste it to your desktop.

thanks,

right, i've tried to change from .1 to .4148 but somehow, it says that the original file is packed, sth like that

((

i can't save it from .1 to .4148

..........

If you're not an administrator on your computer, then none of the solutions presented will work.

Run everything as an administrator and it should work.

still not working mate.

what happens essentially now is that the program is deleted by windows after an attempt to run the program is made

HI anyone?
i have trouble to open my msn.. and it has an event id of 78..
anyone knows how to solve this ?

Hi BandAid3030,

i would really need your help.
i have the same problem with my messenger, i tryed everything you mentioned in the thread above but nothing seams to be working !!!! do you have any other solutions?

Exact Error 78 in the event log "\Activation context generation failed for "C:\Program Files\Windows Live\Messenger\msnmsgr.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\Windows\WinSxS\manifests\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4148_none_5090ab56bcba71c2.manifest. Component 2: C:\Windows\WinSxS\manifests\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.1_none_e163563597edeada.manifest."

Steps Taken are

1.) Uninstall ALL of your Microsoft Visual Basic C++ Redistributables.
2.) Uninstall the entire Windows Live Essentials Package, then Restart.
3.) Reinstall Windows Live Messenger (Try running it to see if it works).
4.) Reinstall Microsoft Visual Basic C++ Redistributable 2008 and 2008 (SP1)
As an admin, but did not work

then i tried the following
The only other solution that I can suggest is for you to try and edit your manifest with Resource Tuner:

1.) A simple Google search will yield Resource Tuner, and, after installing, the msnmsgr.exe file is opened with Resource Tuner.
2.) The manifest option is expanded in the left pane to show the manifest for msnmsgr.exe as "1".
3.) Click on this manifest and then press "Ctrl+Shift+E" to open the manifest editor.
4.) At this point, all I did was isolate the code in the manifest that pointed to version 9.0.30729.1 and changed it to 9.0.30729.4148.

ie:
<dependentAssembly>
            <assemblyIdentity
                type="win32"
                name="Microsoft.VC90.CRT"
                version="9.0.30729.4148"
                processorArchitecture="x86"
                publicKeyToken="1fc8b3b9a1e18e3b"
            />
        </dependentAssembly>
also as an admin, but the file was saving as "Bak" and the original file remains, not sure what that means and if it affects anything.

please let me know if you or anyone els has any other solution to the problem, thanks

quote:

---

Originally posted by BandAid3030
The only other solution that I can suggest is for you to try and edit your manifest with Resource Tuner:

1.) A simple Google search will yield Resource Tuner, and, after installing, the msnmsgr.exe file is opened with Resource Tuner.
2.) The manifest option is expanded in the left pane to show the manifest for msnmsgr.exe as "1".
3.) Click on this manifest and then press "Ctrl+Shift+E" to open the manifest editor.
4.) At this point, all I did was isolate the code in the manifest that pointed to version 9.0.30729.1 and changed it to 9.0.30729.4148.

ie:
<dependentAssembly>
            <assemblyIdentity
                type="win32"
                name="Microsoft.VC90.CRT"
                version="9.0.30729.4148"
                processorArchitecture="x86"
                publicKeyToken="1fc8b3b9a1e18e3b"
            />
        </dependentAssembly>


BE SURE TO BACK UP YOUR msnmsgr.exe FILE BEFORE EDITING!

---

Hi I tried this and still no luck....any other back up plan?

I've not had any luck getting this fixed either.  I've tried every suggestion, etc.  Still nothing.