#192 COM Surrogate conflict?

none
open
nobody
1
2012-11-04
2012-10-30
Mark
No

Immediately after installing Classic Shell v3.6.2 (windows explorer features only) on my 2 computers, I began getting error messages stating 'COM surrogate has stopped working' periodically on both computers. I click the 'close' button, and everything works fine for a while, then I get the error message again.

I tried reducing the number of features (returned 'navigation pane style' to 'Windows Vista,' 'add icon overlay for shared folders' to 'off,' etc.) and the number of error popups seemed to be reduced, but the error was not eliminated. Is it possible that installing Classic Shell has replaced a .dll or.ocx file with a different version than my system is expecting? Or do you have some other idea as to why this is happening and how to fix it? The 'COM Surrogate' error message indicates that 'RPCRT4.DLL' is the specific file that caused the conflict, and it is always this file that is listed as the source of the conflict, but this is apparently a normal Windows file, so I'm hesitant to mess with it without more specific guidance - I considered replacing it with a fresh copy of the .dll, but thought I would consult with you first to see if you thought that would help the situation.

One of the systems is running Windows 7 Pro 64-bit, the other is running Windows 7 Home premium 32-bit. Both have been updated, drivers updated, etc., and neither exhibited this error until after installing Classic Shell, so I'm reasonably certain that this is the install that caused the error messages. Any suggestions/ideas/help would be appreciated. I really like the 'don't scroll to the bottom,' and 'up button,' features, and really don't want to uninstall. TIA for any help.

Discussion

  • Ivo Beltchev
    Ivo Beltchev
    2012-10-30

    Classic Shell definitely doesn't replace any system files. It may be something I'm doing in my code that exposes a problem in your system.

    It is suspicious that both of your machines have the same problem. It must be an incompatibility with a piece of software that is installed on both.

    This page: http://helpdeskgeek.com/help-desk/fix-com-surrogate-has-stopped-working-in-windows-7/ suggests it may be a problem with a codec and also suggests some potential solutions. Let me know if any of them work for you.

    BTW, do not mess with RPCRT4.DLL. It is unlikely it's corrputed.

     
  • xpclient
    xpclient
    2012-11-01

    @Mark, Nothing changed at all for Classic Explorer in 3.6.2 so it must be some codec or shell extension crashing. COM Surrogate is DLLHost.exe. It runs out-of-process COM objects. To troubleshoot, you could open Programs and Features (Add/Remove Programs) and arrange them by Date Installed and see which programs you recently installed that may be causing the crashes.