Getting Windows Setup Failed Code 31

Question

_{Wednesday, September 7, 2016 12:51 PM}

Trying a new deployment from a new SCCM server and have been getting Windows setup failed code 31. I have captured all the logs and can post them if needed.

In the SMSTSLog I have a few warnings about drivers and a couple other warnings

Unsuccessful in finding a suitable device driver for device 'High Definition Audio Controller'. OSDDriverClient 9/6/2016 3:53:41 PM 1804 (0x070C)
Unsuccessful in finding a suitable device driver for device 'High Definition Audio Controller'. OSDDriverClient 9/6/2016 3:53:41 PM 1804 (0x070C)
Unsuccessful in finding a suitable device driver for device 'USB Mass Storage Device'. OSDDriverClient 9/6/2016 3:53:41 PM 1804 (0x070C)
Unsuccessful in finding a suitable device driver for device 'Microsoft System Management BIOS Driver'. OSDDriverClient 9/6/2016 3:53:42 PM 1804 (0x070C)
Unsuccessful in finding a suitable device driver for device 'Plug and Play Software Device Enumerator'. OSDDriverClient 9/6/2016 3:53:45 PM 1804 (0x070C)

RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram TSManager 9/6/2016 4:09:02 PM 1472 (0x05C0)
GetTsRegValue() is unsuccessful. 0x80070002. TSManager 9/6/2016 4:09:02 PM 1472 (0x05C0)
RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram TSBootShell 9/6/2016 4:09:02 PM 996 (0x03E4)
GetTsRegValue() is unsuccessful. 0x80070002. TSBootShell 9/6/2016 4:09:02 PM 996 (0x03E4)

And These Errors

Windows setup failed, code 31 OSDSetupWindows 9/6/2016 3:53:55 PM 1368 (0x0558)
Failed to run the action: Setup Windows and ConfigMgr. 
Unspecified error (Error: 80004005; Source: Windows) TSManager 9/6/2016 3:53:55 PM 1472 (0x05C0)
The group (Execute Task Sequence) ignored action failure and continue execution on the next step following the group. TSManager 9/6/2016 3:53:55 PM 1472 (0x05C0)
Start executing an instruction. Instruction name: Gather Logs and StateStore on Failure. Instruction pointer: 132 TSManager 9/6/2016 3:53:55 PM 1472 (0x05C0)
Set a global environment variable _SMSTSCurrentActionName=Gather Logs and StateStore on Failure TSManager 9/6/2016 3:53:55 PM 1472 (0x05C0)
The condition for the group (Gather Logs and StateStore on Failure) is evaluated to be true TSManager 9/6/2016 3:53:55 PM 1472 (0x05C0)
The group (Gather Logs and StateStore on Failure) has been successfully started TSManager 9/6/2016 3:53:55 PM 1472 (0x05C0)
ZTI deployment failed, Return Code = -2147467259  0x80004005 InstallSoftware 9/6/2016 3:53:59 PM 1480 (0x05C8)
Failed to run the action: Error in the task sequence. 

Unspecified error (Error: 80004005; Source: Windows) TSManager 9/6/2016 3:53:59 PM 1472 (0x05C0)

Let the parent group (Gather Logs and StateStore on Failure) decides whether to continue execution TSManager 9/6/2016 3:53:59 PM 1472 (0x05C0)
The execution of the group (Gather Logs and StateStore on Failure) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows) TSManager 9/6/2016 3:53:59 PM 1472 (0x05C0)
Failed to run the last action: Error in the task sequence. Execution of task sequence failed.
Unspecified error (Error: 80004005; Source: Windows) TSManager 9/6/2016 3:53:59 PM 1472 (0x05C0)

