Installing a Configuration Manager client fails with "There was a problem starting PolicyAgentProvider.dll The specified module could not be found"

Applies to: Microsoft System Center Configuration Manager 2007System Center Configuration Manager 2007 R2Microsoft System Center Configuration Manager 2007 R3 More


When installing the System Center Configuration Manager (ConfigMgr) client, the process fails with the following error:

There was a problem starting PolicyAgentProvider.dll The specified module could not be found

You may also see the following in the ccmsetup.log after clicking OK on the error above:

MSI: Action 11:53:11: CcmRegisterWmiMofFile. Registering WMI settings
MSI: Setup failed due to unexpected circumstances
The error code is 80004005 
MSI: Action 13:01:48: Rollback. Rolling back action: 
Installation failed with error code 1603


This can occur if the value of CWDIllegalInDllSearch in the Registry is set to 0xFFFFFFFF per the following Knowledge Base article:

KB2264107 - A new CWDIllegalInDllSearch registry entry is available to control the DLL search path algorithm (


There are two resolutions to this issue:

1. Remove the CWDIllegalInDllSearch entry or change this to a different value.

2. Add the full path to the CCM folder to the environmental variables PATH:

C:\Windows\SysWOW64\CCM or C:\Windows\system32\CCM depending on the architecture of the OS the client is being installed on.

More Information

CcmSetup is running the following command when this failure occurs:

rundll32.exe PolicyAgentProvider.dll,setup_checknamespaces

If CWDIllegalInDllSearch has been configured to 0xFFFFFFFF then rundll32.exe is unable to find the PolicyAgentProvider.dll when running in the current working directory.