Your deployment stops progressing in what seems to be the middle, but some patches never progress past Scheduled. You may see a failure or you may not.
This can be verified in the logs, but this is often an indication that the system shut down or restarted in the middle of the patching process. You may see log entries similar to the following in C:\Windows\ProPatches\Logs\STDeployerCore.log that highlight some patches that are still showing as Executing or Scheduled:
2018-08-06T21:05:32.1345530Z 0c80 V UnScriptedInstallation.cpp:30 Executing (C:\Windows\ProPatches\Patches\windows8.1-kb4346406-x64.msu /quiet /norestart), nShow: true.
2018-08-06T21:05:32.2751767Z 0c80 V ChildProcess.cpp:140 Process handle 00000394 returned '1115'.
2018-08-06T21:05:32.2751767Z 0c80 W DeployerImpl.cpp:106 Patch state is 'Failed'. Registry bread crumb patch state not updated.
2018-08-06T21:05:32.2751767Z 0c80 I Authenticode.cpp:134 Verifying signature of C:\Windows\ProPatches\Patches\windows8.1-kb4346745-x64.msu with CWinTrustVerifier
2018-08-06T21:05:32.6970575Z 0c80 V UnScriptedInstallation.cpp:30 Executing (C:\Windows\ProPatches\Patches\windows8.1-kb4346745-x64.msu /quiet /norestart), nShow: true.
2018-08-06T21:05:32.7595763Z 0c80 V ChildProcess.cpp:140 Process handle 000003E4 returned '1115'.
2018-08-06T21:05:32.7595763Z 0c80 W DeployerImpl.cpp:106 Patch state is 'Failed'. Registry bread crumb patch state not updated.
Deployments will not be able to resume after a shutdown or similar event, so it is recommended that you re-scan your target machine(s) to verify which patches were properly applied and push a new deployment.
Shavlik Protect 9.x
Ivanti Patch for Windows Servers 9.3.x