Unable to start DSC Configuration (HRESULT 0x80041033)

I’m quite new to DSC. I’m able to create mof files after that in push mode by starting Start-DSCConfiguration cmdlet i’m getting this error.

 PS C:\> Start-DscConfiguration -Path 'c:\' -Wait -Force -ComputerName LocalHost -Verbose
VERBOSE: Perform operation 'Invoke CimMethod' with following parameters, ''methodName' = SendConfigurationApply,'className' = MSFT_DSCLocalConfiguratio
nManager,'namespaceName' = root/Microsoft/Windows/DesiredStateConfiguration'.
VERBOSE: An LCM method call arrived from computer DHANUSH-PC with user sid S-1-5-21-2953993634-1734277334-2268608716-1001.
VERBOSE: [DHANUSH-PC]: LCM:  [ Start  Set      ]
The WS-Management service cannot process the request. The WMI service or the WMI provider returned an unknown error: HRESULT 0x80041033 
    + CategoryInfo          : ResourceUnavailable: (root/Microsoft/...gurationManager:String) [], CimException
    + FullyQualifiedErrorId : HRESULT 0x80041033
    + PSComputerName        : LocalHost
VERBOSE: Operation 'Invoke CimMethod' complete.
VERBOSE: Time taken for configuration job to complete is 2.515 seconds

My DSC code is

configuration ConfigName {
    Node $ComputerName {

        WindowsFeature IIS{
            Name = 'web-server'
            Ensure = 'Absent'
$computername = 'LocalHost'
ConfigName -OutputPath c:\

Iam not able to do any kind of DSC tasks because of this error. Even for empty ones. Please help me on this


Have you started the PS console as administrator?

Best regards,

Yes, the console is in elevated mode.

hmm what OS is the computer your running this on ?

This error generally indicates that LCM failed to initialize. LCM will try to initialize by doing the following:

  1. Load all files under system32\configuration folder. This contains LCM core files and File provider.
  2. Load all files under Program Files\WindowsPowerShell\Configuration folder.

Most likely LCM failed to load some of these files either due to access issue or there are some extra files that are not supposed to be there. Try to compare these folder from a working machine. Also check event etw for any additional log.