sccm assignment enforce failed

ConfigMgr Software Updates Deployment (Assignment) & Individual Updates Compliance FAQs

Consider a deployment containing 100 updates. Now each of these 100 updates will have their own compliance state on the machine and the Deployment you can say is a collective compliance of each of them. Meaning that until all of the updates within the deployment are not deemed compliant, the Deployment itself is not compliant.

So here take an Example of a Software Update group ‘Endpoint' having a few definition updates and I have targeted the same to a collection.

Here is where you can see the Deployment compliance.

And here is where you the see the individual updates in the deployment with their compliance.

Now an important distinction to make here is that, the individual updates Compliance are available to us in the All Software Updates view and you don't have to create an Update Group or Deploy it.

How does that happen? Note that Client machines scan against the WSUS regularly on schedule and once the fresh updates are synced they get scanned for whether it is required or not on that machine and it stored in the WMI and they send the state message to the Server.

So at the time of the creation of the deployment the individual compliance at that time is already known to us. Though here on console it just shows the numbers, you can actually go to the Software Updates Scan report to find the actual machines names for a given update.

Now it is important to clear this point here that the number you see for individual updates here is not related only to the machines in the deployment but all the client in the infra which have sent the compliance for this individual update. So suppose you have 1000 client in hierarchy-

And you deployed this update to a collection of 10 machines, the numbers for individual updates here will come from all the 1000 machines. Like already mentioned that this Scan is not related to the deployment. If you want to narrow it down only for a collection you might want to use the software update reports.

Now suppose if the deployment is targeted and it finds only 3 are required to it and it installs 2 and fails to install 1. Then as a result the 2 updates which got installed correctly will change their individual compliance and even though the deployment itself will remain Non-Compliant.

The individual update status can be easily obtained from Client WMI if you know its CI_UniqueID (From console)

One more important side node about the CCM_UpdateStatus class here. Note that this class will only contain the updates which are either Missing OR Installed on the client machine. Also this class is not related to the deployment at all.

Now have a look at the Deployment or Assignment compliance on Client WMI –

Now here the GUID is the actual Deployment Unique GUID that you can obtain from the console. You can see the Deployment is itself marked as IsCompliant here on the client.

Now also try to understand what a signature is here (highlighted in green)

Now every time a deployment is modified its CRC changes, and that is when it asks the client to send the compliance again for this new changed deployment. So that is how we track it.

Now you can see it exactly matches the Signature in client WMI, If this doesn't match you know that the client did not even get the changed policy for the deployment.

And this can help narrow the actual troubleshooting for compliance to troubleshooting policy.

There are three types –

Evaluation Message – Happens when the deployment is evaluated on the client. Enforcement Message – Happens when the deadline generally hits. Compliance Message – Changes after the updates are installed from Non-Compliant to Compliant.

On top of these all the above are generated for each CI (Update) and Deployment. Needless to say the one for deployment depends on the individual CIs in it so even one CI getting into a bad state will cause the state of the deployment to be that way. E.g: One CI is the deployment being not compliant will cause the whole deployment to non-compliant.

So even the TopicType for the state messages are different for the Assignment Compliance and Individual CI compliance.

For Assignment Compliance –

Evaluation Message – Topic Type 302

Enforcement Message – Topic Type 301

Compliance Message – Topic Type 300.

And for the individual CIs it is –

Evaluation Message – Topic Type 400

Enforcement Message – Topic Type 402

Compliance Message – Topic Type 401.

For the Assignment or the deployment the place is CI_AssignmentStatus table

It has columns for all the three types of messages for the deployment which will be updated once received respectively.

It uses AssignmentID (which can be obtained from CI_CIAssignments)

So we can see all the three types of messages come to the same table and we have different section for Compliance, Enforcement and Evaluation here.

Also  types if there are enforcement errors etc and their codes should be visible here.

Now what is Enforcement Type Unknown ?

