This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(288, 42%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
I'm occasionally getting 0x87D00324 (-2016410844) errors in Software Center (application always installs fine) when using two registry clauses with Or set the Connector. After a failure, clicking Retry in Software Center then shows the app is installed with no errors. The purpose of having multiple registry clauses to detect ARP info for different product codes for x86 and x64 .msi's.
Does the install iterate through all detection methods until it detects the correct one during the install with "Or" as the Connector?
It appears the detection methods are randomly being chosen without iteration and will fail until it finds the right one after clicking retry in Software Center.
If this is the case, is there a more reliable solution to avoid these detection errors outside of a custom script?
Multiple deployment types, one for x64 and one for x86 would probably be the best solution.
After further testing with multiple deployment types (one for x86 and one for x64), I'm still running into the same issue with only one registry detection method in which it will fail the first time 0x87D00324 (-2016410844), but clicking Retry in Software Center will show it as installed; I confirmed the client has the correct registry entry.
Anyone experience 0x87D00324 with or without using PSADT when only using a single registry detection method?
I ended up switching to msi product code and file system detection methods which work without issue.
ssclient log:
AppDetails received Event Application Enforcement Failed, state 4, causing a state display value of Failed. The Action Button says _Retry and its enabled state is True (Microsoft.SoftwareCenter.Client.ViewModels.ApplicationDetailsViewModel+<WmiDataConnection_WmiNotificationEvent>d__138 at MoveNext)
The registry detection issue was resolved by adding Start-Sleep -seconds 15 within the PSADT installer script after the msi install commands. I confirmed that the install iterates through all detection methods with "Or" set as the Connector for all detection methods configured until it detects the correct one. This was done by adding a half dozen incorrect registry detection entries with the correct one buried in the middle.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(64, 77%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERS%3C/text%3E%3C/svg%3E)
Use this to detect the installed app location
Clear-Host $Hive = Get-ChildItem -Path HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall $Hive2 = Get-ChildItem -Path HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall Write-Host -ForegroundColor Green "x64 Registry Hive - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall " $Hive | Get-ItemProperty | Select-Object -Property PSChildName, DisplayName, DisplayVersion, UninstallString | Sort-Object DisplayName | Format-Table -AutoSize -Wrap Write-Host -ForegroundColor Cyan "x86 Registry Hive - HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall" $Hive2 | Get-ItemProperty | Select-Object -Property PSChildName, DisplayName, DisplayVersion, UninstallString | Sort-Object DisplayName | Format-Table -AutoSize -Wrap
Once located use this to set detection, 99% it will work
$App = (Get-ChildItem -Recurse "HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\" | Get-ItemProperty | Where-Object {($_.DisplayVersion -ge '5.11.0.522.1') -and ($_.Displayname -eq "Adobe Creative Cloud")} | Select-Object Displayname, DisplayVersion) if ($App.DisplayVersion -ge "5.11.0.522.1") {Write-Host "Adobe Creative Cloud is installed"} else {}
This will work perfectly
Hi, @Steve
Thank you for posting in Microsoft Q&A forum.
The purpose of having multiple registry clauses to detect ARP info for different product codes for x86 and x64 .msi's.
For this purpose, we may use "This registry key is associated with a 32-bit application on 64-bit systems" instead of using two registry clauses.
If we check the box "This registry key is associated with a 32-bit application on 64-bit systems" in detection rule of Registry, then SCCM will first check 32-bit registry locations for the specified registry key. If the registry key isn't found, the client searches 64-bit locations. You may check it and try again to see if it help.
Related documentation:
https://home.memftw.com/configmgr-2012-and-32-bit-application-installers/
https://learn.microsoft.com/en-us/mem/configmgr/apps/deploy-use/create-applications#bkmk_detect-rule
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Unfortunately, the msi’s have two different product codes so that solution would not apply. Does the install iterate through all detection methods until it detects the correct one during the install with "Or" as the Connector?
Hi, @Steve
Thanks for the feedback.
Does the install iterate through all detection methods until it detects the correct one during the install with "Or" as the Connector?
No, I don't think so. And you said when you test with multiple deployment types(one deployment with one registry clause), it will also failed at the first time. So the connector "Or" should means: if one of the detection methods is met, it will be considered as success.
The issue that failed on first time but success on retry should be related to the option:
"Run installation and uninstall program as 32-bit process on 64-bit clients".
Check this option may fix the issue.
Here is an old thread for your reference:
https://social.technet.microsoft.com/Forums/en-US/0634d877-08ee-4505-bc70-92f1be6fbbbc/deployment-always-fails-on-first-time-but-succeeds-on-retry?forum=configmanagerapps
If the response is helpful, please click "Accept Answer" and upvote it.