This is typically caused because the bootable partition is not beeing set correctly. If you are usind OSD set the system partition value on your script to the correct parittion. If you are using provisioning, set the correct partition as the active and bootable partition.
Eric, I agree with you except Fixwindows.exe is automatically put in the OSD script and with Dell computers, Dell puts a oem partition and also in some laptop models it adds another partition so if you captured a factory built harddrive then I have actually seen the cmd window that comes up for fixwindows in the Deploy job mark the wrong partitions causing this problem.
I think fixwindows.exe was written for only a 2 partitioned hard drive, os and boot.