Error 0x80070005 when using SWbemLocator.ConnectServer to initiate a WMI session despite using the correct username and password

System Requirements:

  • WMI 1.5 or higher
  • Windows 95, 98, 98SE, Millennium
  • Windows NT 4.0, 2000, XP, 2003, Vista, 2008, 7

The Problem:

When using WMI’s SWbemLocator.ConnectServer class to log onto a remote system, you receive an 0x80070005 access denied error (Decimal -2147024891).

This error occurs even though the username and password are correct and the account credentials are synchronised properly between the local and remote machine – either by domain or manually in a workgroup.

More Info

The classfull connection line for using SWbemLocator is:

Set objWMIService = objSWbemLocator.ConnectServer(<computerName>, <wmiDefaultClassPath>, <username>, <password>)

for example:

Set objWMIService = objSWbemLocator.ConnectServer("", "root\cimv2", "Administrator", "12345abcde")

The Fix

There is a very good chance that the problem you are having is to do with the username you are entering. You need to ensure that you are prefixing the username with the logon domain.

For example if your domain is camie.local your username should be camie\Administrator

Set objWMIService = objSWbemLocator.ConnectServer("", "root\cimv2", "camie\Administrator", "12345abcde")

But I’m using a workgroup!

Don’t worry, you can do one of three things.

  1. Prefix the remote machine name (the local logon domain)
  2. Prefix the workgroup
  3. Send a null logon domain
Set objWMIService = objSWbemLocator.ConnectServer("", "root\cimv2", "myHostName\Administrator", "12345abcde")

Set objWMIService = objSWbemLocator.ConnectServer("", "root\cimv2", "workgroup\Administrator", "12345abcde")

Set objWMIService = objSWbemLocator.ConnectServer("", "root\cimv2", "\Administrator", "12345abcde")

Using one of the above, you should be able to connect to the remote workstation. If you are dealing with a mix of workgroups or cannot know the hostname in advance I suggest using \<username> with I have tested to work on Windows 95 right through to Windows 7.

How to Enable Web Based Enterprise Management (WBEM) / Windows Management Instrumentation (WMI) for Remote Access under Windows Millennium Edition

System Requirements:

  • Windows Millennium Edition


The Problem:

This document outlines the steps required to connect to a Windows Millennium machine using WMI using either a Monkier (inherited session credentials) or SWbemLocator.ConnectServer (specific, stated logon credentials).

This is often difficult to achieve, especially in a domain environment or an environment where more modern versions of Windows need access to the remote WMI service.


More Info

Windows Millennium Edition ships with the latest version of WMI for Windows 9x, that being version 1.5.

This guide will show you how to properly install WMI in order to facilitate remote access connections over a Network. Please note that while this will enable WMI requests over a LAN, the settings will not discriminate between a LAN and an Internet connection. Consequently firewall technology should be employed when dealing with systems that expose a direct peer-to-peer Internet connection.

More Info: WMI on computers running Windows 98, 98SE and Windows Millennium Edition


The Fix

The steps below will enable you to connect remotely over WMI under some circumstances (but not all). These steps must be applied to install WMI and configure it before you can change the advanced remote connection settings.

Just as with the WMI installation for Windows 95/98 and unlike the Windows NT. The WMI 1.5 installer does not include the rather useful DCOMCnfg.exe utility that is required for GUI configuration of WMI for remote access. Thankfully the DComConfig utility was made available separately for Windows 9x. Despite being branded for Windows 95/98, the program works fine under Windows Millennium if you are more comfortable using the GUI to configure WMI than using the registry file at the end of this document.


Configure DCOM

Once you have installed dcm95cfg.exe you must configure DCOM. To configure DCOM run the DCOMCnfg utility found in c:\windows\system

