| Event Id | 592 |
| Source | WDSMC |
| Description | An error occurred while trying to load the module %1 for Content Provider %2. Error Information: %3 |
| Event Information | According to Microsoft : Cause : This event is logged when trying to load the module for content provider. Resolution : Ensure that the ProviderDLL registry key points to the correct file To resolve this issue, do the following in the specified order: a)Ensure that the registry data is correct. b)Reinstall Windows Deployment Services. Note: To perform these procedures, you must either be a member of the local Administrators group or have been delegated the appropriate authority. Ensure that the registry data is correct Caution : Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data. To ensure that the registry data is correct: 1.Open Registry Editor. (ClickStart, typeregedit in theStart Search box, and then press ENTER.) 2.Ensure that the registry key for the provider that failed exists in the following location:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\ 3.If the registry key exists in the specified location, do the following: a)Ensure that theProviderDll subkey exists and contains a path to the .dll file. b)Ensure that the .dll file exists at that same location. For example, the ProviderDll key for the Windows Deployment Services content provider (WDSCP) is systemroot%\system32\wdscp.dll. c)Ensure that the content provider has the necessary permissions to read the registry keys at the following location: HKLM\System\CurrentControlSet\Services\WDSServer\Providers\WDSMC\Providers\ d)If all of this information is correct, restart the WDSServer service (in theCommand Prompt window, runnet stop wdsserver and then run net start wdsserver). 4.If the provider key, the ProviderDll subkey, or the file is missing, do one of the following: a)If the provider is the Windows Deployment Services content provider (WDSMC), you will need to reinstall Windows Deployment Services by using Server Manager b)If the provider is a custom or non-Microsoft provider, reinstall it. Reinstall Windows Deployment Services To reinstall Windows Deployment Services: 1.OpenServer Manager (ClickStart, point toAdministrative Tools, and then click Server Manager.) 2.UnderRoles Summary, clickRemove Roles. 3.ClickWindows Deployment Services, and then follow the instructions in the wizard. 4.After the role removal is completed, clickAdd Roles in Server Manager to reinstall Windows Deployment Services. Verify : 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. |
| Reference Links | Event ID 592 from Source WDSMC |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.