установка приложения с ошибкой 0x87d00324 2016410844
System Center Configuration Manager и как с ним бороться
SCCM, Intune, MDT, EMS, MDM, MAM, Azure AD и другие странные слова
установка приложения с ошибкой 0x87D00324 (-2016410844)
Ошибка из серии «поспешишь — людей насмешишь и будешь читать логи».
Установка Visio 2013 x86 на операционную систему x64 заканчивается ошибкой:
Executing Command line: «C:\Windows\ccmcache\8\setup.exe» /adminfile silent.msp with user context
Working directory C:\Windows\ccmcache\8
Post install behavior is BasedOnExitCode
Waiting for process 2268 to finish. Timeout = 120 minutes.
Process 2268 terminated with exitcode: 0
Looking for exit code 0 in exit codes table…
Matched exit code 0 to a Success entry in exit codes table.
Performing detection of app deployment type Silent install Visio 2013 x86(ScopeId_59A4B277-455C-46D4-9A22-85B0F4D6D8AF/DeploymentType_49e90a4a-5471-4fbb-af43-ca04b25a4c17, revision 1) for user.
+++ Application not discovered. [AppDT Id: ScopeId_59A4B277-455C-46D4-9A22-85B0F4D6D8AF/DeploymentType_49e90a4a-5471-4fbb-af43-ca04b25a4c17, Revision: 1]
Т.е. приложение корректно устанавливается, но после завершения установки выдаёт ошибку. Это происходило из-за того, что в методах обнаружения в спешке был указан файл Visio.exe в папке %Program Files%\Microsoft Office\Office15. 32-битное приложение в системе х64 устанавливается в папку Program Files (x86), а переменная %Program Files% перенаправляет нас в Program Files, где, понятное дело, нужных нам файлов нет.
Правильным решением в данном случае будет указать два метода обнаружения: 
Установка приложения с ошибкой 0x87d00324 2016410844
Вопрос
Deployment to the client is successful but the error reported within Clients «SCCM Software Center»
The software change returned error code 0x87D00324(-2016410844).
Can’t figure this one out and I did some googling with no success in finding a solution?
I am running an Adobe Flash install (.EXE)
Any help or direction would be greatly appreciated
Ответы
How did you set up the detection method (details)? An application installation will only be successful if the software to be installed will be detected successfully.
Все ответы
Thank you for the follow up regarding my issue.
How did you set up the detection method (details)? An application installation will only be successful if the software to be installed will be detected successfully.
I had setup the «detection method» as
Setting Type: Registry
Hive: HKEY_LOCAL_MACHINE
Key: SOFTWARE\Wow6432Node\Macromedia\FlashPlayer
Specified Reg Key: ( Supplied the registry key path for it to check)
Checked: Use (Default) registry key value for detection
Data Type: Version
Selected: This registry setting must satisfy the following rule to indicate the presence of this application
Value: 11.4.402.265 (Check for this Latest Adobe Flash Build/Version # 11.4.402.265)
P.S. I have just added the second x64 bit path for Registry Checking, as I only had the x32 WOW path. same error on both x86 and x64 systems.
Wow6432Node is not valid on x86 systems.
You should configure your registry check to verify the key at SOFTWARE\Macromedia\FlashPlayer and check the checkbox that says to use a 32-bit environment on 64-bit systems.
Also, why use the default value? I doubt there’s anything in there (the default value is the value display in a key in regedit with the name of «@»).
For a complete walk-through, check out this post: http://blog.configmgrftw.com/?p=469
Thank you for your response
«»Wow6432Node is not valid on x86 systems.»»»
Yes, that I am aware of that. Windows on Windows, for running x86 apps on x64 Windows
When I first created the detection method I had only created the «WoW» Check
for Flash value in the reg, which was running against both x86 & x64 Win 7
systems, and forgot to include the x64 check/, either case, the error appeared
on the WOW check. Presently I have 2 «Detection Clauses» one for x86
and the second clause is x64 ( non WOW Path), and still receive the same erorrs
on both x86 & x64 systems. ( and x64 system have both reg entries since Win 7 has both x86 & x64 versions of IE)
Looking at the registry of an x64 Win 7 system I find the Adobe Flash registry entry is
located in both Wow6432Node and also in the x64 sections of the reg.
«»»» Also, why use the default value? I doubt there’s anything in there (the default value is the
value display in a key in regedit with the name of
«@»).»»»»
When Default Value is selected the boxes/options below that allow for more detailed
information to be entered when performing the «reg check»? This is
where I had been able to enter specific Build/Version to look for, Flash
11.4.402.265, so that if it does not discover the build # it will proceed with
the install.
I figured having the option to check for Build/Version # would omit SCCM reinstalling on
systems that have build 11.4.402.265 already?
From what I understand is that Adobe Flash x64 installs both versions x86 & x64 since Win 7 has both IE
x86 & IE x64 bit versions by default, and this would explain the Wow6432Node reg
entries and the true x64 reg entries in both locations when installing.
Overall, I am thinking I may be heading in the wrong direction in resolving this, as x86 & x64 versions install on the systems, so this tells me it is detecting when / what needs to be installed, the issue seems to be how it reports back after installing.
Looking further, I view the Content Status Page, and there reporting info in Asset Detail under [Success] all others < / In Progresss / Error /Unknown >has no info.
question
We are in the process of performing the Feature update for 1909 in our environment.
Most of the users to whom we have deployed are receiving the error mentioned below
Please suggest on how to process and manage them on larger deployments
I was getting the same error code on several clients and the issue was related to a language pack CAB file that was not matching the OS version (1909 in our case). For my specific case, a language pack was deployed to the PC and needed to be prestaged and that operation was failing at OS upgrade.
Anyway, I found the root cause by using the Setupdiag tool (https://docs.microsoft.com/en-us/windows/deployment/upgrade/setupdiag). It tells you exactly what the problem is (last step where it failed, error code, last action, etc.)
Hope this will help other people.
1 Answer
You need to find 0x1900xx type of error code which would reveal you the real reason for Inplace Upgrade. Also use setupdiag to evaluate the root cause, it’s a good tool which collects all logs needed into one place and tries to read the root cause.
Thanks for your reply Yannara, we are currently deploying this feature update from SCCM as a regular deployment. How would you suggest we check with the Setupdiag tool on end user machines as we have over 1000+ users facing the issue with this feature update install.
Could there be an alternate solution or way to check with this issue.
Also we have checked with the setupdiag process and please find the status below from setupdiagrestults
Would you mind letting me know the update of the problem? If you need further assistance, feel free to let me know.
Установка приложения с ошибкой 0x87d00324 2016410844
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Answered by:
Question
Deployment to the client is successful but the error reported within Clients «SCCM Software Center»
The software change returned error code 0x87D00324(-2016410844).
Can’t figure this one out and I did some googling with no success in finding a solution?
I am running an Adobe Flash install (.EXE)
Any help or direction would be greatly appreciated
Answers
How did you set up the detection method (details)? An application installation will only be successful if the software to be installed will be detected successfully.
All replies
Thank you for the follow up regarding my issue.
How did you set up the detection method (details)? An application installation will only be successful if the software to be installed will be detected successfully.
I had setup the «detection method» as
Setting Type: Registry
Hive: HKEY_LOCAL_MACHINE
Key: SOFTWARE\Wow6432Node\Macromedia\FlashPlayer
Specified Reg Key: ( Supplied the registry key path for it to check)
Checked: Use (Default) registry key value for detection
Data Type: Version
Selected: This registry setting must satisfy the following rule to indicate the presence of this application
Value: 11.4.402.265 (Check for this Latest Adobe Flash Build/Version # 11.4.402.265)
P.S. I have just added the second x64 bit path for Registry Checking, as I only had the x32 WOW path. same error on both x86 and x64 systems.
Wow6432Node is not valid on x86 systems.
You should configure your registry check to verify the key at SOFTWARE\Macromedia\FlashPlayer and check the checkbox that says to use a 32-bit environment on 64-bit systems.
Also, why use the default value? I doubt there’s anything in there (the default value is the value display in a key in regedit with the name of «@»).
For a complete walk-through, check out this post: http://blog.configmgrftw.com/?p=469
Thank you for your response
«»Wow6432Node is not valid on x86 systems.»»»
Yes, that I am aware of that. Windows on Windows, for running x86 apps on x64 Windows
When I first created the detection method I had only created the «WoW» Check
for Flash value in the reg, which was running against both x86 & x64 Win 7
systems, and forgot to include the x64 check/, either case, the error appeared
on the WOW check. Presently I have 2 «Detection Clauses» one for x86
and the second clause is x64 ( non WOW Path), and still receive the same erorrs
on both x86 & x64 systems. ( and x64 system have both reg entries since Win 7 has both x86 & x64 versions of IE)
Looking at the registry of an x64 Win 7 system I find the Adobe Flash registry entry is
located in both Wow6432Node and also in the x64 sections of the reg.
«»»» Also, why use the default value? I doubt there’s anything in there (the default value is the
value display in a key in regedit with the name of
«@»).»»»»
When Default Value is selected the boxes/options below that allow for more detailed
information to be entered when performing the «reg check»? This is
where I had been able to enter specific Build/Version to look for, Flash
11.4.402.265, so that if it does not discover the build # it will proceed with
the install.
I figured having the option to check for Build/Version # would omit SCCM reinstalling on
systems that have build 11.4.402.265 already?
From what I understand is that Adobe Flash x64 installs both versions x86 & x64 since Win 7 has both IE
x86 & IE x64 bit versions by default, and this would explain the Wow6432Node reg
entries and the true x64 reg entries in both locations when installing.
Overall, I am thinking I may be heading in the wrong direction in resolving this, as x86 & x64 versions install on the systems, so this tells me it is detecting when / what needs to be installed, the issue seems to be how it reports back after installing.
Looking further, I view the Content Status Page, and there reporting info in Asset Detail under [Success] all others < / In Progresss / Error /Unknown >has no info.
Установка приложения с ошибкой 0x87d00324 2016410844
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Answered by:
Question
Deployment to the client is successful but the error reported within Clients «SCCM Software Center»
The software change returned error code 0x87D00324(-2016410844).
Can’t figure this one out and I did some googling with no success in finding a solution?
I am running an Adobe Flash install (.EXE)
Any help or direction would be greatly appreciated
Answers
How did you set up the detection method (details)? An application installation will only be successful if the software to be installed will be detected successfully.
All replies
Thank you for the follow up regarding my issue.
How did you set up the detection method (details)? An application installation will only be successful if the software to be installed will be detected successfully.
I had setup the «detection method» as
Setting Type: Registry
Hive: HKEY_LOCAL_MACHINE
Key: SOFTWARE\Wow6432Node\Macromedia\FlashPlayer
Specified Reg Key: ( Supplied the registry key path for it to check)
Checked: Use (Default) registry key value for detection
Data Type: Version
Selected: This registry setting must satisfy the following rule to indicate the presence of this application
Value: 11.4.402.265 (Check for this Latest Adobe Flash Build/Version # 11.4.402.265)
P.S. I have just added the second x64 bit path for Registry Checking, as I only had the x32 WOW path. same error on both x86 and x64 systems.
Wow6432Node is not valid on x86 systems.
You should configure your registry check to verify the key at SOFTWARE\Macromedia\FlashPlayer and check the checkbox that says to use a 32-bit environment on 64-bit systems.
Also, why use the default value? I doubt there’s anything in there (the default value is the value display in a key in regedit with the name of «@»).
For a complete walk-through, check out this post: http://blog.configmgrftw.com/?p=469
Thank you for your response
«»Wow6432Node is not valid on x86 systems.»»»
Yes, that I am aware of that. Windows on Windows, for running x86 apps on x64 Windows
When I first created the detection method I had only created the «WoW» Check
for Flash value in the reg, which was running against both x86 & x64 Win 7
systems, and forgot to include the x64 check/, either case, the error appeared
on the WOW check. Presently I have 2 «Detection Clauses» one for x86
and the second clause is x64 ( non WOW Path), and still receive the same erorrs
on both x86 & x64 systems. ( and x64 system have both reg entries since Win 7 has both x86 & x64 versions of IE)
Looking at the registry of an x64 Win 7 system I find the Adobe Flash registry entry is
located in both Wow6432Node and also in the x64 sections of the reg.
«»»» Also, why use the default value? I doubt there’s anything in there (the default value is the
value display in a key in regedit with the name of
«@»).»»»»
When Default Value is selected the boxes/options below that allow for more detailed
information to be entered when performing the «reg check»? This is
where I had been able to enter specific Build/Version to look for, Flash
11.4.402.265, so that if it does not discover the build # it will proceed with
the install.
I figured having the option to check for Build/Version # would omit SCCM reinstalling on
systems that have build 11.4.402.265 already?
From what I understand is that Adobe Flash x64 installs both versions x86 & x64 since Win 7 has both IE
x86 & IE x64 bit versions by default, and this would explain the Wow6432Node reg
entries and the true x64 reg entries in both locations when installing.
Overall, I am thinking I may be heading in the wrong direction in resolving this, as x86 & x64 versions install on the systems, so this tells me it is detecting when / what needs to be installed, the issue seems to be how it reports back after installing.
Looking further, I view the Content Status Page, and there reporting info in Asset Detail under [Success] all others < / In Progresss / Error /Unknown >has no info.