PENDING Failed to run SCCM task sequence 0x80004005

[LOKI]

Hi,

Everything was working fine and the team were building laptops until this morning when we started getting the "failed to run task sequence 0x80004005"

This occurs after typing in my password in the 'Welcome to the Task Sequence Wizard'. I've checked the logs and there is no clear indicator there. The task sequence doesn't even kick off.

I've checked all the usual, time settings, diskpart clean, etc.. I've rebooted the SQL and SCCM server. Restarted the IIS. But then again, nothing has changed from yesterday.

Extract from the log:

D:\_SMSTaskSequence does not exist TSMBootstrap 17/08/2017 10:32:55 1572 (0x0624)
Creating directory D:\_SMSTaskSequence TSMBootstrap 17/08/2017 10:32:55 1572 (0x0624)
Updated security on object D:\_SMSTaskSequence. TSMBootstrap 17/08/2017 10:32:55 1572 (0x0624)
!sBootDevicePath.empty(), HRESULT=80004005 (e:\qfe\nts\sms\framework\tscore\bootvolume.cpp,34) TSMBootstrap 17/08/2017 10:32:55 1572 (0x0624)
System partition not set TSMBootstrap 17/08/2017 10:32:55 1572 (0x0624)
Unable to find the partition that contains the OS boot loaders. Please ensure the hard disks have been properly partitioned
Unspecified error (Error: 80004005; Source: Windows) TSMBootstrap 17/08/2017 10:32:55 1572 (0x0624)
BootVolume::GetCurrent(pBootVolume), HRESULT=80004005 (e:\qfe\nts\sms\framework\tscore\bootimage.cpp,537) TSMBootstrap 17/08/2017 10:32:55 1572 (0x0624)
ValidateSystemPartition(), HRESULT=80004005 (e:\qfe\nts\sms\framework\tscore\bootimage.cpp,1062) TSMBootstrap 17/08/2017 10:32:55 1572 (0x0624)
Failed to prepare the system partition for staging.
Unspecified error (Error: 80004005; Source: Windows) TSMBootstrap 17/08/2017 10:32:55 1572 (0x0624)
BootImage:repareForStaging(sLocalDataPath), HRESULT=80004005 (e:\qfe\nts\sms\framework\tscore\bootimage.cpp,783) TSMBootstrap 17/08/2017 10:32:55 1572 (0x0624)
Failed to validate for boot image staging TSMBootstrap 17/08/2017 10:32:55 1572 (0x0624)
StageBootImage() failed. 0x80004005. TSMBootstrap 17/08/2017 10:32:55 1572 (0x0624)
TS::Boot::BootImage::StageBootImage( pAssociatedWinPE->GetPackageID(), TsBootProgress, pv, hCancelEvent), HRESULT=80004005 (e:\qfe\nts\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,2262) TSMBootstrap 17/08/2017 10:32:55 1572 (0x0624)
Failed to stage WinPE. Code(0x80004005) TSMBootstrap 17/08/2017 10:32:55 1572 (0x0624)
Command line for extension .exe is "%1" %* TSMBootstrap 17/08/2017 10:32:55 1572 (0x0624)
Set command line: "X:\sms\bin\x64\TsProgressUI.exe" /Unregister TSMBootstrap 17/08/2017 10:32:55 1572 (0x0624)
Executing command line: "X:\sms\bin\x64\TsProgressUI.exe" /Unregister TSMBootstrap 17/08/2017 10:32:55 1572 (0x0624)
==========[ TsProgressUI started in process 1892 ]========== TsProgressUI 17/08/2017 10:32:55 1896 (0x0768)
Command line: "X:\sms\bin\x64\TsProgressUI.exe" /Unregister TsProgressUI 17/08/2017 10:32:55 1896 (0x0768)
Unregistering COM classes TsProgressUI 17/08/2017 10:32:55 1896 (0x0768)
Unregistering class objects TsProgressUI 17/08/2017 10:32:55 1896 (0x0768)
Shutdown complete. TsProgressUI 17/08/2017 10:32:55 1896 (0x0768)
Process completed with exit code 0 TSMBootstrap 17/08/2017 10:32:55 1572 (0x0624)
Successfully unregistered TS Progress UI. TSMBootstrap 17/08/2017 10:32:55 1572 (0x0624)
ExecuteSelectedTaskSequence(fpCallbackProc,pv,hCancelEvent), HRESULT=80004005 (e:\qfe\nts\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,1591) TSMBootstrap 17/08/2017 10:32:55 1572 (0x0624)
hrReturn, HRESULT=80004005 (e:\qfe\nts\sms\client\tasksequence\tsmbootstrap\tsmediaresolveprogresspage.cpp,445) TSMBootstrap 17/08/2017 10:32:55 1572 (0x0624)
ThreadToResolveAndExecuteTaskSequence failed. Code(0x80004005) TSMBootstrap 17/08/2017 10:32:55 1572 (0x0624)
ThreadToResolveAndExecuteTaskSequence returned code 0x80004005 TSMBootstrap 17/08/2017 10:32:55 1368 (0x0558)
Setting wizard error: An error occurred while starting the task sequence (0x80004005). For more information, contact your system administrator or helpdesk operator. TSMBootstrap 17/08/2017 10:32:55 1368 (0x0558)
ResolveProgressPage::OnWizardNext() TSMBootstrap 17/08/2017 10:32:55 1368 (0x0558)
Activating Finish Page. TSMBootstrap 17/08/2017 10:32:55 1368 (0x0558)
Loading bitmap TSMBootstrap 17/08/2017 10:32:55 1368 (0x0558)
Executing command line: X:\windows\system32\cmd.exe /k TSBootShell 17/08/2017 10:33:14 300 (0x012C)
The command completed successfully. TSBootShell 17/08/2017 10:33:14 300 (0x012C)
Successfully launched command shell. TSBootShell 17/08/2017 10:33:14 300 (0x012C)

