Why Does the KACE SDA Get Stuck at "Set Engine Run Key" with Windows 11 22H2 Image?

I am deploying a Windows 11 22H2 image to a Dell Latitude 5520. The imaging process gets past the SDA Breadcrumb File task. The machine is supposed to restart either before or after the "Set Engine Run Key" task. Instead, I get a pop up in front of the Dell splash screen that says, "This computer restarted unexpectedly or encountered an unexpected error. Windows installation cannot proceed. To install Windows, click "OK" to restart the computer, and then restart the installation." If I click "OK", the screen flashes off and then the message pops back up again. And will continue to loop. I found that the only fix is while the error message is still on the screen:

  • Press "fn + SHIFT + F10" to bring up the command prompt, then type: regedit [ENTER]:
  • HKLM --> SYSTEM --> Setup --> Status --> Child Completion
  • Open setup.exe and change the value from 1 to 3
  • Close the regedit screen, then click "OK" on the error banner
  • Machine will reboot load into Windows 11, then continue with the imaging process

I've run this same image on a Dell Latitude 5530 and HP ProBook 450 G9 and have not had any issues. Does anyone know why this happens? Does this only happen with the Dell Latitude 5520? Is there a fix for this?

0 Comments   [ + ] Show comments

Answers (1)

Posted by: grvenega 1 year ago
Yellow Belt

The 'setengine run key' phase is just what the SDA reports, until the client boots upfrom the HDD/SSD for the 1st time, logs in and connects back to the appliancevia the kace task engine, to continue the deployment of the PO tasks. So, if aclient hangs at that point, the issue is with the client, could be related toone of the following:

1. a sysprepissue
2. too manydrivers in the image [pre-sysprep]
3. lack ofthe proper drivers injected at mid-level 

For moreinformation, seehttps://support.quest.com/kace-systems-deployment-appliance/kb/4288771/task-engine-stuck-on-set-engine-run-key

The imagewill have to be sysprepped with an unattend file and the unattend parameter,making sure to include the some autologon configuration. This can be doneeither manually or by leveraging the Sysprep Creator utility.
Steps bysteps instructions are here https://support.quest.com/kace-systems-deployment-appliance/kb/4232511/how-to-system-image-sysprep-capture-and-deploy

  • Thank you. I looked at the first link you provided and I think the issue may stem for scenario 4. It was suggested by a technician at Quest that I only capture the C drive and not both C and S... It's weird because out of the three model laptops I'm imaging it only happens with the Dell Latitude 5520. Anyway, thanks for the info! - kjwilson777 1 year ago
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