Jump to content
wevsspot

Microsoft Security Essentials Causing Side by Side Errors

Recommended Posts

If the file is saved in the wrong format MSE will throw an error. Seems to me the last time I did it I hit the save button without changing the default selection. So that would have been ANSI.

Share this post


Link to post
Share on other sites

Hi, Firstly thanks for your fix. Ive attempted it but now get a slightly different error?

 

Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 28. Invalid Xml syntax.

 

Line 28 (goimg off notepad++) is just computer code?

 

My file currently has this as the xml style section. for what its worth, the <?xml version="1.0" encoding="UTF-8" standalone="yes"?> section is currently in its original place on the end of an existing code line. worth bumping it down?

 

many thanks for any help

 

 

<!-- Copyright © Microsoft Corporation -->

<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">

<assemblyIdentity

version="5.1.0.0"

processorArchitecture="amd64"

name="Microsoft.MSE.MSESysprep"

type="win32"

/>

<description>Microsoft Security Client Sysprep module</description>

<compatibility xmlns="urn:schemas-microsoft-com:compatibility.v1">

<application>

<!--Windows 7-->

<supportedOS Id="{35138b9a-5d96-4fbd-8e2d-a2440225f93a}"/>

</application>

</compatibility>

<dependency>

</dependency>

<trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">

<security>

<requestedPrivileges>

<requestedExecutionLevel

level="asInvoker"

uiAccess="false"

/>

</requestedPrivileges>

</security>

</trustInfo>

</assembly>

Edited by Bossworld

Share this post


Link to post
Share on other sites

Ok, one more time. This is a direct copy and paste from a recent build and fix;

 

Start copy below this line;

 

 

<!-- Copyright © Microsoft Corporation -->

version="5.1.0.0"

processorArchitecture="amd64"

name="Microsoft.MSE.MSESysprep"

type="win32"

/>

Microsoft Security Client Sysprep module

<!--Windows 7-->

level="asInvoker"

uiAccess="false"

/>

End copy above this line.

 

By far and away the easiest way to do this is using ResourceHacker. Also note that the file is saved in UTF-8 format.

Share this post


Link to post
Share on other sites
By far and away the easiest way to do this is using ResourceHacker. Also note that the file is saved in UTF-8 format.

RecourceHacker is definitely simpler to use -- it only opens up the section that needs to be replaced. I just made the switch, and MSE runs without any problems. I'll have to wait until tomorrow morning, though, when the scan is set to run automatically. Checking the Event Viewer Admin logs and comparing the times of the errors, the auto scan seems to be what's triggering the error.

 

Thanks again. I'll post back tomorrow with an update. So far, so good.

Edited by skay_baltimore

Share this post


Link to post
Share on other sites

can be dleted

This ?

You mean the entire file can be deleted and MSE still function properly?

Share this post


Link to post
Share on other sites

This ?

You mean the entire file can be deleted and MSE still function properly?

 

I think he meant that his post would be deleted. Not sure though :x

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...