Setup library msgrocm.dll could not be loaded, or function OcEntry could not be found. Please advise
I seem to have a problem with getting to Add /Remove Windows Components section. Every time I try to click on Control Panel/Add Remove Programs/Add windows Components, the following message comes up; Setup library msgrocm.dll could not be loaded, or function OcEntry could not be found. Please advise
December 17th, 2010 6:20am

Hi jaderob, Follow the below steps and check the results: a. Click Start, point to Control Panel, and then click System.b. On the Advanced tab, click Environment Variables.c. Under System Variables, click Path, and then click Edit.d. Click inside the Variable value box, and then press END to put the insertion point at the end of the Variable value box.e. Type ;%SYSTEMROOT%\SYSTEM32\WBEM, and then click OK.f. Click OK, and then click OK. Regards:Samhrutha G S - Microsoft Support.Visit our Microsoft Answers Feedback Forum and let us know what you think.
Free Windows Admin Tool Kit Click here and download it now
December 18th, 2010 1:26am

HiI am having similiar issues and tried the suggestion above with no positive fix. I am using Win XP Media SP3. Thx in Adv.
January 1st, 2011 11:45pm

If the WBEM stuff is missing from your PATH statement, you may have other problems, but you will not have this problem.The result after adjusting the PATH variable would be:It still doesn't work. When invoking Add/Remove Programs, Add/Remove Windows Components, you see a message like this:Windows XP SetupSetup library msgrocm.dll could not be loaded, or function OcEntry could not be found.Contact your system administrator. The specific error code is 0x7e.When you click OK, you see a message like this:Windows XP SetupThe application could not be initialized.Assuming XP is installed on your C drive...You will see that message if the following file is missing or corrupt:c:\windows\system32\setup\msgrocm.dllThe file should not be missing or corrupt since it is one of the 3498 Protected Files that XP monitors under Windows File Protection.If any of those files ever come up missing, Windows File Protection should quickly and silently replace it, so something has gone wrong.You can navigate to the c:\windows\system32\setup folder and see if the msgrocm.dll file is there. If it is there, you can rename it or delete it and then (if your Windows FIle Protection is not afflicted), the missing file will be quickly and silently replaced with a backup copy. Press F5 to refresh the folder view and see if the file is replaced.When Windows File Protection replaces the missing file, you will see an event like this is the Event Viewer System log:Event Type: InformationEvent Source: Windows File ProtectionEvent Category: NoneEvent ID: 64002Description:File replacement was attempted on the protected system file c:\windows\system32\setup\msgrocm.dll. This file was restored to the original version to maintain system stability. The file version of the system file is 4.7.0.3001.If the msgrocm.dll file is not automatically replaced, you can replace it manually.XP keeps copies of the 3498 Protected Files in the following folder:c:\windows\system32\dllcacheYou can use Explorer to navigate to the c:\windows\system32\dllcache folder and locate the backup copy of the file and copy/paste it into the c:\windows\system32\setup folder.When pasting in the copy, respond in the affirmative if asked to overwrite or replace the current file. Do, or do not. There is no try.I decided to save up points for a new puppy instead of a pony!
Free Windows Admin Tool Kit Click here and download it now
January 2nd, 2011 8:12am

If the WBEM stuff is missing from your PATH statement, you may have other problems, but you will not have this problem.The result would be:It still doesn't work. When invoking Add/Remove Programs, Add/Remove Windows Components, you see a message like this:Windows XP SetupSetup library msgrocm.dll could not be loaded, or function OcEntry could not be found.Contact your system administrator. The specific error code is 0x7e.When you click OK, you see a message like this:Windows XP SetupThe application could not be initialized.Assuming XP is installed on your C drive...You will see that message if the following file is missing or corrupt:c:\windows\system32\setup\msgrocm.dllThe file should not be missing or corrupt since it is one of the 3498 Protected Files that XP monitors under Windows File Protection.If any of those files ever come up missing, Windows File Protection should quickly and silently replace it, so something has gone wrong.You can navigate to the c:\windows\system32\setup folder and see if the msgrocm.dll file is there. If it is there, you can rename it or delete it and then (if your Windows FIle Protection is not afflicted), the missing file will be quickly and silently replaced with a backup copy. Press F5 to refresh the folder view and see if the file is replaced.When Windows File Protection replaces the missing file, you will see an event like this is the Event Viewer System log:Event Type: InformationEvent Source: Windows File ProtectionEvent Category: NoneEvent ID: 64002Description:File replacement was attempted on the protected system file c:\windows\system32\setup\msgrocm.dll. This file was restored to the original version to maintain system stability. The file version of the system file is 4.7.0.3001.If the msgrocm.dll file is not automatically replaced, you can replace it manually.XP keeps copies of the 3498 Protected Files in the following folder:c:\windows\system32\dllcacheYou can use Explorer to navigate to the c:\windows\system32\dllcache folder and locate the backup copy of the file and copy/paste it into the c:\windows\system32\setup folder.When pasting in the copy, respond in the affirmative if asked to overwrite or replace the current file. Do, or do not. There is no try.I decided to save up points for a new puppy instead of a pony!
January 2nd, 2011 8:12am

Joselbarra -- Thank you for the detailed explaination and fix. I tried your suggestions by going to the appropriate directory and1. renamed the msgrocm.dll file and doing a F5 noticed that a new file was created. I then went to control panel and tried to goto add/remote windows components and got the same error. I did notice that the msgrocm.dll file version is 5.1.0.111110 ( Both the backup and the newly created file had the same version). Date created 9/16/2003.2. I then went to the ddlcache folder and noticed that msgrocm.dll is the same version. I copied and pasted this file to setup directory and was still unsuccessful in unloading the windows component.I do have another system here that is running win7 but not sure what version the msgrocm.dll it has.
Free Windows Admin Tool Kit Click here and download it now
January 2nd, 2011 6:50pm

Is the afflicted system running Windows XP?For XP Service Pack 3, the version is 4.7.3001 (like my Event Log said when Windows File Potection replaced it).For XP Service Pack 2, the version is 4.0.0155.I am running XP SP3 and replaced the file with the SP2 version on and it still works okay (it is clumsy to do that when Windows File Protection keeps wanting to replace it).You can check the version by right clicking the file, Properties, Version tab...At least you know something about how Windows File Protection works now ;)Do, or do not. There is no try.I decided to save up points for a new puppy instead of a pony!
January 2nd, 2011 7:31pm

Yes, I am running Win XP Media Center Edition 2002 SP3. File Version is 5.01.1110. Thx in Adv.
Free Windows Admin Tool Kit Click here and download it now
January 2nd, 2011 10:21pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics