Return
-
Title
Windows 10 deployments cause KACE Task Engine to run twice during Windows PO Tasks -
Description
When doing a Scripted install or an image deployment ( WIM or Kimage ) when the system reboots and begins the Post Install tasks, Kace Task Engine is started twice causing all PO tasks to be run twice and sometimes fails the deployment due to conflicts.
-
Cause
Starting with Windows 10, Microsoft has made the "Run" and "RunOnce" registry keys from being synchronous (meaning all must complete before the shell is visible) to asynchronous (the shell shows up before they are done). This causes the Task Engine to run twice.
-
Resolution
The workaround for now.Create a PO batch task named, “windows10 fix”The 'Bat Script:' text should read “exit /b 0“ without the quotes (see screenshot)Check the “Reboot Required“ box and save the task.
Add this task as the first PO task on your windows 10 deployment. The reboot will clear the dual Task Engine problem by restarting the device prior to the second Task Engine starting.**Note: As it adds another reboot you will need to change the autologon count appropriately.