DComCfg Utility Launch

  1. By default the “Enable Distributed COM on this computer” check box on the Default Properties tab should be ticked. Often if WMI isn’t working, this has inexplicably become unchecked, disabling DCOM completely.DcomCnfg Screen 1
  2. This will enable WMI to run on the local computer, but not from remote network connections. To enable the basic level of remote access check the “Enable remote connection” box on the Default Security tab. If this doesn’t work for you, keep reading!DcomCnfg Screen 2
  3. Restart the computer.

It is important to understand that unlike with Windows NT, Windows 9x doesn’t have the concept of a special system service. Consequently DCOM won’t start WMI when it is requested from the network. In order to enable on-demand access the WinMgmt.exe program in c:\windows\system\wbem needs to be running.


This dos prompt command will run the process for the duration of the session. You can always confirm that it is running by pressing Ctrl + Alt + Del once and viewing the task manager

WinMgmt Process in Ctrl + Alt + Del Screen

If you want to persistently run WinMgmt.exe as a ‘Service’ add the following information to the registry as shown.


Setup WinMgmt as a start service

Advanced Remote Access Settings

The above settings should work between NTLM enabled Windows 9x boxes and NT 4 systems, however you may have problems if the Active Directory extensions are installed or if you are attempting to connect from a Windows 2000, XP, 2003, Vista, 2008 or 7 machine.

Connection difficulties seem particularly true if you are using SWbemLocator.ConnectServer or are in any way connecting via IIS.

Do appreciate that this guide isn’t covering more basic things like “synchronise your accounts and passwords” between workgroup systems, ensure that you have IE 6.0 SP1 installed or that you have Windows Scripting Host 5.6 installed and so on.

First off, re-register the WinMgmt stack using the following command in the c:\windows\system folder

RegSvr Command for WMI

WBEM ships with an additional configuration utility, the WBEM Control app, found in c:\windows\system\wbem\


On the advanced tab enable the “Enable Anonymous Connection with share level security” setting and restart the computer.

Enable Anonymous Share Access

This setting allows WMI to respond to network requests that do not carry the required account credentials registered as having access to the WMI class hierarchy.

If you are now able to connect using SWbemLocator.ConnectServer you may like to try to reconfigure WMI to use WMICntl to assign permissions to WMI. To do that simply use the Security tab and, selecting Root, press the Security button and add in the user accounts that you want to gain remote access with to the security permissions list.

WMI Control Security

All being well, you should now have a working Windows 98 machine which supports Remote WMI from modern Windows systems.

If you would like to enable all of these settings without launching their respective utilities, you can use this registry script to automatically configure workstations with the remote access settings.




"Enable for ASP"=dword:00000000



See Also

View: How to Enable Web Based Enterprise Management (WBEM) / Windows Management Instrumentation (WMI) for Remote Access under Windows NT 4.0

View: How to Enable Web Based Enterprise Management (WBEM) / Windows Management Instrumentation (WMI) for Remote Access under Windows 95, 98/98SE

Removing Windows Media Player 7 from Windows Millennium

Windows Millennium… The final stage in MS-DOS’s evolution. With this release of Windows, 9x is no more.

As with a lot of Microsoft products… you always feel that you get lumbered with MegaBytes of unnecessary data, programs and dll files.

You could call this page the Head Quarters of the “Say No To 7” campaign.

So what can be done about it:.

We want some of the extra features. We want the operating system shell, Kernel and GUI enhancements, but not all of the features:

Updated 22nd February 2006

Windows Media Player 7

This application may be Microsoft’s first attempt at an all in one media player, and in my opinion… they didn’t quite hit the mark. The biggest problem with it is its resource requirements. They are huge. The application takes far too long to load even on the fastest of systems. This of course means that that you will run out of available memory, run up a huge swap file and have to reboot the system.

There are still problems with the CD audio, you are lumbered with features that you will never use such as the mobile device synchronisation options. All of these could be optional and save on the space.. but no. As with windows, office and so many apps before it you can’t.

NOTE: This has not been tested any other Operating System than Windows Millennium

