We have a 32-bit application running on Win 7 64-bit. For almost all our users (and throughout testing), the application runs successfully. But, for one of our users the application's WMI calls are failing. I changed the DLL to run a VBS script to do the WMI call and it still did not work. So, I had the user open a command window and run the VBS script. The script worked. I then had them open a 32-bit command window and run the VBS script. The script failed with the same error as our application is getting using C++ calls - WBEM_E_PROVIDER_LOAD_FAILURE (0x80041013). Any idea why this would be or how to fix the issue? Do I need to repair WMI? If so, can I repair just the 32-bit part? This is the VBS script: strComputer = "." Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\CIMV2") Set colItems = objWMIService.ExecQuery( _ "SELECT * FROM Win32_Process",,48) For Each objItem in colItems Wscript.Echo objItem.ProcessId & ";" & objItem.Name & ";" & objItem.WorkingSetSize Next Thanks, Mike HigginbothamRegards, Mike Higginbotham

Hi, This is the TechNet Forum for questions regarding Window 7. Unfortunately, your question is related Script. For better assistance please ask for help in the Scripting Forums: http://social.technet.microsoft.com/Forums/en/ITCG/threads/ The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thanks for understanding Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi, This is the TechNet Forum for questions regarding Window 7. Unfortunately, your question is related Script. For better assistance please ask for help in the Scripting Forums: http://social.technet.microsoft.com/Forums/en/ITCG/threads/ The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thanks for understanding Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Thanks for the response. I used scripting just as an example. We first noticed the problem using C++ calls. The problem is not in the script. The script runs fine in a 64-bit command window but the WMI calls fail in a 32-bit command window.Regards, Mike Higginbotham