Event ID 599 — Multicast Content Provider Support

Applies To: Windows Server 2008 R2

The multicast server uses a content provider to transmit the data from the server to the client. The Windows Deployment Services content provider can transfer any file over a multicast transmission; however, you can create or use a custom content provider if you want additional functionality. For example, you could create a content provider that transfers a .zip archive, a .vhd image, or a database and then extracts data out of it. The providers must be functioning properly to deploy content using multicast transmissions.


Event Details

Product: Windows Operating System
ID: 599
Source: WDSMC
Version: 6.1
Message: The Content Provider %1 returned an error while trying to open a new instance.

Configuration: %2
Error Information: %3


Ensure that the content provider configuration settings are correct

The content provider must be able to locate and open the specified content. If you are using a custom or non-Microsoft content provider, contact the vendor for troubleshooting information. Otherwise, to ensure that the content provider configuration settings are correct, do the following in the specified order:

  • Ensure that Res.rwm exists.
  • Ensure that the required registry permissions are set.
  • Ensure that there is enough memory

Ensure that Res.rwm exists

Ensure that the Res.rwm exists for the image you want to transfer over a multicast transmission. The Res.rwm file should be located at RemoteInstall\Images\<ImageGroup>. If this file does not exist, you will need to add an install image to the server. To do this, run the following command at the command prompt: WDSUTIL /Add-Image /ImageFile:<path to wim file> /ImageType:install

If the Res.rwm file exists, use the procedure in the following section to ensure that the necessary registry permissions on the server are set.

Ensure that the required registry permissions are set

Caution: Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data.

To perform this procedure, you must either be a member of the local Administrators group or have been  delegated the appropriate authority.

To ensure that the correct registry permissions are set:

  1. Open Registry Editor. (Click Start, type regedit in the Start Search box, and then press ENTER.)
  2. Make sure that the failed content provider has correct permissions to read the registry keys at the following location: HKLM\System\CurrentControlSet\Services\WDSServer\Providers\WDSMC\Providers\<content provider>. To do this, right-click the WDSServer node, click Permissions, click SYSTEM, and then make sure that Read is selected. Note: The failed content provider is specified in the event log message. To find this message, open Event Viewer, expand Custom Views, expand Server Roles, click Windows Deployment Services, and then find WDSMC event 599 or 601.

If this does not fix the issue, use the procedure in the following section to ensure that there is enough memory on the server.

Ensure that there is enough memory

To perform this procedure, you must either be a member of the local Administrators group or have been delegated the appropriate authority.

To free up memory on the server:

  1. On the Windows Deployment Services server, right-click an empty area of the taskbar, and then click Task Manager.
  2. Click the Processes tab.
  3. Make sure that the User Name and Memory (Private Working Set) columns appear. If they do not appear, click Select Columns on the View menu, select the User Name and Memory (Private Working Set) check boxes, and then click OK.
  4. At the bottom of the tab, select the Show processes from all users check box.
  5. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  6. To sort the processes by memory usage, click the Memory (Private Working Set) column heading.
  7. Determine whether it is safe to end any of the memory-intensive processes.
  8. To end a process, click the process name, and then click End Process.
  9. When prompted, click End Process again to confirm that you want to end the process.


To verify that all of your content providers are running properly:

  1. Open the Command Prompt window.
  2. At the command prompt, type sc control wdsserver 130.
  3. Confirm that the output includes entries for all of your content providers. Note that the default content provider is WDScp.dll.

Multicast Content Provider Support

Windows Deployment Services