Hopefully this is a good reference area for this issue. I had been tracking this down as a possible problem with Windows 10 and Provisioning since the issue only appeared recently as I have been building out our Windows 10 provisioning templates. As it turns out, this problem is not caused by LANDESK provisioning issues with Windows 10. I was able to trace the problem to a Microsoft KB 3163018.
In ever case we had, this patch was hanging up our provisioning automation because the system would just sit there with the blue screen and the 'restarting' swirly animation. Hard rebooting the device allowed the system to continue on. We have turned this patch off within LANDESK. Hope this saves someone some time troubleshooting.