We have two images for our Windows 7 workstations that are about a year old. One sysprepped; one not sysprepped. I have a project to update the image to reduce amount of time it takes to push updates once the old image is deployed.

I deploy the non-sysprepped image down to a computer successfully. Install the updates to bring it current. I'm deleting the sysprep.succeeded tag from c:\windows\system32\sysprep as well as the KACE folder from %ALLUSERSPROFILE%. 

Before sysprep, I capture the newly updated non-sysprepped system. Once captured, I restart the system and then use the Sysprep Creator tool to create a new unattend.xml and executor file. During the setup, I set my organization information, time zone/locale, enable the admin account, choose to keep in a workgroup. I run the executor and shut the system down. Boot up and capture the new sysprep image (as a .wim file) successfully to the kbox. 

Per the KB article at the recapture is done; I restart the machine to validate the mini-setup runs correctly but during the "Setup is applying system settings" stage, I'm getting the error message "Windows Setup could not configure Windows to run on this computer's hardware". Simply pressing OK, reboots the system back into the same error.

Honestly, I don't know why this is failing or where I can go to get more specific information. I'm not sure what really changed and am looking for any ideas or tips if anyone else has seen this?

Thank you for any help you can provide and please feel free to ask me for any other information if needed
1 Comment   [ + ] Show Comment


  • Chuck is correct, I have observed that sysprep can damage the OS, which is why its always recommended to obtain a non-syspreped image just in case you need to push it back down to the original system. One other method you might use is a virtual system, then before you sysprep the system complete a snapshot (VMWare) so you can easily return to that image.
Please log in to comment


I have seen this before and in my experience the image itself is normally fine. Try applying the sysprepped image that you uploaded to another computer to see if it works.

Answered 09/07/2015 by: chucksteel
Red Belt

  • Unfortunately deploying the sysprepped image to a different system altogether produces the same error. The deployment goes fine but it's during the first reboot (mini-setup) that it fails with the error. I'm just wondering if there is a way to get more information out of the error because I have no idea why it's failing at this point.
    • Yes there is a way to get more info, you need to check the DISM logs on that machine and it should tell you exactly what failed: C:\Windows\Logs\DISM\dism.log
Please log in to comment
Ended up working with support on this. Seems like a storage driver was not being correctly manipulated during the sysprep process. End result unfortunately was to create a brand new image on a VM versus refreshing an already existing image.
Answered 09/10/2015 by: dtobias_keenan
Green Belt

  • The same thing happened to me but my setup resulted in a blue screen and not the error you were seeing.
Please log in to comment
Answer this question or Comment on this question for clarity