xc3ss1v3 Posted July 16, 2014 Report post Posted July 16, 2014 Hey guys and gals... I've suddenly run into an issue where my OSD TS is failing at the Apply Operating System step with an error code of 8007000B "An attempt was made to load a program with an incorrect format." Upon some preliminary research, it seemed this early was likely due to some kind of mismatch between x86 and x64 boot images vs. OS image or possibly with WinPE 5.0. I've double and triple check the bitness of both the OS being deployed and the boot image being used. Both are x86 in this case. I've deployed fresh WinPE 5.0 images with no extra drivers installed to be sure that wasn't the issue. I can't imagine it's the actual OS image as it was working just fine and nothing has changed AFAIK other than offline servicing of latest Windows Updates. Could that possibly be an issue? I've attached an SMSTS.log for review. smsts.log Quote Share this post Link to post Share on other sites More sharing options...
wilbywilson Posted July 16, 2014 Report post Posted July 16, 2014 I believe that I've read that offline servicing of the Windows Updates can sometimes cause issues, unfortunately. But, the offline servicing process should have made a ".bak" file of your original WIM. Can you revert to that original WIM and see if the TS works? Quote Share this post Link to post Share on other sites More sharing options...
xc3ss1v3 Posted July 17, 2014 Report post Posted July 17, 2014 I believe that I've read that offline servicing of the Windows Updates can sometimes cause issues, unfortunately. But, the offline servicing process should have made a ".bak" file of your original WIM. Can you revert to that original WIM and see if the TS works? I'm think that is what caused it. I looked back in the logs and there was an error concerning copying the .wim back to the source drive (think I inadvertently restarted during the process) and now when I try to re-schedule those updates, I get an error saying that it can not read the image format. Guessing there's some sort of corruption in it. Instead of just reverting back to the .bak file, I'm running a new build & cap for a completely fresh .wim. Will report back what I find. Thanks for the help. Quote Share this post Link to post Share on other sites More sharing options...
xc3ss1v3 Posted July 17, 2014 Report post Posted July 17, 2014 I believe that I've read that offline servicing of the Windows Updates can sometimes cause issues, unfortunately. But, the offline servicing process should have made a ".bak" file of your original WIM. Can you revert to that original WIM and see if the TS works? Okay... in this particular case, this error was definitely being caused by a corrupt .wim file created by a failed offline servicing. Just for fun, I created a new .wim using a B&C and also used the .bak wim file, re-scheduled offline servicing which completely successfully on both, and was able to use those to successfully deploy an OS again. Thanks for the assist! Quote Share this post Link to post Share on other sites More sharing options...
