0x87D00324 (also shown as -2016410844) means Configuration Manager could not detect the application after the installation command finished. It does not necessarily mean that the installer failed.
The usual cause is a mismatch between the deployment type’s detection method and what the installer actually creates: the wrong file path, registry hive, MSI product code, architecture, installation context, or timing. Check the installer result and detection result separately before repairing the client or clearing its cache.
What 0x87D00324 means
Configuration Manager runs an application deployment in two important stages:
- It executes the deployment type’s installation command.
- It runs the detection method again to verify that the application is now installed.
If the installer returns success but the detection rule returns false, Configuration Manager reports 0x87D00324: the application was not detected after installation completed.
#1 Best Overall
- Ultra-Portable: Slim, portable, and light weight allowing you to protect your investment wherever you go
- Ergonomic Comfort: Doubles as an ergonomic stand with two adjustable height settings
- Optimized for Laptop Carrying: The metal mesh provides your laptop with a stable laptop carrying surface
- Ultra-Quiet Fans: Three ultra-quiet fans create a noise-free environment for you
- Extra Usb Ports: Extra USB port and power switch design allows for connecting more USB devices. Warm Tips: The packaged cable is USB to USB connection. Type C connection devices need to prepare an Type C to USB adapter
This distinction matters. A successful installer exit code only describes the installer process. It does not prove that Configuration Manager’s file, registry, MSI, or script detection rule found the expected result.
Microsoft documents separate errors for content problems. For example, 0x87D00607 indicates that content was not found, while 0x87D01107 indicates that the client could not access all provided program locations. Those are different from this post-install detection error.
Use the correct troubleshooting order
- Confirm whether the application actually installed.
- Confirm whether it installed for the user or for the computer.
- Check the exact artifact used by detection: file, folder, registry value, MSI product code, or script output.
- Check 32-bit and 64-bit redirection.
- Check reboot and asynchronous-install behavior.
- Confirm that the client received the current application revision and content.
- Investigate client health, distribution points, boundaries, or cache only if the logs indicate those areas.
Check the Configuration Manager logs first
On the affected device, the default client log folder is:
C:WindowsCCMLogsReview these logs with CMTrace or another text viewer:
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errors| Log | What it tells you |
|---|---|
AppEnforce.log |
The command line run, execution context, content path, installer exit code, and reboot request. |
AppDiscovery.log |
The detection method evaluated and whether the result was Installed, Not installed, or Unknown. |
AppIntentEval.log |
Application applicability, requirements, dependencies, and intended state. |
CIAgent.log |
Configuration Item evaluation and state processing. |
LocationServices.log |
Management-point and distribution-point location activity. |
ContentTransferManager.log and DataTransferService.log |
Content download and transfer problems. |
What to find in AppEnforce.log
Look for the deployment type being enforced and verify:
- The exact installation command Configuration Manager executed.
- Whether the command ran as
SYSTEMor as a logged-on user. - The cache directory containing the deployment content.
- The installer’s process exit code.
- Whether the installer requested a reboot.
Then compare the result with AppDiscovery.log. If AppEnforce.log shows a successful installer exit code and AppDiscovery.log shows the application as Not installed, focus on detection rather than reinstalling the client.
Correct the detection method
To edit detection for an existing application in the current Configuration Manager console:
- Open the Configuration Manager console.
- Go to Software Library.
- Expand Application Management and select Applications.
- Select the affected application.
- Open the Deployment Types tab in the details pane.
- Open the deployment type’s properties.
- Select the Detection Method tab.
You can either select Configure rules to detect the presence of this deployment type and choose Add Clause, or select Use a custom script to detect the presence of this deployment type and choose Edit.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #2
- Whisper-Quiet Operation: Enjoy a noise-free and interference-free environment with super quiet fans, allowing you to focus on your work or entertainment without distractions.
- Enhanced Cooling Performance: The laptop cooling pad features 5 built-in fans (big fan: 4.72-inch, small fans: 2.76-inch), all with blue LEDs. 2 On/Off switches enable simultaneous control of all 5 fans and LEDs. Simply press the switch to select 1 fan working, 4 fans working, or all 5 working together.
- Dual USB Hub: With a built-in dual USB hub, the laptop fan enables you to connect additional USB devices to your laptop, providing extra connectivity options for your peripherals. Warm tips: The packaged cable is a USB-to-USB connection. Type C connection devices require a Type C to USB adapter.
- Ergonomic Design: The laptop cooling stand also serves as an ergonomic stand, offering 6 adjustable height settings that enable you to customize the angle for optimal comfort during gaming, movie watching, or working for extended periods. Ideal gift for both the back-to-school season and Father's Day.
- Secure and Universal Compatibility: Designed with 2 stoppers on the front surface, this laptop cooler prevents laptops from slipping and keeps 12-17 inch laptops—including Apple Macbook Pro Air, HP, Alienware, Dell, ASUS, and more—cool and secure during use.
File-system detection
For a File System rule, verify each setting against the installed device, not the source folder:
- File versus folder detection.
- Local path.
- File or folder name.
- Version, size, creation-date, or modification-date comparison.
- Whether the artifact exists before post-install detection runs.
A file-system detection path must be local to the client. A UNC path cannot be used as the file-system detection path.
Do not detect an installer artifact in the package source or a temporary extraction folder if setup deletes it. Choose a persistent file or folder that proves the intended application is installed. For example, an executable under the application’s final installation directory is usually more useful than setup.exe in a temporary directory.
Registry detection
Check the following registry settings:
- Hive, such as
HKEY_LOCAL_MACHINEorHKEY_CURRENT_USER. - Key path.
- Value name and data.
- Whether Use (Default) registry key value for detection is selected correctly.
- Data type.
- Version comparison and operator.
Configuration Manager can detect either a registry key or a registry value. Make sure the rule reflects the value actually written by the installer.
Check the user or system context
A common failure occurs when the installer writes per-user data but the deployment type runs and detects as SYSTEM. A system-context process cannot reliably use the logged-on user’s HKEY_CURRENT_USER hive as its detection location.
Open the deployment type’s User Experience tab and check the installation behavior:
- Install for user
- Install for system
- Install for system if resource is device; otherwise, install for user
For a device-targeted application, use a machine-wide installation and machine-level detection unless the application is deliberately designed to be per-user.
Check 32-bit and 64-bit redirection
On 64-bit Windows, 32-bit and 64-bit applications can use different registry views. File-system locations can also differ, particularly between Program Files and Program Files (x86).
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallRank #3
- 👍【Triple Efficient Fans】TECKNET laptop cooling pad with 3 powerful fans works at 1200 RPM to pull in cool air from the bottom to prevent your laptop, notebook, netbook, Ultrabook, Apple MacBook Pro cool from overheating during extended use or intense gaming.
- ✌️【Easy to Use】Powered directly by your laptop's USB port, the 110mm fans operate quietly and feature a dedicated on/off switch. No external power adapter is needed.
- 👑【Double USB Ports】One USB port can power the laptop cooler, the other one can be connected to external devices, such as keyboard, mouse, audio, etc. Blue LED indicators confirm the fans are running. Note: The included cable is USB-A to USB-A.
- 👍【Ergonomic Comfort】Choose between two adjustable height settings to achieve a more comfortable viewing angle. Integrated rubber pads on the surface and base keep your laptop securely in place.
- 👌【Wide Compatibility】Compatible with various laptop sizes from 12 up to 17 inches, such as Apple MacBook Pro Air, HP, Alienware, Dell, Lenovo, ASUS, etc (USB cable included). The laptop fan can also accurately dissipate heat for your tablet, router, game console.
For file detection, enable This file or folder is associated with a 32-bit application on 64-bit systems when the application installs in the 32-bit location.
For registry detection, enable This registry key is associated with a 32-bit application on 64-bit systems when the application writes to the 32-bit registry view.
Do not add Wow6432Node manually as a general workaround. Use the Configuration Manager 32-bit option so the client evaluates the appropriate registry view.
MSI product-code detection
For a Windows Installer deployment type, verify that the detection product code belongs to the exact MSI being installed. In the console, the product code can be read by selecting Browse and choosing the MSI file.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Check for these common mismatches:
- The deployment installs a different architecture or edition than the MSI used for detection.
- A wrapper or bootstrapper installs a different MSI.
- A major upgrade changed the product identity.
- The installation is per-user while detection expects a machine installation.
- A newer source MSI has a different product code.
If entering a product code manually, use the complete GUID format, including braces. Never assume that replacing an MSI with a newer release preserves its product code.
Custom detection scripts
Configuration Manager evaluates a custom detection script’s exit code, standard output, and standard error. The success condition is:
- Exit code
0. - Non-empty standard output.
This script reports the application as installed:
Write-Output "Installed"
exit 0This script does not:
exit 0A zero exit code with no output is treated as Not installed. A non-zero exit code produces an Unknown detection state.
PowerShell detection scripts run with -NoProfile. Do not rely on aliases, variables, functions, or modules loaded only by a user profile. Detection scripts are limited to 32 KB. If the script must inspect 32-bit locations on a 64-bit client, enable Run script as 32-bit process on 64-bit clients on the Detection Method page.
Recommended Free Tools
Rank #4
- 【High-Speed Cooling Performance】 Equipped with two powerful fans and a precision metal mesh design, KYOLLY’s laptop cooling pad delivers optimal airflow to quickly dissipate heat, preventing overheating—even during extended use. Perfect for gaming, multitasking, or long work sessions.
- 【Slim, Lightweight & Highly Portable】 With its ultra-slim profile and lightweight build, this laptop cooler is easy to carry anywhere. A soft blue LED indicator lets you know when the fans are active, combining style with functionality.
- 【5-Level Height Adjustment & Anti-Slip Design】 Customize your typing and viewing angle with five ergonomic height settings. The built-in anti-slip baffles securely hold your laptop in place, making it both a efficient cooler and a reliable stand.
- 【Quiet Operation with Smooth Speed Control】 Enjoy focused work or gameplay thanks to virtually silent fan operation. Adjust wind speed smoothly with the rolling wheel controller to balance cooling power and noise level—ideal for office or shared environments.
- 【Universal Compatibility & Practical USB Ports】 Designed for laptops up to 15.6 inches, this cooler is perfect for home, office, or on-the-go use. Two additional USB ports offer convenient connectivity for peripherals like mice, keyboards, or phones.
Review multiple detection clauses
Multiple clauses can be combined with And or Or, and clauses can be grouped using the console’s Group and Ungroup actions.
Use this logic carefully. For example, an And condition requiring two registry values will fail if either value is absent. An Or condition may be appropriate for supported editions, but only if either result genuinely proves that the intended application is installed.
Do not create duplicate clauses merely to cover 32-bit and 64-bit registry locations. If the same logical key exists in the 32-bit view, use the supported 32-bit registry option instead.
In some environments, detection can race with an installer that creates registry entries asynchronously. A Microsoft Q&A case reported a 15-second delay helping with a multiple-registry-clause scenario. Treat that as a case-specific workaround, not as a replacement for correcting an inaccurate rule.
Free tools Windows power users keep installed
One-click scans. No signup required.
Check reboots and asynchronous installers
Some launchers exit before their child installer finishes. Others create services, registry entries, or application files only after a delay or reboot. A bootstrapper may also return before the MSI or updater it launched has completed.
Check the installer’s own log and the return code in AppEnforce.log. A standard reboot-required result is 3010. You can configure how Configuration Manager handles it here:
- Open the deployment type properties.
- Select the Return Codes tab.
- Select Add.
- Enter the return code.
- Choose the appropriate code type, such as Success (no reboot), Soft Reboot, Hard Reboot, Failure (no reboot), or Fast Retry.
If the application becomes detectable only after restarting, restart the computer and reevaluate the deployment. A short post-install delay may help with a confirmed asynchronous installer, but it cannot fix a wrong path, registry view, product code, context, or script.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Check policy, content, and deployment-type revisions
If you recently changed the detection rule or command line, confirm that the client received the updated application revision. A client using an older revision may execute an old command or evaluate an old detection method.
Best Value
- 9 Super Cooling Fans: The 9-core laptop cooling pad can efficiently cool your laptop down, this laptop cooler has the air vent in the top and bottom of the case, you can set different modes for the cooling fans.
- Ergonomic comfort: The gaming laptop cooling pad provides 8 heights adjustment to choose.You can adjust the suitable angle by your needs to relieve the fatigue of the back and neck effectively.
- LCD Display: The LCD of cooler pad readout shows your current fan speed.simple and intuitive.you can easily control the RGB lights and fan speed by touching the buttons.
- 10 RGB Light Modes: The RGB lights of the cooling laptop pad are pretty and it has many lighting options which can get you cool game atmosphere.you can press the botton 2-3 seconds to turn on/off the light.
- Whisper Quiet: The 9 fans of the laptop cooling stand are all added with capacitor components to reduce working noise. the gaming laptop cooler is almost quiet enough not to notice even on max setting.
Also verify:
- The current deployment type revision reached the client.
- The updated content was distributed to the required distribution points.
- The source folder contains the intended installer and wrapper files.
- The command line references the intended file.
- The cache path shown in
AppEnforce.logcontains the expected content.
Stale or incorrect content can make an installation behave differently from what the detection rule expects. However, a pure content-location failure normally produces a content or location-related error rather than 0x87D00324.
Refresh policy and reevaluate the application
After saving the corrected deployment type and distributing any changed content, allow the new policy to arrive. On the client, you can trigger policy retrieval from Control Panel > Configuration Manager > Actions by running the machine policy retrieval actions available in your environment. Then trigger an application deployment evaluation or use the Configuration Manager client notification feature from the console.
Recheck AppDiscovery.log to confirm that the corrected rule now returns Installed. If you make a new deployment type revision, test it on a device where you can inspect the actual installed file and registry state.
What not to do
- Do not assume the installer failed. The error specifically identifies a post-install detection failure.
- Do not reinstall the Configuration Manager client first. Repair is justified only when logs show a broader client-processing problem.
- Do not clear the client cache as a detection fix. Cache cleanup does not correct an inaccurate detection rule.
- Do not add a delay to every deployment. Use one only when installer timing is confirmed as the cause.
- Do not weaken detection to an arbitrary file. The chosen artifact should reliably prove that the intended application and version are installed.
Definitive fix checklist
- Open Software Library > Application Management > Applications.
- Open the application’s Deployment Types tab and edit the deployment type.
- Correct the detection path, registry rule, MSI product code, version comparison, architecture setting, or script output.
- Make sure the installation context matches the detection context.
- Configure reboot and return-code behavior correctly.
- Confirm the current policy and content revision reached the client.
- Review
AppEnforce.logandAppDiscovery.log. - Reevaluate the application after policy refresh.
FAQ
Does 0x87D00324 mean the installer failed?
No. It means Configuration Manager did not detect the application after the installation command completed. Check the installer exit code in AppEnforce.log and the detection result in AppDiscovery.log separately.
Where do I change the detection rule?
In the Configuration Manager console, go to Software Library > Application Management > Applications, select the application, open the Deployment Types tab, open the deployment type properties, and select Detection Method.
Why does a file or registry detection rule work manually but fail in Configuration Manager?
The rule may be running under the SYSTEM account, using a different 32-bit or 64-bit view, checking HKEY_CURRENT_USER instead of HKEY_LOCAL_MACHINE, or evaluating the device before an asynchronous installer has finished.
Should I add a 15-second delay?
Only if logs show that the installer returns before its files or registry entries exist. A delay cannot fix an incorrect path, product code, registry view, user context, or custom-script result.
Why does my custom PowerShell detection script still report Not installed?
The script must exit with code 0 and write non-empty output to standard output. A script containing only exit 0 produces no output and is treated as Not installed.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Should I clear CCMCache or reinstall the Configuration Manager client?
Not as a first step. Clear cache only for a demonstrated content problem, and repair or reinstall the client only when the logs show a wider client-processing failure.
The Bottom Line
0x87D00324 is usually fixed by aligning the deployment type’s detection method with the application’s real post-install state. Verify the actual file, registry value, MSI identity, script output, architecture, installation context, and reboot behavior; then confirm the client is using the current deployment type revision. The logs will tell you whether the installer failed or detection failed.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
