JayL Posted September 27, 2017 Report post Posted September 27, 2017 I'm working on Win10 deployment. Created win10 64bit boot image with package ID XXX00043 and loaded in SCCM 2012. It had some problem, so deleted it and created a new one with package ID XXX00046 and . But when I booted my laptop up from bootable USB and select the Win10 TS from the list, it gave me an error: "This task sequence cannot be run because the program file for XXX00043 cannot be located on a distribution point." I recreated TS with boot image ID XXX00046, recreated TS. But it still look for XXX00043. I don't XXX00043 in SCCM now. Any idea? Thx Quote Share this post Link to post Share on other sites More sharing options...
SMoRZ3 Posted September 27, 2017 Report post Posted September 27, 2017 Have you tried recreating your boot media? Anytime you mess with your boot images its usually a good idea to re-create your media. Quote Share this post Link to post Share on other sites More sharing options...
JayL Posted September 27, 2017 Report post Posted September 27, 2017 Yes, I did that with no luck Quote Share this post Link to post Share on other sites More sharing options...
SMoRZ3 Posted September 27, 2017 Report post Posted September 27, 2017 Ive had issues with SCCM using older revisions of stuff. To work around this and get my newer changes quicker / and reliably I have started copying a task sequence, making changes, and then deploying that one. Then when I deploy it I get only that version of the TS. So I have a lot of "%OS VERSION% - %TODAYS DATE% - %VERSION%" Example "Win 10 ENT 1703 x64 - 9-27-17 - V1" test TS when I'm perfecting my TS for production.... Try copying your TS and seeing if the boot error goes away.... Quote Share this post Link to post Share on other sites More sharing options...
JayL Posted September 27, 2017 Report post Posted September 27, 2017 Tried that... did not help. Same issue Quote Share this post Link to post Share on other sites More sharing options...
SMoRZ3 Posted September 27, 2017 Report post Posted September 27, 2017 Have you right clicked your task sequence, gone to properties, advanced tab, and then made sure the new boot image is selected? Quote Share this post Link to post Share on other sites More sharing options...
JayL Posted September 28, 2017 Report post Posted September 28, 2017 I had fixed this issue. Thank you all. Quote Share this post Link to post Share on other sites More sharing options...
SMoRZ3 Posted September 28, 2017 Report post Posted September 28, 2017 1 hour ago, JayL said: I had fixed this issue. Thank you all. What was the fix for future reference? Quote Share this post Link to post Share on other sites More sharing options...
