Fix OSD Error Cannot find the script file LTIBootstrap
Operating System deployment using Configuration Manager is not just about creating and deploying an image. It is an entire process that allows you to define actions before the image is applied to a system and the actions after the image is applied. Last week while I was working on OSD, my Task Sequence failed to resume after first logon. I came across OSD Error Cannot find the script file LTIBootstrap. The configuration manager was integrated with latest version of MDT. So in my case the OSD process went well until there was a point when the it automatically logs in and tries to run the unattended file. The unattended file is suppose to call the LTIBootstrap.vbs so that MDT can complete its process after first login. But it looked like this didn’t happen. This LTIBootstrap.vbs was not called and when i checked the log files I did not find any errors. The error that I got can be seen in the below screenshot.
Can not find script file “X:LTIBootstrap.vbs”
OSD Error Cannot find the script file LTIBootstrap
I don’t know if there is any other way to fix this issue. I am sharing the troubleshooting step that worked for me, if something else has helped you resolve this issue please share it in comments so that it could help others. In the MDT settings package that I had created, I edited a file named Unattend.xml. In this file look for the section where the LTIBootstrap script file is called, you could delete that section or comment it. Once you do that, update the MDT setting package. The next time when you deploy the TS, you will not find this error and the TS executes successfully.
Hello Prajwal in my case after deleting the LTIBootstrap.vbs in unattended.xml, the Task Sequence failed to resume after first logon. Please advised
Have been struggling for 3 days with different solutions and this worked like anything for me.
I had this issue with VMware workstation and windows 10 x64 1709 and it was due to using uefi instead of bios for the vm
Thanks for posting this. So, _removing_ the call to ltibootstrap.vbs in unattend.xml allowed the task sequence to _continue_ the TS after reboot? Interesting
Comments are closed.