For those of you devoted to Windows Media Player 6.4 here’s how to get your music life back (Please make sure to read all instructions before proceeding):

To uninstall Windows Media 7 under Windows Millennium

  1. Download and Re-install WM7 from   (This is required to install the uninstall routines)
  2. Open a Command Prompt
  3. On the prompt type(Assuming that ME is installed on c:):
    c:\windows\inf\unregmp2.exe /SafeUninstall:c:\windows\inf\wmp.inf
  4. Press enter
  5. Reboot the Computer
  6. Open a Command Prompt
  7. On the prompt type(Assuming that ME is installed on c:):
    c:\windows\inf\unregmp2.exe /SafeUninstall:c:\windows\inf\mplayer2.inf
  8. Press enter
  9. Reboot the Computer*
  10. Delete the directory C:\Program Files\Windows Media Player
  11. Download and install Windows Media Player 6.4 from

You will now have removed Windows Media 7 from Windows ME, and replaced it with a full copy of Windows Media 6.4:

If you do not wish to install and use Tweak UI, you can place the commands at step 6 and 15 into a Start: Run dialogue box and selecting OK. If this fails then you will have to use Tweak UI

* After this point, and only if you are an advanced user, you can access the system registry and remove all references to Windows Media Player, WMP, mplayer and c:\program files\Windows Media Player . Be sure to back the registry up first of all and Re-Boot after you have finished. This will ensure that you have removed most traces of 7 from your system, and will help keep the registry tidy.
You can also remove certain system files regarding Windows Media Player. Click Here to download a partial list.

No Media Player… No CD Player

New Version 1.3 – Now with Auto Start support!

In removing 7 from your computer, you have now removed Audi CD capabilities. I have compiled a file that will install the Windows 98 CD-Player on Windows ME

  1. Download (251 KB) from this server
  2. Run the file
  3. Make sure to read all on-screen instructions before proceeding
  4. After installation, all of the required system files will have been updated with the CD Player routines. Except the registry
  5. The registration entry’s will be listed on the desktop as 0.reg – 12.reg. You will need these files in order to install and use auto start
  6. Insert files 0.reg – 12.reg by double clicking them and saying OK *
  7. Open ‘Control Panel’, ‘Add/Remove Programs’. Go to the ‘Windows Setup’ tab, select ‘Multimedia’. Tick ‘CD Player’ and click ‘OK’
  8. The files will install
  9. Reboot Your Computer

* Back up your system registry before running this update

After Running this update you will have to install the registry update files found on the desktop. These files update the Add/Remove Programs tab as to the presence of CD Player and enable the CD Audio auto start feature. I plan to write a automated installation file soon.

To uninstall Windows Media 6.4 under Windows Millennium

  1. Download and Re-install WM6.4 from   (This is required to install the uninstall routines)
  2. Open a Command Prompt
  3. On the prompt type(Assuming that ME is installed on c:):
    c:\windows\inf\unregmp2.exe /SafeUninstall:c:\windows\inf\mplayer2.inf
  4. Press enter
  5. Reboot the Computer*
  6. Delete the directory C:\Program Files\Windows Media Player

You will now have removed Windows Media Player completely from Windows ME.

* After this point, and only if you are an advanced user, you can access the system registry and remove all references to Windows Media Player, WMP, mplayer and c:\program files\Windows Media Player . Be sure to back the registry up first of all and Re-Boot after you have finished. This will ensure that you have removed most traces of 6 from your system, and will help keep the registry tidy.
You can also remove certain system files relating to Windows Media Player.

Keeping Windows Media Player 6.4

So, you’ve decided to do the honourable thing. You value your system resources, that or your worried about your Grid Computing project results being crippled by WM7.

If you check your resources, you’ll find that WM7, playing your average MP3 can take between 60% and 90% of your system processor resources away from you. Catastrophic if you use a processor dependant application such as SETI@Home. In contrast, the New WM8 (Windows XP only) takes 50% – 70% and Windows Media 6.4 anything between 1% and 15% of system resources*

