DCOM Error 10021 is logged when you run a WinRM command against a remote computer that has update 936059 applied

View products that this article applies to.

Error message description

When you run a Windows Remote Management (WinRM) command against a remote computer that has update 936059 applied, some errors may be logged in the System log. These errors may resemble the following:

↑ Back to the top

Cause

This problem occurs because the update for Windows Remote Management (WinRM) that is included with Microsoft Knowledge Base article 936059 incorrectly sets the security descriptor for the COM Application under the following subkey:

HKEY_CLASSES_ROOT\AppID\{3e5ca495-8d6a-4d1f-ad99-177b426c8b8e}\LaunchPermission

↑ Back to the top

Resolution

Method 1

You can use the Component Services MMC snap-in to set the correct access control entries. To do this, follow these steps:

Click Start, click Run, type DCOMCNFG, and then click OK.
Expand Component Services, expand Computers, expand My Computer, and then click DCOM Config.
Right-click Microsoft Windows Remote Shell Host, and then Properties.
On the Security tab, under Launch and Activation Permissions, select Customize.
Click Edit.
Assign the following permissions:
- Everyone - Local Launch and Local Activation
- Network Service, System, Administrators Group, Interactive - Local Launch, Remote Launch, Local Activation and Remote Activation (all check boxes)

Method 2

If you must deploy this change to multiple computers, you can update the registry value by using a script. To have us create and run this script for you, go to the "Fix it for me" section. If you would rather do this yourself, go to the "Let me fix it myself" section.

Fix it for me

To create and run this script automatically, click the Fix this problem link, click Run in the File Download dialog box, and then follow the steps in this wizard.

Note this wizard may be in English only; however, the automatic fix also works for other language versions of Windows.

Note If you are not on the computer that has the problem, you can save the automatic fix to a flash drive or to a CD, and then you can run it on the computer that has the problem.

Now go to the "Did this fix the problem?" section.

Let me fix it myself

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756 How to back up and restore the registry in Windows

To deploy this change to multiple computers, update the registry value by using the following script:


reg add HKEY_CLASSES_ROOT\AppID\{3e5ca495-8d6a-4d1f-ad99-177b426c8b8e} /v LaunchPermission /t REG_BINARY /d 0100048098000000A400000000000000140000000200840006000000000014000B000000010100000000000100000000000314001F000000010100000000000512000000000314001F000000010100000000000513000000000314001F000000010100000000000514000000000318001F00000001020000000000052000000020020000000314001F00000001010000000000050400000001010000000000051200000001020000000000052000000020020000 /f

↑ Back to the top

Did this fix the problem?

Check whether the problem is fixed. If it is fixed, you are finished with this article. If it is not fixed, you can contact support.

↑ Back to the top

Rapid publishing disclaimer

Microsoft corporation and/or its respective suppliers make no representations about the suitability, reliability, or accuracy of the information and related graphics contained herein. All such information and related graphics are provided "as is" without warranty of any kind. Microsoft and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information and related graphics, including all implied warranties and conditions of merchantability, fitness for a particular purpose, workmanlike effort, title and non-infringement. You specifically agree that in no event shall Microsoft and/or its suppliers be liable for any direct, indirect, punitive, incidental, special, consequential damages or any damages whatsoever including, without limitation, damages for loss of use, data or profits, arising out of or in any way connected with the use of or inability to use the information and related graphics contained herein, whether based on contract, tort, negligence, strict liability or otherwise, even if Microsoft or any of its suppliers has been advised of the possibility of damages.

↑ Back to the top