When Windows Explorer generates the thumbnail image from the ASF file, the Dllhost.exe process consumes excessive CPU resources. Cause. This issue occurs because the index object in the ASF file is corrupted. Resolution. Update information. To resolve this issue, install update rollup 2855336.

Locate the following path: HKEY_LOCAL_MACHINE\Software\Microsoft\OLE. Change the EnableDCOM string value to N. Restart the operating system for the changes to take effect. Use DCOMCNFG.EXE. Run Dcomcnfg.exe. If you are running Windows XP or Windows Server 2003, perform these additional steps: Click the Component Services node under Console Root.

When the default (machine-wide) authentication is set to None on Windows NT 4.0, an error occurs during the launching of Dllhost.exe and it terminates. The client's creation API gets a CO_E_SERVER_EXEC_FAILURE error.

This article describes how to use the Debug Diagnostics v1.2 tool to troubleshoot a Microsoft Internet Information Services (IIS) process that has stopped responding. When an IIS process like Inetinfo.exe, Dllhost.exe, or W3wp.exe stops responding (hangs), you may experience any of the following symptoms: A Web page does not load correctly.

Dllhost.exe is the system-provided surrogate that is used by a COM DLL (in- process) server to run in its own separate process. When the default (machine-wide) authentication is set to None on Windows NT 4.0, an error occurs during the launching of Dllhost.exe and it terminates.

Examples of an IIS process are Inetinfo.exe, Dllhost.exe, and W3wp.exe. When high CPU usage by an IIS process occurs, you experience one or more of the following symptoms: A Web page does not load correctly.

Fixes an issue in which memory is exhausted by the dllhost.exe process when you select or move a video file in Windows Explorer. This issue occurs after you install update 2670838 in Windows 7 or Windows Server 2008 R2.

Fixes an issue in which a memory leak occurs in a Dllhost.exe process that hosts the MQSAgent2 COM+ application in BizTalk Server.

This issue occurs when you run such rules extensions or custom MAs after you change the configuration file for MIISServer.exe, Mmsscrpt.exe.config, or Dllhost.exe.config. For example, you edited the MIISServer.exe.config file to change the default batch size for processing sync entries for the FIM Service MA.

Dllhost.exe. For example, you edit the MIIServer.exe.config file to change the default batch size for processing sync entries for the FIM Service MA. In this case, the synchronization engine installer for this update intentionally does not replace the configuration file to avoid deleting your previous changes.