Microsoft, are in fact updating Windows Media 6. They don’t publicise this, as they want everyone on version 7 or above. Microsoft are updating 6.4 to suit the new codec’s and Internet Explorer versions that they produce. This inevitable was their own mistake in deciding not to allow Windows 95 and NT 4 users to use WM7. For what ever reasons they chose to do this, technical or political fortunately for us we can still get the most out of 6.4.

The latest build of Windows Media 6.4 is version:

For Windows 3.1x:
(Maximum Internet Explorer version 5.0 build 913.2206)

For Windows NT 3.5x:
Not released
(Maximum Internet Explorer version 5.0 build 913.2206)

For Windows 95:
(Maximum Internet Explorer version 5.5 SP2 build 4807.2300 + Q320920)

For Windows NT4. 98 and Millennium:
(This version ships with Internet Explorer 6.0 SP1 build 2800.1106 + Q828026)

For Windows 2000:
(This version ships with Internet Explorer 6.0 SP1 build 2800.1106 + Q828026)

For Windows XP Home, Professional:
(This version ships with Internet Explorer 6.0 SP2 build 2900.2180)

For Windows Server 2003:
(This version ships with Windows 2003 Internet Explorer 6.0 build 3790.0)

If your using Windows Media Player v6.4, you can extend its functionality by installing the following patches and utilities.
Note: These will not work with Windows Media Player for Windows 3.x. Do not install on Windows XP installations

Patch Downloads Codec Downloads

The remaining life in Windows Media Player 6 is on borrowed time. With Windows 95 having been retired on Dec 31st 2001 and likewise with NT 4 / Windows 98 being retired in July 2003 users can expect 6.4 to become a distant memory.

Microsoft have always had a thing about it’s media players. Distributing the old MCI version of it right up until Windows Millennium. Even then in Windows Millennium 6.4 remained present side by side with 7.0. Windows XP no longer included the Windows 3.11 MCI version, but 6.4 remains side by side with 8.0 & 9.0.

I predicted that “Windows .net, the next Windows version due in 2003 will not contain 2 versions of Media Player. The minimum system specification by then won’t warrant it. But by then you are likely to see the ability to choose your Media Player and Internet Browser, at least the front end of it. Personally, I’ll be sticking with Microsoft’s contributions to the industry.”

With the release of Windows 2003 Server, the renamed Windows .net, Windows Media Player 6.4 still ships along side 9.0. Windows Media Player 9 updates that modify the core .OCX drivers in media player will however continue to incriment the Windows Media Player 6.4 build number, as has been shown by the univeral rise to build version 1128 with the relase of Q808226.

But at the end of the day its entirely down to personal preference

*Statistics taken on an Intel PIII 733eb with 256 MB RAM

Windows Media Player 9.0

Windows Media Services 9 is upon us, and with this comes Windows Media Player version 9. What makes this significane is that it, unlike version 8 can be installed on other Operating Systems. I can confirm from seeing the beta’s that 9 installs on Windows 2000 and runs quite well. I’ve not tried it on any 9x OS, however under Microsofts Operating System retirement policy, I would expect it to install on Windows Millennium, and perhapse Windows 98SE, but I would hold me breath over any of the 98’s.

Windows Media Player 9 is virtually identical aestetics wise to that of Windows XP’s version 8, however there have been refinments to both the code, the layout, the look and most importantly the codecs and underlying backbone of Windows Media format.

The player in its beta format handles better than Windows Media 7 does. However users won’t be surprised to learn that it covers the same sort of CPU and memory overhaeds as 7.1 and 8 respectivly do on their OS’s. This is perhapse the price we pay for eveoloution, who knows. The crux of the matter is that 6.4 unfortunatly is becoming more and more unstable especially when connecting to streaming servers. Its reliability is deminsihing.

