WMI Scripts Generate "Permission Denied" Error Message

Support for Windows XP has ended

Microsoft ended support for Windows XP on April 8, 2014. This change has affected your software updates and security options. Learn what this means for you and how to stay protected.

This article has been archived. It is offered "as is" and will no longer be updated.
Symptoms
Windows Management Instrumentation (WMI) scripts that run on a computer that is running Windows 95, Windows 98, Windows Millennium Edition (Me), or Windows 2000 and that connect to a remote Windows XP-based computer may not work correctly, and may generate a "Permission denied" error message. This issue also affects WMI consumer programs.

You may also receive the following error return code:
0x80041003 WBEM_E_ACCESS_DENIED
Cause
In Windows 2000 and Windows XP Beta 1, all providers are loaded in-process to the WinMgmt service, which runs under the LocalSystem account. After Beta 2, the providers are required to load into a provider subsystem with the NetworkService security account.

In Windows 2000, the WinMgmt service is a separate automatic service that runs under the LocalSystem account. To minimize the overhead of system services and enable tighter control over system resource use, the WinMgmt service has been migrated to SVCHOST. The migration itself is transparent for WMI clients. However, WinMgmt now shares the same host with other system services. The security regulations for the service host require that all the remote connections use packet-level authentication (RPC_C_AUTHN_LEVEL_PKT).
Resolution

Windows 2000

To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack

Windows 95, Windows 98, Windows Me

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix should have the following file attributes or later:
   File name      Operating system   -------------------------------------------------   Wbemprox.dll   Windows 95, Windows 98, Windows Me				

Status
Microsoft has confirmed that this is a problem in Windows 2000. This problem was first corrected in Windows 2000 Service Pack 2.
0x80041003
Properties

Article ID: 282949 - Last Review: 01/12/2015 17:16:47 - Revision: 5.0

Microsoft Windows XP Home Edition, Microsoft Windows XP Professional, Microsoft Windows 2000 Server, Microsoft Windows 2000 Advanced Server, Microsoft Windows 2000 Professional Edition, Microsoft Windows 95

  • kbnosurvey kbarchive kbqfe kbhotfixserver kbbug kberrmsg kbfix kbwin2000presp2fix KB282949
Feedback
ERROR: at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)