In this post, I will show you how to fix SCCM application install error 0x87D00324(-2016410844). The software change returned error code 0x87D00324 (-2016410844).
When you deploy applications or packages using SCCM, sometimes the applications may fail to install it on client computers. Sometimes they install correctly but show an error code like 0x87D00324 which is a common issue.
When you see an application fails to install with error, the software center shows the error code that is important for troubleshooting the application installation issues. In addition to that, do not forget to review the ConfigMgr log files as well.
In this blog, I have covered numerous posts on creating and deploying applications using Configuration Manager. This includes creation of both .exe and .msi applications.
Every application has a different detection method, install commands, uninstall commands and the overall way you deploy it.
In most cases, when the application installation fails, it fails with an error code that is seen in the software center. More details about the error code and installation failures should also be logged in AppEnforce.log file located on the client computer.
One such example is the error code 0x87D00324 (-2016410844) that appears in the software center when you install the SCCM application. Let’s see why you encounter the error code 0x87D00324 and how to fix this error permanently.
First let’s understand why you get the SCCM application install error 0x87D00324(-2016410844). The error code 0x87D00324 means the application installed successfully, but there was wrong detection method used.
If you are seeing the software change returned error code 0x87D00324 (-2016410844) in SCCM software center, the issue is surely with the detection method that you have used. Correcting the detection method under application properties resolves this issue.
I have seen many people reporting the application deployment error 0X87D00324(-2016410844) in forums. If you have not joined the forums yet, feel free to be a part of the community.
The simple solution to this issue is to have a check on the application detection method which is usually specified incorrectly. For example, you may specify a wrong version number for an application or an incorrect registry path.
Why you don’t encounter error code 0x87D00324 with MSI Applications
When you use an .MSI based installer, the SCCM can read the .msi file and populates the install and uninstall commands. A valid detection method is also populated which is another advantage of using msi applications.
With MSI applications, the chances of the application install failing with error code 0x87D00324 is too minimal. However not all applications are available in .msi format.
While packaging the executable applications (.exe) in SCCM, you have to manually specify the install program, uninstall program and detection method.
The silent install and uninstall commands are usually available online however the detection method should be specified correctly.
Ok, now that you know why you get the application install error 0x87D00324, let me quickly show you how to correct the detection method for an SCCM application.
Whenever you want to modify the detection method of an application in SCCM, it has to be done under the application properties.
I am just picking up one application to show you how can you correct or modify the detection method. In the ConfigMgr console, go to the Software Library\Overview\Application Management\Applications.
Select the application and click Deployment Properties. Right-click the application and select Properties. Click the Detection Method tab, select the detection method that you have specified and click Edit Clause. On the Detection Rule window, you can correct the detection method.
Important – After you make changes to the application detection method, you must update the application content. To accomplish that, select the application first and then select the deployment types tab. Right-click the application and select Update Content.
After you correct the detection method, update the content, go back to the client computer. Now you shouldn’t see The software change returned error 0x87D00324(-2016410844). This is how you fix SCCM application install error 0x87D00324(-2016410844).
Prajwal Desai is a Microsoft MVP in Intune and SCCM. He writes articles on SCCM, Intune, Windows 365, Azure, Windows Server, Windows 11, WordPress and other topics, with the goal of providing people with useful information.
- Remove From My Forums
-
Вопрос
-
устанавливаю приложение – сценарий BAT (распаковка архива в папку %userprofile%\ПАПКА111)
я указываю в методе обнаружения папку. путь %userprofile%. имя папки ПАПКА111
сценарий отрабатывает, приложение развертывается, но выдается ошибка проверки установкиесли я разверну как пакет, то ошибка не появляется. но мне интересно развернуть как приложение
Ответы
-
я развертываю на группу пользователей.
как быть тогда? сделать папку в корне c:\ ?
режим установки на пользователя. только после входа пользователя
В этом случае вам надо использовать скрипт в detection method, например PS:
Test-Path (Join-Path $env:USERPROFILE 'ПАПКА111')
Подробнее можно почитать например здесь: SCCM; Applications; Detection Method; User Environment variables;
Грамотная постановка вопроса – уже 50% решения.
SCCM User Group Russia на FaceBook и
в Telegram- Помечено в качестве ответа
4 мая 2018 г. 11:43
- Помечено в качестве ответа
-
я прописал по вашему совету, но почему-то сейчас установка не производится, а в мониторинге пишется, что развертывание успешно. нужной директории в профиле пользователя нет.
Да, мой косяк…
Поменяйте на:
if (Test-Path (Join-Path $env:USERPROFILE 'ПАПКА111')) {$true}
Грамотная постановка вопроса – уже 50% решения.
SCCM User Group Russia на FaceBook и
в Telegram- Помечено в качестве ответа
aalyam
4 мая 2018 г. 20:15
- Помечено в качестве ответа
-
mitushinem
- Завсегдатай
- Сообщения: 25
- Зарегистрирован: 20 сен 2013 04:07
- Откуда: Смоленск
- Контактная информация:
Проблема при установке ПО через Application Catalog
Есть проблема с установкой любого ПО через Application Catalog.
После запуска на установку вроде бы как все проходит нормально и программы устанавливаются, но выдается ошибка установки (код ошибки 0x87d00324 2016410844).
Правила проверки настраиваю по пути до запускаемого файла. При повторном запуске уже говорит что программа установлена, ну это и логично.
Все разворачивается для категории Все пользователи, режим установки – для системы.
Но если приложение удалить, то потом оно становится хорошо
Буду пробовать назначить на устройство, хотя не уверен что это что-то изменит
Спасибо!
-
Виталий Якоб
- Администратор сайта
- Сообщения: 36
- Зарегистрирован: 19 сен 2013 09:52
Re: Проблема при установке ПО через Application Catalog
Сообщение
Виталий Якоб »
mitushinem писал(а):
Правила проверки настраиваю по пути до запускаемого файла. При повторном запуске уже говорит что программа установлена, ну это и логично.
Не очень удачный выбор метода обнаружения. Кто-то может установить ПО в какой-то другой каталог, с точки зрения системы ПО будет установлено, с CM — нет. Выйдет подобная коллизия и если мне не изменяет память, CM будет пробовать развернуть задачу 1004 раза.
В данном случае, установка производится с MSI пакета, поэтому лучший метод обнаружения будет “Установщик Windows” с кодом продукта.
Такая ошибка сто процентов возникает у Вас и при обязательном развёртывании, либо на x86 либо на x64 системах.
-
Виталий Якоб
- Администратор сайта
- Сообщения: 36
- Зарегистрирован: 19 сен 2013 09:52
Re: Проблема при установке ПО через Application Catalog
Сообщение
Виталий Якоб »
Обнаружение программ установленных через различные инсталляторы завёрнутые в EXE мы делаем через реестр:
Обнаружение настраивается на существование ключа реестра. Необходимо настраивать обнаружение для двух типов систем, x64 и x86.
Пример для обнаружения Mozilla FireFox 15
X86
Код: Выделить всё
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Mozilla Firefox 15.0.1 (x86 ru)
X64
Код: Выделить всё
HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\Mozilla Firefox 15.0.1 (x86 ru)
-
alyam
- Сообщения: 2
- Зарегистрирован: 08 мар 2017 07:25
Re: Проблема при установке ПО через Application Catalog
Сообщение
alyam »
здрасьте!
а как быть, если устанавливаешь приложение – сценарий BAT (распаковка архива в папку %userprofile%\ПАПКА111)
я указываю в методе обнаружения папку. путь %userprofile%. имя папки ПАПКА111
сценарий отрабатывает, приложение развертывается, но выдается ошибка проверки установки
What Causes Error 0X87D00324 During SCCM Deployment? This error code means that the application was installed, but it couldn’t be detected by SCCM. Usually, a faulty or incorrect detection method is set in the application you are deploying.
What is Windows Update error code 0x87D00324 (- 2016410844?
0x87D00324(-2016410844)
The software package installed successfully, but a software detection rule was not found. You can verify the install by checking logs at %windir%tempcu_install_software name. log. This can indicate a problem with the install even if the install reported success.
What is error code 0x87D00325 on Windows 10 install?
ERROR: Installation Failed ( error code 0x87D00325 )
This is triggered by an application not uninstalling correctly. FIX: Try uninstalling again if the option is available.
What is 0x87D00664 Windows Update error?
0x87D00664 – This error code indicates install time for the update exceeded the current maximum run time. We have increased the patch runtime for 8 hours (480 min) but however its failed.
How do I get rid of Windows Update error?
If you’ve recently installed a Windows update and you are having a problem, here’s how to uninstall the update to try to resolve the issue:
- Select Start > Settings > Windows Update > Update history > Uninstall updates . …
- On the list that appears, locate the update you want to remove, and then select Uninstall next to it.
Installing a package using SCCM fails with error 0x87D00324(-2016410844) but package is not…
How do I clear Windows Update error?
How to Fix Update Error
- Restart the Computer and Run Windows Update Again. …
- Check for Driver or Hardware Conflict. …
- Vacate Space on Your Drive. …
- Try the Windows Update Troubleshooter Tool. …
- Stop Updates. …
- Erase Software Distribution Log. …
- Download the Latest Feature Update from Microsoft. …
- Run the System File Checker (SFC) Scan.
What is install error code 0X87D00324?
What Causes Error 0X87D00324 During SCCM Deployment? This error code means that the application was installed, but it couldn’t be detected by SCCM. Usually, a faulty or incorrect detection method is set in the application you are deploying.
How do I fix Windows 10 Cannot install?
- Make sure that your device has enough space. …
- Run Windows Update a few times. …
- Check third-party drivers and download any updates. …
- Unplug extra hardware. …
- Check Device Manager for errors. …
- Remove third-party security software. …
- Repair hard-drive errors. …
- Do a clean restart into Windows.
What is error code for Windows Cannot install?
Usually you can easily figure out that the 0x80070570 error is caused by damaged Windows files. Often, you start to get the error immediately after reinstalling or updating an operating system. If you reinstall the OS, your solution is to write the boot file once again.
What is 0x80244007 error when Windows tries to scan for updates on a WSUS server?
This issue occurs when the number of updates to be synchronized exceeds the maximum number of installed prerequisites that a WSUS client can pass to SyncUpdates .
What is window update error 0x80240438?
Update error 0x80240438 typically occur when the security programs in the system block the updates, considering them a threat falsely. This issue can occur with both the Windows Firewall and third-party antivirus solutions.
What does Windows Update client failed to detect with error 0x8024402?
This error could arise due to an invalid network setting, LAN setting, or update setting that does not match the update requirements. It can be prevented by authorizing the Automatically detect connection settings.
What causes Windows stop code error?
However, various studies indicate that stop errors usually aren’t caused by Microsoft Windows components. Instead, these errors are related to malfunctioning hardware drivers or drivers that are installed by third-party software. These drivers include video cards, wireless network cards, security programs, and so on.
How do I force install a program in Windows 10?
Procedure:
- Open Settings.
- Click on Update & security.
- Click on For developers on the left panel.
- Switch on Install apps from any source including loose files option.
- Click Yes to confirm the risks involved in running an app outside the Windows Store.
- Restart your computer if applicable to complete the task.
How to fix the upgrade patch cannot be installed by the Windows installer?
The author of this answer has requested the removal of this content.
Why does Windows 10 upgrade keep failing?
The most common upgrade errors can be traced to a handful of basic causes: software incompatibilities, storage-related issues, and errors in the Setup wizard. Even if you don’t know the exact reason for an upgrade problem, you might be able to resolve it with some simple troubleshooting measures.
Why is Windows Update not installing?
Add Disk Space
Windows won’t be able to install updates if your computer does not have enough disk space. Consider adding more space if there’s no more room in your hard drive for a system update. As an alternative, you can also perform disk cleanup. Search for the Disk Cleanup utility and run the program.
Why does my Windows Update keep failing?
There’s a possibility that your system files were corrupted or deleted recently, which causes Windows Update to fail. Outdated drivers. Drivers are needed to handle components that don’t natively come with Windows 10 compatibility such as graphic cards, network cards, and so on.
What is 0x8700324 (- 2016410844?
The error code 0x87D00324 means the application installed successfully, but there was wrong detection method used. What is this? If you are seeing the software change returned error code 0x87D00324 (-2016410844) in SCCM software center, the issue is surely with the detection method that you have used.
What is software Center error code 0x87d00315?
The 0x87d00315 error code translates to “The CI version info data is not available.” ExecuteApplicationQuery – Failed to get machine targeted applications (0x87d00315). Client computers may unexpectedly receive a software update deployment if the target collection is changed from “All Systems” to another collection.
What does Windows failed to install the following update with error 0x80240020?
Description. This failure occurs because there is an application or driver currently installed that is not compatible with the feature update.
What command fixes Windows errors?
In the command prompt window, type SFC /scannow and press Enter . System file checker utility checks the integrity of Windows system files and repairs them if required.
How to hard reset my PC?
Ways to reset a desktop PC
- Click the power button, then hold down Shift while choosing Restart. This opens the recovery menu. This works even if you’re not logged into Windows.
- Click Troubleshoot.
- Select either Refresh your PC to repair the PC, or Reset your PC to prepare the PC for another user.
How do I fix the Windows 10 repair code?
Basic Fixes for Stop Code Errors
- Restart Your Computer. The first fix is the easiest and most obvious: restarting your computer. …
- Run SFC and CHKDSK. SFC and CHKDSK are Windows system utilities you can use to fix a corrupt file system. …
- Update Windows 10.
What is 0x8024402c Windows features?
Error code 0x8024402c means WU_E_PT_WINHTTP_NAME_NOT_RESOLVED – The proxy server or target server name cannot be resolved. Windows wants to download files from the Internet to activate the feature, but cannot.
SCCM is one of the best tools for deploying applications and updates on a large scale. But as good as it is, occasionally, you may still face deployment issues such as the 0X87D00324 error.
This error code, specifically, means that the application was installed, but it couldn’t be detected by the configuration manager. As for why this happens, in most cases, either the detection method or the values in use are incorrect.
Validating these will resolve this error for most users, but there are a few other solutions you can try as well. We’ve listed the steps to apply all these in the guide below.
Table of Contents
What Causes Error 0X87D00324 During SCCM Deployment?
The 0X87D00324 error occurs due to the use of an incorrect detection method during SCCM deployment. In rare cases, you may encounter this error despite using the correct detection method if there are other issues relating to command synchronicity or network access.
Since an incorrect detection method causes this error in most cases, validating it and ensuring all the values are correct will resolve this error most of the time. You’ll find all the necessary details regarding this in the sections below.
Validate the Detection Method
The Configuration Manager detects an application by verifying its GUID (Unique Application Identifier) from the registry. If the verification fails due to an incorrect path or wrong GUID, or any other reason, the detection fails, and error 0X87D00324 is returned. The steps to resolve these issues are listed below:
- In the ConfigMgr console, navigate to Software Library > Overview > Application Management > Applications.
- Select an application and click Deployment Types or Deployment Properties.
- Right-click the application and select Properties.
- In the MSI file properties window, switch to the Detection Method tab.
- Select the specified detection method and click on Edit or Edit Clause.
- In the Detection Rule window, select Windows Installer as the setting type.
- Verify that the listed product code is correct by checking the registry entry on the client machine. The registry path is:
32 bit:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\
64 bit:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
- The list of keys in curly brackets {} are the product codes for various programs. Select one of them and check the Display Name. Repeat this until you find the program you’re trying to install.
- Once you find that, verify that the GUID matches with the product code used in the Detection Clause.
Even after the detection clause is corrected, you may still encounter this error. This is likely because ConfigMgr uses binary differential replication (BDR). Basically, it only resends new or changed content instead of sending all the source files to minimize network bandwidth usage. You can easily fix this issue by refreshing the deployment with the following steps:
- Open the Configuration Manager properties on the client computer.
- Run the Machine Policy Request and Evaluation Cycle in the Action tab.
- Once the new policy is received, the deployment will work, and the application will install without any errors.
Add Delay to Detection
Some installers can spawn a child process to perform the actual installation. If the initial process exits but the installation isn’t complete yet, ConfigMgr will try to detect the product but inevitably fail.
In cases like this, adding a simple script to add a timeout is enough to fix this issue. You can also add a sleep period after the installation process by adding Start-Sleep -seconds 60
within the PSADT installer script after the msi install commands. A 60-second delay is generally enough, but you can modify it as you prefer.
User Reported Fixes
Note: User-reported fixes generally only apply to niche scenarios, but they are worth looking into nonetheless.
One user reported facing the 0X87D00324 error because he only copied the GUID (product code), and not the curly brackets, as he didn’t think they were necessary. We tend not to notice small things like this, so make sure you give the product code a double check.
Another user reported that he wrote a script but couldn’t deploy it as an application. The reason why this happened was that the script was running as an account that didn’t have network access. Using a network access account and ensuring it has access to the application you’re trying to deploy will resolve the issue in such scenarios.