With this volly of new Windows Media technologies, I can only guess that there will be new ActiveX plugins finally to facilitate the advances in browser technology and in Streaming technology. This change will spell the ultimate end for 6.4. Even if the 9 format will play on 6.4, it is unlikly that it will be able to play back on 6.4’s ActiveX, that has for so long been the only realy way to deliver any Windows Media, ASx / WMx / Proparetly WM6 format content over the internet.

I still use 6.4 for my MP3 listening and for video playback where it can handle it. But I’m increasingly using 8 to watch streaming content and inevitably under Windows XP to listen to Music CD’s. Reluctantly I’m being dragged kicking and screaming into the 21st MultiMedia century, and I imagine so will you. Although not necesarily with Microsofts player.

The Question that I can see your all posing to me right at this moment… Can I remove Windows Media Player 9.0.. answer… Not the Beta version you can’t!

UPDATE 7th August 2002:
Having now had a chance to play with 9 properly, I have to say that I am very much impressed. Microsoft have clearly been listening to the Windows Media community over it.

Some key points worth noting are:

  • The new Taskbar Tile player, perfect for keeping an eye on web feeds, dvd’s, visualisations and controlling your multi media
  • Info Centre. New improved to provide track and album info, as well as links to purchasing the music
  • Improved CD recognition technologies. Non-US CD versions of a release now display the correct track data (UK Releases at least)
  • .NET services bar. I suspect that this will become more of a feature in the future as the inductry drives towards cleaning up the Internet Music environment
  • New A/V mulitmedia effects. Such as cross fading of media and the little touches on minimisang and maximising video

Removing Windows Media Player 8

Can it be done, can it be removed From Windows XP?

No, not using the methods described here on this page. I also do not want to experiment with this as, until we see Windows Media Player 8.1 arrive, there is no way to re-install it once its gone, short of a system re-install.

However, due to the current legal wrangles going on between the Microsoft Corporation, the United States and the European Union. Microsoft have submitted to the findings of the litigation and, in the forthcoming Microsoft Windows XP Service Pack 1 (SP1), estimated to be released to the general consumer in August / September 2002. Usefs will have the ability to uninstall at least the front end of Windows Media Player from their systems using the Control Panel Add / Remove programs applet. The Service Pack will also allow users to uninstall Microsoft Internet Explorers front end, Windows Messenger (Currently removable via the sysoc process) and several other previously embedded utilities.

In the mean time, if you need to use a low process dependant version of Media Player, for example if you run SETI@Home or like to listen to music while Compiling or Rendering all I can suggest is:

  1. Open Windows Media Player 8
  2. Click the Tools button in the Menu Bar, and select Options
  3. Choose the File Types tab and deselect everything except for the CD and DVD options
  4. Click OK to conrim and exit Windows Media Player 8
  5. Browse to x:\Program Files\Windows Media Player (Where x: is the System Drive)
  6. Run mplayer2.exe
  7. Click the View button in the Menu Bar, and select Options
  8. Select the Formats tab
  9. Click the Select All button
  10. Click OK to confirm, then re-start Media Player
  11. You can also point the Start Menu Shortcut to mplayer2.exe

This will default all Media File types to open in Windows Media 6.4. CD Audio, VCD and DVD disks will still open in Windows Media Player 8.

Now that we are seeing openness on the part of the Microsoft Corporation and its integrated products, where does the future lie for the Microsoft vision. This is something only time will tell, however, if Real Networks get their media player onto a Microsoft Operating system CD ever again, Microsoft can say good by to me as a customer. I personally don’t want anything to do with Real Player or their dire codecs.

UPDATE: 03 June 2002:
Microsoft are not going for Windows Media 8.1 as CNet predicted, but instead have invested their efforts on a complete overhaul of the Windows Media Suite and family of products and services in “Windows Media Services 9”

UPDATE: 11 August 2002:
The time of reckoning has finally arrived for 6.4. Here for your viewing pleasure is the new ActiveX control for Windows Media Player Content.

ActiveX Control Screenshot