Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

PENDING SCCM Application Deployment 0x87D00213 Timeout Occurred

  • Thread starter Thread starter tmryan
  • Start date Start date
  • Replies Replies 2
  • Views Views 11K

tmryan

New Member
Messages
1
Reaction score
0
Points
1
I'm deploying an application called GTSuite which I've done before with previous version many times using the powershell PSADT AppDeploy Toolkit template (currently using version 3.8). However, while deploying a new version of the GTSuite application the installation times out due to hanging processes invoked by the main setup-windows.exe installer. This is confirmed on the client by the error found in the AppEnforce.log on the client (see below). When I manually run script I can see the processes being spanwed by the main setup-windows.exe which are hanging.

Exceeded timeout of 40 minutes while waiting for process 5028 to finish.
WaitForRunningProcess failed. Error 0x87d00213
CScriptHandler::CompleteEnforcement failed with 0x87d00213
CAppProvider::CompleteEnforcement failed with error 0x87d00213


The powershell command to execute the GTSuite installer is as follows:

Execute-Process -Path "$dirFiles\setup-windows.exe" -Parameters "--mode unattended --optionfile `"$dirSupportFiles\silent-windows.options`""

I'm wondering if anyone has encountered such behvior with an installer and if so, how did you manage to resolve a situation like this with hanging installation processes?

Thanks in advance for your time and consideration.
 

Attachments

  • 1577715074928.png
    1577715074928.png
    18.4 KB · Views: 5
Your app installation failed for timeout, check the app deployment type and change the estimated installation time. Or might be other installation running on you client machine?
 
Question when, I'm creating an update package which SCCM will allow me to do. However; when I deploy the newly created package the SCCM application cuts off. Is their some way I can stop that from happening or is their some place I should be looking?
 

Forum statistics

Threads
7,135
Messages
27,867
Members
18,155
Latest member
DanDanDanissimo
Back
Top