Execution::enExecutionFail != m_eExecutionResult, HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmanager\tsmanager.cpp,1087) TSManager 9/6/2016 4:09:01 PM 1472 (0x05C0)
Task Sequence Engine failed! Code: enExecutionFail TSManager 9/6/2016 4:09:01 PM 1472 (0x05C0)
Task sequence execution failed with error code 80004005 TSManager 9/6/2016 4:09:01 PM 1472 (0x05C0)
Failed to delete directory 'C:\SMSTaskSequence' TSManager 9/6/2016 4:09:02 PM 1472 (0x05C0)
SetNamedSecurityInfo() failed. TSManager 9/6/2016 4:09:02 PM 1472 (0x05C0)
SetObjectOwner() failed. 0x80070005. TSManager 9/6/2016 4:09:02 PM 1472 (0x05C0)
RemoveFile() failed for C:\SMSTaskSequence\TSEnv.dat. 0x80070005. TSManager 9/6/2016 4:09:02 PM 1472 (0x05C0)
RemoveDirectoryW failed (0x80070091) for C:\SMSTaskSequence TSManager 9/6/2016 4:09:02 PM 1472 (0x05C0)

All replies (16)

_{Thursday, September 22, 2016 1:17 PM ✅Answered}

I think the problem may have been the driver package I got from Dell. They have a package you can download with all the drivers included. I changed to a different model of computer and tested getting some drivers individually the normal way. They seem to have installed. Going to get the rest necessary to finish the install and try it again.

_{Wednesday, September 7, 2016 1:16 PM}

This is an error from Windows setup as the log indicates and thus you need to check the Windows setup log files.

Generally (but not always), this error relates to the product key used during setup. What OS are you deploying and have you specified a product key in the task sequence?

Jason | http://blog.configmgrftw.com | @jasonsandys

_{Wednesday, September 7, 2016 1:23 PM}

Where are those logs located? I am deploying Win7 and didn't specify a product key.

_{Wednesday, September 7, 2016 1:30 PM}

https://technet.microsoft.com/en-us/library/dd744583(v=ws.10).aspx

Jason | http://blog.configmgrftw.com | @jasonsandys

_{Wednesday, September 7, 2016 2:33 PM}

I can't find any of those logs. I assume I will need the $windows.~bt one but I can't find any of them in the command prompt.

EDIT: I did find the Panther folder. It wasn't in alphabetical order. the setuperr.log has nothing in it.

_{Wednesday, September 7, 2016 6:24 PM}

%WINDIR%\Panther is the primary folder to look in. setuperr.log may or may not have anything useful in it. setupact.log is usually more useful. https://support.microsoft.com/en-us/kb/927521 also has some supplementary info about the Windows setup log files and locations.

From memory, error code 31 can also be caused by problems with the unattend.xml file. Are you customizing that file in any way?

Jason | http://blog.configmgrftw.com | @jasonsandys

_{Wednesday, September 7, 2016 9:34 PM}

Here is what is says at the end of the log as far as the red and yellow lines

2016-09-07 09:47:24, Info       [0x0640ae] IBSLIB PublishMessage: Publishing message [Windows Setup could not install one or more boot-critical drivers. To install Windows, make sure that the drivers are valid, and restart the installation.]

2016-09-07 09:47:25, Info                         [SETUP.EXE] Called script [X:\windows\Setup\Scripts\ErrorHandler.cmd] to handle fatal error
2016-09-07 09:47:25, Info       [0x070042] DIAG   CallBack_DiagnosticDataSend: Called with notification for Error published by ErrorHandler
2016-09-07 09:47:25, Warning    [0x070041] DIAG   DiagnosticDataSendWorker: invalid arguments
2016-09-07 09:47:25, Warning               DIAG   CallBack_DiagnosticDataSend: DiagnosticDataSendWorker failed, hresult=0x80070057
2016-09-07 09:47:25, Info       [0x0601d7] IBS    InstallWindows:Error Type = 3211266

I assume I am having driver issues? After some reading it looks like unsigned drivers may be the cause.

Also as for as unattend.xml I haven't customized anything in this deployment. All it is set to do is install windows.

_{Thursday, September 8, 2016 1:29 AM}

Don't focus on just the red and yellow as those aren't necessarily actual errors or warnings and are meaningless out of context even if they are actual warnings or errors.