Any help would be greatly appreciated.

 

[Prajwal Desai]

"Unable to find the partition that contains the OS boot loaders. Please ensure the hard disks have been properly partitioned" - Are you sure you used the disk part to clean the HDD and create partitions ?. It shouldn't show the error unless the HDD has got issues.

 

[LOKI]

It does this on every PC. I've rebuilt the same few test laptops over and over for testing. But this morning, I'm getting this error on all of them

 

[LOKI]

It would seem that it no longer works on any of my test PC's despite diskparting, cleaning etc.. However, I just pulled a new laptop out of the box and its working fine. It would appear that my test machines have developed issues at the same time. It was unlikely but, it seems to be the case. Thanks for responding.

 

[Prajwal Desai]

If it's working for new one's and not the old ones, i would suggest you looking up for mac ID's of those old ones and delete them from SCCM console.

 

[LOKI]

We rebuilt another 'known computer'. Removed the object from AD and SCCM devices to make it an 'unknown computer'. But this too throws up an error. I saw this error on the others before I cleaned the disk and tried again. At which point it then gives me the 80004005.

I created a standalone USB Media from the TS which works perfectly. However, using the Boot Media method does not unless the PC us a true unknown computer i.e. brand new out the box.

Does the device information reside anywhere else other than in the Device collection? This is where I have always removed devices from in the past with no issues for rebuilding after.

 

[Prajwal Desai]

The device about the computer exists in SCCM database. You can remove the device entry either from the console or from DB as well.

 

[LOKI]

I have just built a brand new machine and it goes through fine. Removed it from the SCCM Device list and attempted to rebuild. I'm offered up a TS as it is now an unknown machine, however it begins for maybe 2 seconds and Fails to Run Task Sequence. This happens for all PC's that have previously been built using SCCM.

Before now, I could remove the PC from the device list and build over and over. I'm not sure what has changed or what is causing this issue.

 

[Jamios28]

Hey!

did you ever fix this? I have the same issue

 

[LOKI]

No, it is still only working for new hardware. As we are mid deployment, any hardware being reused is having to be built by a standalone version of the media rather than the PXE. I can't quite find the issue.

 

[velaa98]

I had the same problem, in my case, it was fixed by updating Distribution Points for Boot Image i was using in the Task Sequence, i had available a new version of the Windows ADK package.

 

[LOKI]

This was resolved a couple of years ago. Sorry its an old thread. Thanks!

 

[e_sun29]

This was resolved a couple of years ago. Sorry its an old thread. Thanks!

Hi, can you share what was the solutions ? I have the same issue