MDT 2013 Task sequence Dirty Environment found due to unexpected reboot.

Hi Guys,

I hope someone could shed some light here. I have an MDT 2013 task sequence that installs the OS (Windows 8.1 in this case) and a few 3rd party applications (Winzip, Adobe reader etc). On top of this I have a command line step in the task sequence that executes a driver check & update to an internal Lenovo Update Retriever server in our environment. This installs all the latest drivers for this manufacturer and works like a charm with one exception. The installation of one of the drivers forces a windows reboot, and to the MDT this reboot is unexpected with the result being when the machine comes up again, a "dirty environment" is found. I click on "No" when prompted to recover and the installation continues and completes just fine. The problem I have is that this prompt basically holds up the entire task sequence and waits for...