SideBySide Error in Application Event Log -- What is it and how do I address it?


  • What does this mean:

    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 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows.

    - <Event xmlns="">
    - <System>
      <Provider Name="SideBySide" />
      <EventID Qualifiers="49409">72</EventID>
      <TimeCreated SystemTime="2011-08-27T04:31:15.000000000Z" />
      <Security />
    - <EventData>
      <Data />
      <Data />
      <Data />
      <Data />
      <Data />
      <Data />
      <Data />
      <Data />
      <Data>c:\program files\microsoft security client\MSESysprep.dll</Data>
      <Data>c:\program files\microsoft security client\MSESysprep.dll</Data>
      <Data />
      <Data />
      <Data />
      <Data />
      <Data />
      <Data />
      <Data />
    Saturday, August 27, 2011 5:13 PM

All replies

  • Hi,


    Microsoft Win32 Side-by-Side service - It is used to manage the use of various versions of the same component(i.e. DLLs, COMs) installed on the same computer.


    “It looks like there was a problem with the SXS manifest for this binary. This manifest is used when multiple versions of a binary need to be referenced. Since this shouldn't occur with MSE, I don't think this will be an issue. Are you able to open the MSE UI and start a scan?  If so, you can ignore this error."


    There’s a same thread you can refer:




    Leo   Huang



    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Marked as answer by Leo HuangModerator Monday, September 5, 2011 1:06 AM
    • Unmarked as answer by saberman Monday, September 5, 2011 3:06 AM
    Tuesday, August 30, 2011 3:49 AM
  • The thread you referred to goes back to the beginning of June 2011.  Someone from Microsoft posted a reply toward the beginning of the thread that they would look into it and respond to the thread.  They didn't.

    It seems to me that since this is an obvious bug in Microsoft's security package (or packaging) it should be addressed and fixed by Microsoft.  One does not get a warm and fuzzy feeling when the systems's security package is generating errors in an event log.

    >Since this shouldn't occur with MSE
    Does this mean there is a potential exploit involving using the erroreous reference to launch a replacement binary?

    • Edited by saberman Monday, September 5, 2011 3:13 AM Typo
    Monday, September 5, 2011 3:12 AM
  • Just installed MSE yesterday and I get this error in the log often. (Was using Norton 360 v5 free from Xfinity before but felt it was overkill for me -- completely uninstalled it and cleaned up the leftover bits, of course.)  This log error didn't happen with previous MSE revisions so it must be something about the latest revs since June, I take it.  As usual, ignore Windows quirks and ms will fix them someday. :)
    Tuesday, September 6, 2011 9:22 PM
  • I just spent around 40 hours testing different scenerios on a test PC and none were successful, when trying to keep Microsoft Essentials AntiVirus application as my 1st choice.
    - The test PC does not receive email and is connected to the Internet.


    This is probably not what you want to hear or want to do, but it is an immediate solution until Microsoft resolves the Microsoft Essentials AntiVirus application ID 72 Side-by-Side issue.



    1) I Uninstalled Microsoft Essentials:
    - The Installation folder was removed automatically.

    2) The 'Action Center' displayed a message to update the definitions.
    - I Updated the Windows Defender definitions.
    - Then I ran 'Quick Scan'.

    3) If you have .NET Extended installed, as I do:
    - URL:
    - -
    - - Run Windows 'Update' many times until there is nothing else to install.

    4) Check to see if you have the following security fixes installed. If not, then install them.
    - KB2473228
    - -
    - KB2487367
    - -
    - KB2468871
    - -
    - KB2533523
    - -

    5) Reboot your PC
    - - Run Windows 'Update' many times until there is nothing else to install.
    - - If so, make sure to reboot your PC at least after the last one is installed.

    6) I created a system image without any AntiVirus solution installed.

    7) The test PC does not receive email.
    - I left it on for 96 hours and there were not any ID 72 Side-by-Side issues in the Event Viewer.

    8) Then I installed the 'FREE' Avast Antivirus
    - It has been running for 96 hours and there were not any ID 72 Side-by-Side issues in the Event Viewer.

    If I can spend this much time trying to find a work around solution, imagine how soon Microsoft could fix the issue with their programmers who have the Microsoft Essentials source code.


    • Edited by usnetxp Tuesday, September 13, 2011 3:33 PM the text box didn't format it as I pasted it
    Tuesday, September 13, 2011 3:30 PM
  • Any new information on this one?

    I'm seeing it on a Windows Server 2008 R2 and a Windows 7 Professional machine? MSE still seems to be working but it's filling my Event Viewer with Errors every day at 12:30 am...

    Monday, January 16, 2012 2:41 AM
  • I too have been having this error message.

    I found that simply renaming the file will stop the error.

    This is not the proper fix.

    c:\program files\microsoft security client\MSESysprep.dll

    Re name to

    c:\program files\microsoft security client\MSESysprep.bak.dll

    I have been running like this for 1 week now with no side by side error appearing im my event logs.


    I have also run  full scans and quick scans to see if there was a error due to the renaming, and there is none.


    The proper fix would be to remove the imaging calls to the 32 bit app not used in the dll file. Via Visual Studio

          <sysprepModule moduleName="$(runtime.system32)\msesysprep.dll" methodName="DllSysprep_Cleanup" stage="cleanup"></sysprepModule>

    • Proposed as answer by Hooded Wednesday, January 18, 2012 1:35 PM
    Wednesday, January 18, 2012 1:31 PM
  • Isn't it fairly obvious by now that Microsoft has no interest in these defects.  Frankly I doubt their ability to actually fix ANY of this.
    Saturday, February 4, 2012 10:53 PM
  • Isn't it fairly obvious by now that Microsoft has no interest in these defects.  Frankly I doubt their ability to actually fix ANY of this.

    I suspect Microsoft would like to fix these types of problems.  The reason they can't do it is a design flaw in .Net that is so deep they would have to redo the entire architecture.
    Sunday, February 5, 2012 4:35 AM
  • Echoing what "Hooded" has said, editing out the "Imaging" block section of the MSESysprep.dll fixes the issue.  It is apparently incompatible with Win7.

    Some details on how to do this can be found here:  

    It would be preferable if Microsoft incorporated a similar repair into an update.

    • Proposed as answer by HDDGuru Sunday, February 19, 2012 4:57 PM
    Sunday, February 19, 2012 4:56 PM
  • And here it is May 7 and still no fix ...  Looks like MS doesn't care ... Unacceptable PEOPLE!
    Monday, May 7, 2012 1:05 PM
  • "Code-Toad" wrote in message news:a9a24370-bb5a-44cf-beb9-6b0dae7819a2...
    And here it is May 7 and still no fix ...  Looks like MS doesn't care .... Unacceptable PEOPLE!
    In case you hadn't heard, MS released a new version of MSE a couple of weeks ago.

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Monday, May 7, 2012 2:39 PM