Jason | http://blog.configmgrftw.com | @jasonsandys

_{Thursday, September 8, 2016 6:08 AM}

I am also pretty sure that error 31 is related to a product key problem ...

Torsten Meringer | http://www.mssccmfaq.de

_{Thursday, September 8, 2016 2:58 PM}

I assume that this is the important line

2016-09-08 08:25:37, Info       [0x0640ae] IBSLIB PublishMessage: Publishing message [Windows Setup could not install one or more boot-critical drivers. To install Windows, make sure that the drivers are valid, and restart the installation.]

_{Thursday, September 8, 2016 7:28 PM}

Have you reviewed this: http://scug.be/sccm/2010/10/28/sccm-osd-issue-with-win7-x64-bit-deployment-on-hp-8740w/

Jason | http://blog.configmgrftw.com | @jasonsandys

_{Monday, September 12, 2016 5:01 PM}

I switched to Apply Driver package. The deployment gets further along but it looks like I still have driver issues. It gets far enough that the Panther folder is now in $WINDOWS.~BT folder.

Seems like I'm on the right track though.

2016-09-12 08:24:06, Info       [0x0602a4] IBS    CallBack_AddDriverPackageIntoDriverStore:Driver package path is [C:\SMSTaskSequence\drivers\10\nusb3hub.inf]
2016-09-12 08:24:06, Info       [0x0602b2] IBS    CallBack_AddDriverPackageIntoDriverStore:Driver package is [critical]
2016-09-12 08:24:06, Info                  IBS    AddDriverPackageIntoDriverStore:Driver package path is [C:\SMSTaskSequence\drivers\10\nusb3hub.inf]
2016-09-12 08:24:06, Info                  IBS    AddDriverPackageIntoDriverStore:Image architecture is [0x9]
2016-09-12 08:24:06, Info                  IBS    AddDriverPackageIntoDriverStore:System root is [C:\Windows]
2016-09-12 08:24:06, Info                  IBS    AddDriverPackageIntoDriverStore:System drive is [C:\
2016-09-12 08:24:07, Warning    [0x0602b1] IBS    AddDriverPackageIntoDriverStore:Failed to add the driver package [C:\SMSTaskSequence\drivers\10\nusb3hub.inf] into driver store. Error code is [0x80070032]
2016-09-12 08:24:07, Error      [0x0602a9] IBS    CallBack_AddDriverPackageIntoDriverStore:Failed to install the driver package [C:\SMSTaskSequence\drivers\10\nusb3hub.inf]. Driver package is [Critical]. Error code is [0x32][gle=0x00000032]
2016-09-12 08:24:07, Error      [0x0602ab] IBS    CallBack_AddDriverPackageIntoDriverStore:An error occurred while installing the driver package [] offline GLE is [0x32][gle=0x00000032]
2016-09-12 08:24:07, Info       [0x0640ae] IBSLIB PublishMessage: Publishing message [Windows installation cannot continue because a required driver could not be installed.]
2016-09-12 08:24:07, Info                         [SETUP.EXE] Called script [X:\windows\Setup\Scripts\ErrorHandler.cmd] to handle fatal error

_{Monday, September 12, 2016 8:18 PM}

Actually it looks like it is failing on every driver install. Whether it's critical or non.

_{Monday, September 19, 2016 2:22 PM}

Actually it looks like it is failing on every driver install. Whether it's critical or non.

Hi,

    What is your boot image version? Have you tried to switch to a new created boot image or the one which has newer version?

Best regards,

Jimmy 

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Monday, September 19, 2016 3:43 PM}

The version for all of my Boot images is 10.0.10586.0 even the default ones made by SCCM.

I am using a boot image I created.

_{Monday, July 1, 2019 9:13 AM}

I also received the error 31, and my issue was that I added a new OS to the TS and it defaulted to the education version in the list. When I changed it to Enterprise version it worked again.

Emil Skibsted Kristensen