imageHere’s a new Knowledge Base article we published. This one talks about an issue where Security Update MS10-019 may not visible in the Configuration Manager console for some operating systems.

=====

Symptoms

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

Cause

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 (http://support.microsoft.com/kb/2264107)

Resolution

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.

=====

For the most current version of this article please see the following:

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

J.C. Hornbeck | System Center & Security Knowledge Engineer

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

App-V Team blog: http://blogs.technet.com/appv/
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: http://blogs.technet.com/momteam/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/

The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/