I ran into this error today, building a Windows 7 image from a Build and Capture Task Sequence. The SMSTSLog showed the following at the “Setup windows and ConfigMgr” step:
The task sequence execution engine failed executing the action (Setup windows and ConfigMgr) in the group (Build the Reference Machine) with the error code 2147500037
Action output: on information to C:\_SMSTaskSequence\unattend.xml
Successfully initialized driver information
Command line for extension .EXE is “%1” %*
Set command line: “\\SCCMSERVER.LOCAL\SMSPKGD$\100004\SOURCES\SETUP.EXE” “/unattend:C:\_SMSTaskSequence\unattend.xml” /noreboot
Executing command line: “\\SCCMSERVER.LOCAL\SMSPKGD$\100004\SOURCES\SETUP.EXE” “/unattend:C:\_SMSTaskSequence\unattend.xml” /noreboot
Process completed with exit code 31
Windows Setup completed with exit code 31
EnteringReleaseSource() for \\SCCMSERVER.LOCAL\SMSPKGD$\100004reference count 1 for the source \\SCCMSERVER.LOCAL\SMSPKGD$\100004\ before releasing
Released the resolved source \\SCCMSERVER.LOCAL\SMSPKGD$\100004exitCode == 0, HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\setupwindows\setupwindows.cpp,440)
setup.run(), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\setupwindows\setupwindows.cpp,1707)
Exiting with code 0x80004005
Windows setup failed, code 31. The operating system reported error 2147500037: Unspecified error
The task sequence execution engine failed execution of a task sequence. The operating system reported error 2147500037: Unspecified error
It turns out that this was due to using a MAK Product key from the customer in the Task Sequence, the indicator was the “Windows setup failed, code 31” error.
Removing the key solved the problem. Using a Volume key should be ok but haven’t got one to test this out yet.
Hope this helps.
I am getting the above error. And i have checked in the task sequence with action Apply windows Settings that i am not specifying any license. Could you please help me?
Hi, this error from Windows setup is either the license key, or something wrong in the unattended xml, or from using non-volume media, or from a badly written driver. These four conditions can cause this error. If you think it may be a driver then install a reference machine and capture the image. Build and capture will save time and headaches…