Microsoft Knowledge Base Email Alertz

(838860) - Describes a problem where you receive an error message when you try to use Add or Remove Programs on a Windows Server 2003-based computer.

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 838860 - Last Review: February 19, 2008 - Revision: 2.0

You receive a "Setup Library wbemupgd.dll could not be loaded" error message when you use Add or Remove Programs in Windows Server 2003

System TipThis article applies to a different version of Windows than the one you are using. Content in this article may not be relevant to you. Visit the Windows Vista Solution Center

SYMPTOMS

When you try to use Add or Remove Programs on a Microsoft Windows Server 2003-based computer, you may receive the following error message:
Setup Library wbemupgd.dll could not be loaded, or function OcEntry could not be found. Contact your system administrator. The specific error code is 0x7e.

CAUSE

This problem occurs because the Path system variable has changed.

RESOLUTION

To resolve this problem, use one of the following methods:
  • Method 1
    1. Click Start, right-click My Computer, and then click Properties.
    2. Click the Advanced tab, and then click Environment Variables.
    3. Click Path in the System variables list, and then click Edit.
    4. Replace three of the paths in the Variable value box. To do this, follow these steps:
      1. Delete the following three paths in the Variable value box:
        %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem
      2. Type the following text in the Variable value box to replace the paths that you removed in step 4a.
        drive:\Windows\System32;C:\Windows;C:\Windows\System32\Wbem
        Note drive is the hard disk drive where Windows is installed, and Windows is the folder in which Windows is installed.
      3. Click OK three times.
  • Method 2
    1. Click Start, click Run, type regedit, and then click OK.
    2. Locate and then click the following registry subkey:
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment
    3. Make sure that the type of the Path registry entry is REG_EXPAND_SZ.

      Note If the type is not REG_EXPAND_SZ, delete the Path registry entry, and then re-create a Path registry entry that has the REG_EXPAND_SZ type.
    4. Right-click the Path registry entry, and then click Modify.
    5. Type the following path in the Value data box:
      %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem

APPLIES TO
  • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
  • Microsoft Windows Small Business Server 2003 Standard Edition
Keywords: 
kbwinservsetup kbprb KB838860
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

AM Report As Irrelevant  
Written: 11/15/2004 6:08 AM
Thanks for this solution. It works perfect !!

Pocall - defgh NOSPAM-AT-NOSPAM eircom.net Report As Irrelevant  
Written: 1/22/2005 12:47 PM
my path variable had dissappeared completely, I added it with the values from microsoft and it still didnt work. I then added it under user variables for administrator and it worked again, hope this helps

Iggy Report As Irrelevant  
Written: 11/7/2005 8:47 AM
Thanks. Applied SP1 and it broke it. As soon as I removed and added per instructions I was able to get into configuration. Thanks Again.

Noob Report As Irrelevant  
Written: 11/22/2005 1:53 AM
Thx a lot! GPO´s allready running too!

Anonymous User Report As Irrelevant  
Written: 2/10/2006 12:03 PM
Yep me to..had to add path staement under usere variable and then it worked!!!