Generally the client never sends anything like that. These state simply mean the Server has not received any Enforcement message for the deployment (Hence LastEnforcementMessageID is NULL). It could be many reasons – Backlogs, Client <->MP issues etc. So if the Assignment is not Compliant (If it is already compliant we don't enforce) and we don't have the LastEnforcementMessage for the deployment then that would be deemed as Enforcement Unknown.

For the Individual Update CIs the place is Update_ComplianceStatus. All the above explanation should be valid for them as well.

Some keys to understand what message type or column value means what for Apps/Update CIs

For Eg. Enforcement state of a deployment is “Waiting for a restart” on a client but Server has not updated it?

This could happen if somehow the state message lost or if there were issues while processing the same on server. So we can ask it to resent the same again.

Note that Assignment compliance is not the same as the individual updates compliance, there are other scripts to resend the updates compliance but those topic types are different.

For this one, from the table we know EnforcementMessage category for Deployment compliance is TopicType 301. And taking the same deployment GUID {F9FAF641-7786-40F3-B074-E4CD4A35D233} as an example.

Here is a sample script to make the MessageSent to FALSE so it will resend the message in the next state message cycle.

Hope it helps!

Support Escalation Engineer   | Microsoft System Center Configuration Manager  

Disclaimer:   This posting is provided “AS IS” with no warranties and confers no rights.

This article was originally published by Microsoft's ITOps Talk Blog . You can find the original article here .

Related Posts

• Troubleshooting SDN Windows Admin Center Certificates
• The care and feeding of Azure Arc for Servers
• Step by Step Setting Up System Center Configuration Manager & ConfigMgr Client on Mac OS
• Microsoft Defender for Identity – Azure ATP Deployment and Troubleshooting
• Microsoft Defender for Cloud latest protection against sophisticated abuse of Azure VM Extensions

How to Fix SCCM Application Deployment Error 0x87d01106

When monitoring the application deployment through SCCM report, the following deployment error was logged for multiple devices.

Error description: Failed to verify the executable file is valid or to construct the associated command line

Further investigation on client machine shows below error in AppEnforce.log file.

Error in C:\Windows\ccm\logs\AppEnforce.log File :

App enforcement environment:

Context: Machine Command line: Powershell.exe -ExecutionPolicy ByPass -File MyScript.ps1 Allow user interaction: No UI mode: 0 User token: null Session Id: 4294967295 Content path: C:\WINDOWS\ccmcache\3 Working directory: Invalid executable file Powershell.exe AppProvider::EnforceApp – Failed to invoke EnforceApp on Application handler ( 0x87d01106 ).

Cause for Error 0x87d01106 

The application was trying to execute a PowerShell script. However, PowerShell.exe could not be located on client computers. The full path for Powershell.exe file was not provided in command line.

powershell.exe -ExecutionPolicy ByPass -File MyScript.ps1

PowerShell.exe path must be defined in PATH environment variable. By default, Powershell.exe path is defined in PATH environment variable however it may overwritten by other applications due to misconfiguration. Hence, the deployment will fail on the computers where Powershell.exe path does not exists in PATH environment variable.

Solution for Error 0x87d01106 

It’s better to provide the complete path for PowerShell executable in program command line. This will eliminate the dependency over PATH environment variable as PowerShell.exe can be located by the path provided with command line.

The complete path to execute PowerShell script should be like this:

%SystemRoot%\system32\WindowsPowerShell\v1.0\powershell.exe -ExecutionPolicy ByPass -File MyScript.ps1

Related Posts:

• SCCM Application Deployment Failed with Error 0x87d01106 | ConfigMgr
• SCCM Client Installation Failed With Error Code 0x87d00215
• PXE-E99: Unexpected network error – SCCM OSD
• Configuration Manager OSD task sequence fails with error  code  0x80004005
• MECM OSD Task Sequence Failed with Error 0x80072EE7
• SCCM Client Push Installation Failed with Error 0x800706ba
• Failed to Add Update Source for WUAgent of type (2) and id ({ID). Error = 0x80004005
• SCCM OSD – Domain Join Failed with Error code 0x54b on HP Elitebook 840 G8
• ccmsetup failed with error code 0x87d00227
• Fix Application Deployment error 0x87d00213 in ConfigMgr
• CMG Connection Point Status Disconnected | SCCM | ConfigMgr
• CMG Setup – Subscription ID drop down not populating
• CMG Setup – Error when granting Contributor permission to the Azure AD app
• Failed to connect with DP – Error Code 0x8004100e | ConfigMgr | SCCM
• SCCM Client Installation Failed with error 0x87d0027e
• ConfigMgr OSD – PXE Troubleshooting
• SCCM WSUS sync error – Sync Failed – WSUS server not configured
• SCCM Software Distribution Troubleshooting

Subscribe to Techuisitive Newsletter

Be the first to know about our new blog posts. Get our newsletters directly in your inbox and stay up to date about Modern Desktop Management technologies & news.

Recent Posts

Understanding sccm incremental collection , evaluation and monitoring.

Configuration Manager uses collection evaluation to update collection membership, based on the collection rules you define. Collection evaluation scope and timing differ depending on site and collection…

Read More »

How to Create , View and Organize SCCM Maintenance Windows

A Configuration Manager maintenance windows restrict the deployments on SCCM client during specified timeframe. The SCCM Maintenance Windows ensure that client configuration changes occur during…

How to Configure and Approve User Application Requests in SCCM

SCCM allows application deployment in way that it goes through approval process. Users requests the application in Software Center, and then an administrator review and…

How to Run script in SCCM without creating a package / application

Configuration Manager has an integrated ability to run PowerShell scripts. This can be used to build custom tools to perform quick actions on client machines.…

Management Point Installation Failed after SCCM 2303 Upgrade

Issue After SCCM 2303 Upgrade from 2111, the Management Point installation failed on all MPs with below error. Status Message: Site Component Manager could not…

SCCM SQL Query to list Desktop & Laptop Devices

SCCM SQL queries are great way to pull out information from SCCM database directly. As a SCCM administrator, you may encounter a situation where custom…

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members. Please post your questions in the correct category.

• Endpoint Manager
• Configuration Manager

SOLVED   SCCM deployment error 0x87D00324(-2016410844)

• Thread starter Sukhjit
• Start date Aug 8, 2019
• Aug 8, 2019

Installing the software through software center gives error code 0x87D00324(-2016410844) although installation is successful. Running the same msi manually from same location works without any error. AppEnforce.log shows below: Prepared command line: "C:\WINDOWS\system32\msiexec.exe" /x "GlobalProtect64.msi" /q AppEnforce 8/7/2019 11:53:29 AM 12076 (0x2F2C) Executing Command line: "C:\WINDOWS\system32\msiexec.exe" /x "GlobalProtect64.msi" /q with user context AppEnforce 8/7/2019 11:53:29 AM 12076 (0x2F2C) Working directory C:\WINDOWS\ccmcache\d AppEnforce 8/7/2019 11:53:29 AM 12076 (0x2F2C) Post install behavior is BasedOnExitCode AppEnforce 8/7/2019 11:53:29 AM 12076 (0x2F2C) Waiting for process 11928 to finish. Timeout = 120 minutes. AppEnforce 8/7/2019 11:53:29 AM 12076 (0x2F2C) Process 11928 terminated with exitcode: 1605 AppEnforce 8/7/2019 11:53:30 AM 12076 (0x2F2C) Looking for exit code 1605 in exit codes table... AppEnforce 8/7/2019 11:53:30 AM 12076 (0x2F2C) Unmatched exit code (1605) is considered an execution failure. AppEnforce 8/7/2019 11:53:30 AM 12076 (0x2F2C) Any ideas?  

• Aug 9, 2019

Hi error code 0x87D00324(-2016410844) is mean the application "Detection Method" don't match your software installation. Open up GlobalProtect application, click properties, go to Deployment Types, click edit, on the tabs click Detection Method, click edit, on setting type select "Windows Installer" then on the Product Code click browse look for globalprotect64.msi it will get product code. If that doesn't work maybe the product code doesn't match, On the client PC with globalProtect installed, look it up under registry "HKLM\Software\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall, it would be list of {Product Code} look in each one of them and find "Display name" GlobalProtect, copy the product code if it look different and...

Hi error code 0x87D00324(-2016410844) is mean the application "Detection Method" don't match your software installation. Open up GlobalProtect application, click properties, go to Deployment Types, click edit, on the tabs click Detection Method, click edit, on setting type select "Windows Installer" then on the Product Code click browse look for globalprotect64.msi it will get product code. If that doesn't work maybe the product code doesn't match, On the client PC with globalProtect installed, look it up under registry "HKLM\Software\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall, it would be list of {Product Code} look in each one of them and find "Display name" GlobalProtect, copy the product code if it look different and put that in Detection Method with setting type "Windows Installer". hope is helps. Rach  

Sam Banford

Well-known member.

• Aug 11, 2019

Sukhjit said: msiexec.exe" /x "GlobalProtect64.msi" /q Click to expand...

Sukhjit said: exitcode: 1605 Click to expand...

• Aug 13, 2019
• Thread Starter

Thanks for your help. It's was "Detection Method" issue. Re-creating the package again with default detection method settings resolved the issue. Love this site. Use all the time for guide, reference and troubleshooting help.  

Latest posts

• Latest: Cola123
• Today at 11:28 AM
• Latest: jackaustin
• Today at 4:23 AM
• Latest: Harshit Pandey
• Yesterday at 10:50 PM
• Latest: Bob Hatcher
• Tuesday at 9:55 PM

• Latest: Damian1984
• Tuesday at 6:05 PM

Forum statistics

Follow along with the video below to see how to install our site as a web app on your home screen.

Note: This feature may not be available in some browsers.

• This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register. By continuing to use this site, you are consenting to our use of cookies. Accept Learn more…

Fix SCCM CcmSetup Failed with Error Code 0x80080005

In this post, I will show you how to fix “ccmsetup failed with error code 0x80080005” that appears during the SCCM client installation. I will also explain what the ccmsetup error code 0x80080005 means and the steps to resolve it.

First of all, let me tell you that it is very rare that you encounter SCCM error 0x80080005 during the client agent installation. The error 0x80080005 is typically seen during the ConfigMgr client agent installation on a few computers, and luckily, there is a solution available. Also note that the error code 0x80080005 is also seen when the client agent is installed as part of a task sequence deployment.

At a remote site, while re-installing the SCCM client agent on a Windows computer, the IT engineer who was on site told me that client agent installation wasn’t working after OSD. After looking at the smsts.log and client setup logs, he found that the ccmsetup failed with error code 0x80080005.

Before you read further, here are some useful troubleshooting guides about client installation errors.

• SCCM Client Agent Install Error 0x80200010
• Fix SCCM Client Agent Installation Error code 80041002
• Fix CcmSetup failed with error code 0x80041010 in SCCM
• How To Fix ConfigMgr Client Install Error 0000052e
• SCCM Client Installation Error 00000005

Translate ccmsetup error code 0x80080005

One of the challenges in troubleshooting SCCM client installation issues finding the error code and understanding what that error code means. The fact is knowing the error code is not sufficient, you also need to find out what that error code means. Here is a useful guide that shows how to translate the SCCM error codes to error messages , debug the issue and find the actual solution.

When you translate the “ error code 0x80080005 ” using the error lookup tools in ConfigMgr, we see the message “ Server execution failed “. Although, you cannot make anything out of this error, you will have to review the ccmsetup.log in detail.

Whenever the client agent installation fails on a computer, you normally attempt to reinstall the client agent that resolves most of the common errors. However, the IT guy in the remote site uninstalled the SCCM client agent and restarted the computer. When he attempted to install the client agent back, the same error code 0x80080005 appeared in ccmsetup.log .

Fix SCCM ccmsetup failed with error code 0x80080005

Let’s look at the steps to resolve the ccmsetup error code 0x80080005. The error code 0x80080005 appears during the SCCM client agent installation due to BITS missing on client computer. As per Microsoft , BITS version 2.5 is required to enable throttled data transfers between the client computer and Configuration Manager site systems. Installing the BITS on the client computer resolves the ccmsetup error code 0x80080005.

During client agent installation, the BITS (Background Intelligent Transfer Service) isn’t downloaded automatically. Most modern client operating systems include BITS by default. But if your operating system doesn’t come with BITS, you’ll need to install it yourself before you can install the client agent.

The below screenshot was taken from a computer where the client agent installation was interrupted with error code 0x80080005. The client agent was supposed to be installed by the task sequence as a part of operating system deployment. In such cases, you must review the complete smsts.log file and ccmsetup.log and make a note of all the errors.

If the error 0x80080005 is observed during client push installation , you must always review the ccmsetup.log file located on the client computer.

After reviewing the smsts.log file , I noticed multiple errors, but one line within that log file reveals “ This operating system does not contain the correct version of BITS. BITS 2.5 or later is required “. All you need to do is install the Microsoft Background Intelligent Transfer Service ( BITS ) version 2.5 or a later on the client computer and run the client agent installation.

In some cases, even though the BITS is installed, you may encounter ccmsetup error code 0x80080005 because the BITS service is stopped or not running. When the BITS service is started, the error 0x80080005 doesn’t appear. The same solution also works when you see ccmsetup failed with error code 0x80200014 .

Sign Up For Newsletter

Join our newsletter to stay updated and receive all the top articles published on the site get the latest articles delivered straight to your inbox..

smsts.log or ccmsetup.log ?

Dear Prajwal Desai,

Please find the below logs when installing the client , for the security concern i have removed the SCCM Server name into dashes(—-)

Client IsSslClientAuthEnabled – Determining provisioning mode state failed with 80070002. Defaulting to state of 63. ccmsetup 4/19/2021 7:43:29 AM 8840 (0x2288) Failed to connect to machine policy namespace. 0x8004100e ccmsetup 4/19/2021 7:43:29 AM 8840 (0x2288) IsSslClientAuthEnabled – Determining provisioning mode state failed with 80070002. Defaulting to state of 63. ccmsetup 4/19/2021 7:43:29 AM 8840 (0x2288) Failed to get client certificate for transportation. Error 0x87d00280 ccmsetup 4/19/2021 7:43:29 AM 8840 (0x2288) Failed (0x87d00454) to send location request to ‘—–‘. StatusCode 200, StatusText ” ccmsetup 4/19/2021 7:43:29 AM 8840 (0x2288) Failed to send location message to ‘HTTPS://—–‘. Status text ” ccmsetup 4/19/2021 7:43:29 AM 8840 (0x2288) GetDPLocations failed with error 0x87d00454 ccmsetup 4/19/2021 7:43:29 AM 8840 (0x2288) Failed to get DP locations as the expected version from MP ‘HTTPS://——‘. Error 0x87d00454 ccmsetup 4/19/2021 7:43:29 AM 8840 (0x2288) Failed to find DP locations from MP ‘HTTPS://——‘ with error 0x87d00454, status code 200. Check next MP. ccmsetup 4/19/2021 7:43:29 AM 8840 (0x2288) Have already tried all MPs. Couldn’t find DP locations. ccmsetup 4/19/2021 7:43:29 AM 8840 (0x2288) IsSslClientAuthEnabled – Determining provisioning mode state failed with 80070002. Defaulting to state of 63. ccmsetup 4/19/2021 7:43:29 AM 8840 (0x2288) Failed to connect to machine policy namespace. 0x8004100e ccmsetup 4/19/2021 7:43:29 AM 8840 (0x2288) IsSslClientAuthEnabled – Determining provisioning mode state failed with 80070002. Defaulting to state of 63. ccmsetup 4/19/2021 7:43:29 AM 8840 (0x2288) Failed to get client certificate for transportation. Error 0x87d00280 ccmsetup 4/19/2021 7:43:29 AM 8840 (0x2288) DownloadFileByWinHTTP failed with a non-recoverable failure, 0x87d00454 ccmsetup 4/19/2021 7:43:29 AM 8840 (0x2288) DownloadFileByWinHTTP failed with error 0x87d00454 ccmsetup 4/19/2021 7:43:29 AM 8840 (0x2288) Failed to get client version for sending state messages. Error 0x8004100e ccmsetup 4/19/2021 7:43:29 AM 8840 (0x2288) Failed to send status 308. Error (87D00215) ccmsetup 4/19/2021 7:43:29 AM 8840 (0x2288) Failed to connect to policy namespace. Error 0x8004100e ccmsetup 4/19/2021 7:43:29 AM 6272 (0x1880) Failed to revoke client upgrade local policy. Error 0x8004100e ccmsetup 4/19/2021 7:43:29 AM 6272 (0x1880) CcmSetup failed with error code 0x87d00454 ccmsetup 4/19/2021 7:43:29 AM 6272 (0x1880)

Server Unable to connect to remote machine “—–” using Kerberos with alternate account, error – 0x800706ba. SMS_CLIENT_CONFIG_MANAGER 4/18/2021 9:53:57 AM 30564 (0x7764) Unable to connect to WMI on remote machine “——“, error = 0x80041033. SMS_CLIENT_CONFIG_MANAGER 4/18/2021 9:55:04 AM 30564 (0x7764) Unable to connect to remote machine “MAHMED” using Kerberos with machine account, error – 0x800706ba. SMS_CLIENT_CONFIG_MANAGER 4/18/2021 9:55:04 AM 30564 (0x7764) Unable to connect to WMI on remote machine “MAHMED”, error = 0x800706ba. SMS_CLIENT_CONFIG_MANAGER 4/18/2021 9:55:04 AM 30564 (0x7764) Execute query exec [sp_CP_SetLastErrorCode] 2097152117, -2147023174 SMS_CLIENT_CONFIG_MANAGER 4/18/2021 9:55:04 AM 30564 (0x7764)

Please note: Server & Client – firewall is Turn Off complete all ports are opened WMI & BITS is installed and working fine in Client & Server – restarted the services Reintall the ISS roles

Loading Software Center returned error code 0x80041001(-2147217407)

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Save my name, email, and website in this browser for the next time I comment.

PatchMyPC Sponsored AD

Recast Sponsored AD

Popular Articles

SCCM 2012 R2 Step by Step Guide

How To Deploy Software Updates Using SCCM ConfigMgr

How to Install WSUS for SCCM | SUP Role | ConfigMgr

Fix Skype for Business Recording Shows Pending Status

Recent articles.

8 Ways to Fix Windows 11 Upgrade Error 0x800F0830-0x20003

How to Enable or Disable Copilot Vision in Microsoft Edge

Manage Windows 11 Readiness dashboard using SCCM

Top 10 ConfigMgr 2403 New Features

Subscribe Newsletter

Subscribe to our newsletter to get our newest articles instantly!

This browser is no longer supported.

Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.

Application installation common error codes reference

• 5 contributors

Applications can be installed on clients by creating deployments from the Configuration Manager console or by targeting applications to tenant attached devices from the Microsoft Intune admin center . Use the information in this article to assist with troubleshooting application installation errors.

General troubleshooting tips

Generally, if an application installs successfully on a device with the given command line in the system context, it will install successfully through Configuration Manager and from the Microsoft Intune admin center. You can simulate this by using PSExec .

• Open an administrative command prompt.
• Change directory to where you saved PSExec .
• Type in psexec -accepteula -s -i cmd .
• This opens a new command prompt window running interactively in the system context. Check that you're in the system context by running a whoami command.
• Run the install from the new windows with the installation command line. For example, msiexec /i "My App.msi" /q would be a quiet install of the "My App" msi file.

You may also find that searching through multiple files for a specific string is useful. For instance, you might want to search all the client .mof files for a specific class, or you might want to search logs for a specific ID. Using a specific ID when searching can give you an understanding of how components are related to each other. Use the select-string cmdlet in those instances.

Configuration Manager errors

General configuration manager troubleshooting tips.

When an application fails to install and the error source is Configuration Manager , typically, following the application troubleshooting guide and using the general troubleshooting tips helps you resolve the error. You may also want to use Support Center for Configuration Manager to help troubleshoot and review information about your clients.

Message : Service is shutting down

Additional information for error resolution : Verify that the Configuration Manager client is running on the target device. Verify the client is running by:

• Reviewing the CCMExec.log on the device
• Verifying that the SMS Agent Host service is running on the device

Message : Parsing error

Additional information for error resolution : This error generally occurs in one of the Configuration Manager components when a piece of data is invalid. This error could stem from something missing for the application, an old package version, or a number of other general errors. Follow the application troubleshooting guide to help locate the error and resolve it. It may be necessary to review additional logs for components that support application installation. Searching for specific IDs or error codes in the logging may help you identify the problem. For more information, see general troubleshooting tips .

Message : Timeout occurred

Additional information for error resolution : Increase the Maximum allowed run time (minutes) for the application. Ensure that the maintenance window on the client is large enough to support the runtime. For more information, see the application troubleshooting guide to help resolve the error.

Message : Item not found

Additional information for error resolution : Verify that the following exist and are accessible to the client:

• The application deployment exists and the client sees the policy.
• The application content exists and is available to the client

For more information, see the application troubleshooting guide to help resolve the error.

Message : Syntax error occurred while parsing

Message : The object or subsystem has not been initialized

Message : CI documents download timed out

Additional information for error resolution : The CI documents activity can be tracked in CIAgent.log , CIDownloader.log , and DataTransferService.log . For more information, see the CI Agent section of the application troubleshooting guide.

Message : Failed to decompress CI documents

Message : CI Version Info timed out

Additional information for error resolution : Typically this error occurs when a change was made to the application and the client doesn't have the new information for it. Verify that the client is getting the policy and it knows about any updated revisions to the application.

Message : The script execution has timed out

Additional information for error resolution : Check the AppEnforce.log for details. You may need to increase the Maximum allowed run time (minutes) for the application. Ensure that the maintenance window on the client is large enough to support the run time. For more information, see the application troubleshooting guide to help resolve the error.

Message : The application was not detected after installation completed

Additional information for error resolution : Review the AppDiscovery.log and the CIAgent.log . Once an installation is completed, the application detection is used again to verify the installation .

Message : Application was still detected after uninstall completed

Additional information for error resolution : Verify the correct uninstall command was used in the AppEnforce.log . Review the AppDiscovery.log and the CIAgent.log . Once an uninstall is completed, the application detection is used again to verify the uninstall .

Message : Script is not signed

Additional information for error resolution : Verify the PowerShell execution policy client setting for the device. The default for this client setting is AllSigned so an unsigned script will cause a failure.

Message : Application requirement evaluation or detection failed

Additional information for error resolution : Review the AppIntentEval.log to discover dependencies and supersedence rules for the application and their states. For more information, see Application deployment evaluation .

Message : Content not found

Additional information for error resolution : Verify the content for the application is on a distribution point and that the distribution point is accessible to the client. For more information, see Application download in Configuration Manager .

Message : No current or future service window exists to install software updates

Additional information for error resolution : Ensure that the maintenance window on the client is large enough to support the Maximum allowed run time (minutes) for the application installation and that the client has received the policy for the window.

Message : Failed to verify the executable file is valid or to construct the associated command line

Additional information for error resolution : Verify that the executable file is installable on its own then verify it's installable with the given command line.

Message : Failed to access all the provided program locations. This program may retry if the maximum retry count has not been reached

Additional information for error resolution : The client is getting locations for the content, but can't reach the locations. Review the client's LocationServices.log for the Distribution Point= . Use ContentTransferManager.log and DataTransferService.log to monitor the download for errors.

Message : The content download cannot be performed because there is not enough available space in cache or the disk is full

Additional information for error resolution : Check that the machine has enough space on the drive. Compare the size of the ccmcache directory with the client cache settings and ensure the setting is adequate for the application's size.

Message : The content download cannot be performed because the total size of the client cache is smaller than the size of the requested content

Additional information for error resolution : Compare the size of the ccmcache directory with the client cache settings and ensure the setting is adequate for the application's size.

Message : A supported App-V client is not installed

Additional information for error resolution : Verify that a supported version of App-V is installed on the client.

Message : The App-V sftmime command returned failure

Additional information for error resolution : For information on sftmime commands, see Manage Virtual Applications by Using the Command Line .

Message : An error occurred when querying the App-V WMI provider

Additional information for error resolution : For information on the App-V WMI provider, see Application Virtualization Client WMI Provider .

Message : Error Unknown

Additional information for error resolution : Follow the application troubleshooting guide to help locate the error and resolve it. It may be necessary to review additional logs for components that support application installation. Searching for specific IDs or error codes in the logging may help you identify the problem. For more information, see general troubleshooting tips .

Message : Application was successfully installed

Additional information for error resolution : The application was successfully installed.

General MSI troubleshooting tips

When errors are encountered from MSI, typically you'll need to Enable Windows Installer logging . After the logging is enabled, you can retry the problem installation and Windows Installer will track the progress and post it to the %temp% folder. The new log's file name is random. However, the first letters are Msi and the file name has a .log extension.

The MsiExec.exe and InstMsi.exe Error Messages and Windows Installer Action Return Values lists are useful when reviewing a Windows Installer log as are the general troubleshooting tips .

Message : User cancel installation

Additional information for error resolution : The installation was canceled by the user. Ask the user to install the application fully. If possible, you can attempt to run the installation for the system rather than the user.

Message : Fatal error during installation

Additional information for error resolution : Enable Windows Installer logging and run the install again. When reviewing the installer log, typically an entry stating Return value 3 is located near the failure reason in the log. For more information on possible return values and their meaning, see Windows Installer Action Return Values .

Message : This action is only valid for products that are currently installed

Additional information for error resolution : Ensure that the product is installed before running a dependant install.

Message : Another program is being installed. Please wait until that installation is complete, and then try installing this software again

Additional information for error resolution : Wait for the prior installation to complete before running a new one. If the prior installation stops responding, you can attempt to stop the installation or terminate the process. Terminating a process might have undesired results.

Message : This installation package is not supported by this processor type. Contact your product vendor

Additional information for error resolution : Ensure that the device's processor architecture is appropriate for the software. Verify the target device meets or exceeds the minimum processor requirement for the application. Contact the product vendor if the device's processor meets the product's processor support specifications.

Message : Another version of this product is already installed. Installation of this version cannot continue. To configure or remove the existing version of this product, use Add/Remove Programs on the Control Panel

Additional information for error resolution : Uninstall the the unwanted version of the product. If you aren't using Configuration Manager, a script, or another management tool to uninstall, uninstall from the device manually. For Windows 10 or later clients, use Windows Settings > Apps to uninstall the unwanted version of the product. For earlier versions of Windows, use Programs and Features from the Control Panel to uninstall the unwanted version of the product.

Message : The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade patch

Additional information for error resolution : Verify the device meets the product versioning prerequisites for the installation.

Windows errors

General windows troubleshooting tips.

Use the Windows system error codes list or Download the Microsoft Error Lookup Tool for looking up additional codes that aren't listed in this article. Using the Windows event logs and the general troubleshooting tips can also help identify the cause of these errors.

Message : Incorrect function

Additional information for error resolution : Review the Windows event logs around the time of the failure in combination with the installation logs to determine the possible cause of the error.

Message : The system cannot find the file specified

Additional information for error resolution :

• If the missing file is a system file, run the System File Checker tool to repair missing or corrupted system files . You can also use /scanfile=file or /verifyfile with the sfc command to scan the binary and check if there is any issue with that file.
• If the missing file is an application file, you can repair or uninstall and reinstall the application to replace the missing file.
• You can launch Process Monitor without capturing events and filters by using ProcMon.exe /NoConnect /NoFilter /AcceptEULA

Message : Debugger terminated process

Additional information for error resolution : Detach any debuggers attached to the process and retry the application installation.

Message : One or more arguments are invalid

0x80000007L

Message : Operation aborted

Additional information for error resolution : Use the installation logs and Configuration Manager application logs to determine why installation stopped. Merge the logs so you can easily review what happened before the 0x80000007L error. Use eventvwr.msc to review the Windows event logs for additional events that occurred around the time of the installation failure.

Message : General access denied error

Additional information for error resolution : If the issue isn't clear from the logs, using eventvwr.msc to review Windows event logs and Process Monitor can help identify problematic files or processes. If needed, use the Windows user interface or icacls to modify permissions on the problematic file.

Additional tips for file permissions in Windows operating systems:

• Deny permissions always take precedence over Allow permissions.
• Explicit permissions take precedence over inherited permissions.
• If NTFS permissions conflict, or example, if group and user permissions are contradictory, the most liberal permissions take precedence.
• Permissions are cumulative.

Message : Unspecified error

Additional information for error resolution : Use the installation logs and Configuration Manager application logs to determine why installation stopped. Merge the logs so you can easily review what happened before the 0x80004005 error. Use eventvwr.msc to review the Windows event logs for additional events that occurred around the time of the installation failure. Follow the application troubleshooting guide to help resolve the error. Process Monitor can also help identify the failure.

Message : Catastrophic failure

Message : Class not registered

Additional information for error resolution : This is typically a configuration-related DCOM error. Review DCOM configuration settings using dcomconfig . If there's a problematic .dll file, you can use regsvr32 to register the dll file and try the install again. A large number of problematic files could be a sign of an underlying issue that needs to be resolved before you can install the application.

Message : The hash value is not correct

Additional information for error resolution : The hash of a file isn't correct and the installation can't complete. Typically you will see this error in the CAS.log . Check to see if file contents for the application were recently updated. There may be an issue with the package, in some cases you may need to rebuild and redistribute it. This issue can also happen if there is a sharing violation on a file, such as a security application scanning the file. Configuration Manager expects exclusive access to the file during a hash check. You can identify the problematic process by running a Process Monitor and adding a filter. The condition to be met is if the Result contains Sharing Violation then Include the event.

Message : Initialization of the dynamic link library failed. The process is terminating abnormally

Additional information for error resolution : If there is a problematic .dll file, you can use regsvr32 to register the dll file and try again. A large number of problematic files could be a sign of an underlying issue that needs to be resolved before you can install the application.

Windows Management Instrumentation (WMI) errors

General wmi troubleshooting tips.

Problematic namespaces can typically be found in the Configuration Manager log files and the WMI logging . WMI relies on Component Object Model (COM)/Distributed Component Object Model (DCOM), the registry, the file system, and Remote Procedure Call (RPC). DCOM registrations and permissions are critical for WMI operations to be successful. You can review DCOM configuration settings using dcomconfig .

When troubleshooting WMI problems, typically you start by verifying that the needed namespaces, classes, and instances exists in the WMI repository and can be accessed.

Verify the namespace exists on the target first by running wmimgmt.msc from an elevated command prompt. When WMI Control launches:

• Select Action then Properties .
• Select the Security tab to see all the namespaces.
• Navigate to the namespace in question.
• Verify the namespace exists and review the security on the namespace.

To connect WMI Control to another computer:

• Select Action then Connect to another computer .
• Select the option for Another computer: then supply the name.
• Select Properties to connect. The connection to the WMI repository on the remote computer doesn't occur until you select Properties .
• You may also wish to try to connect with the IP address too to verify that you can connect.

Verify the namespace exists on the target and that you can query it properly. Run the Windows Management Instrument Tester from an elevated command prompt by typing in wbemtest . When the Windows Management Instrument Tester launches:

• Select Connect...
• Type in the problematic namespace such as root\cimv2 or root\ccm and user credentials if needed. To connect to another machine, supply the name or the IP address such as \\Machine1\root\ccm and credentials if needed.
• Select Enum Classes... to verify you get classes listed for the problematic namespace.
• Set the superclass info to Recursive and select OK to verify classes list for the problematic namespace.
• If you're using the root\ccm namespace, select a class that starts with "CCM_" such as CCM_ClientIdentificationInformation.
• If you're using root\cimv2 , choose one that starts with "Win32_" such as Win32_BIOS.
• Select Instances to verify the instances of the selected class load. For some classes, it's ok if there aren't any instances, just make sure that the Query Result window states Done . Long running queries to list of instances or queries that never finish may indicate a problem.

Verify the repository:

• From an elevated command prompt, run winmgmt /verifyrepository . Verifying is typically useful for invalid class errors especially if you had to recently recompile a .mof file using mofcomp .
• If problems are found during verification, you can try to salvage using winmgmt /salvagerepository
• Typically, you won't use /resetrepository unless it's truly needed an no other alternative exists. Some namespaces won't automatically rebuild and you'll need to either reinstall the software associated with the missing namespace or mofcomp the application's .mof files to rebuild them.

WMI resources:

• Introduction to wbemtest
• Winmgmt service
• WMI Log Files
• Ensure you change the default log size to cover your troubleshooting session.
• Once you have finished troubleshooting, remember to disable the trace and debug logging.
• Setting namespace security with the WMI Control
• WMI troubleshooting
• Ask The Performance Team: WMI

Message : WBEM_E_FAILED

Additional information for error resolution : WBEM_E_FAILED is a generic WMI failure error. The error can be caused by a number of things. The error will sometimes tell you which method or instance failed. You'll probably also see related log entires around the same time if you merge logs together based on similar function. For instance, if you see the error related to content for an application, you may want to merge together CAS.log, ContentTransferManager.log and DataTransfer.log. If the error happened on a site server not a client, you may want to review SMSProv.log for additional information. Use the General WMI troubleshooting tips to help identify the issue along with the application installation logs.

Message : WBEM_E_NOT_AVAILABLE

Additional information for error resolution : The resource, in many cases a remote machine, isn't currently available. Verify the device is online. Use the General WMI troubleshooting tips to help verify connectivity to WMI on the device.

Message : WBEM_E_INVALID_NAMESPACE

Additional information for error resolution : The namespace specified could not be found. Verify the target computer can connect to WMI by following the General WMI troubleshooting tips . Verify namespace specified exists.

Windows Update Agent errors

General windows update agent troubleshooting tips.

The errors for the installation originated from the Windows Update Agent. In many cases, you can attempt to install these updates using the built-in software update management from Configuration Manager, Windows Update for Business, or Microsoft Update. In certain circumstances where it's not feasible to use your regular patching mechanism, the .msu package can be installed with the Windows Update Standalone Installer (wusa.exe) like an application. Use the Windows Update logging and general troubleshooting tips to help determine the cause of the issue.

Message : The update to be installed is already installed on the system

Additional information for error resolution : The update is already installed on the device.

Message : Operation was not performed because there are no applicable updates

Additional information for error resolution : The update isn't applicable to the device. Verify that the device meets the requirements of the update. In cases where a superseding update has been installed, it's very rare that the superseded update would be applicable to the device.

Was this page helpful?

Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback .

Submit and view feedback for

Additional resources