Task Sequence has failed with the error code 0x80070070

Task Sequence has failed with the error code 0x80070070 During the deployment of operating system to a computer in remote site, one of the sccm engineer reported an OSD issue. The OSD error was Task Sequence has failed with the error code 0x80070070. For more information, please contact your system administrator or helpdesk operator. This week has been an OSD troubleshooting week for me. So far I came across more than ten OSD issues this week and sorted it out with lot of effort. I hope this post helps the sccm admins who are facing this issue. The next step was to examine the log files to begin troubleshooting this issue. I asked the sccm engineer to check at what step the TS failed. I also asked to send me the SMSTS.log file.

The task sequence was working fine for all sites. This issue occurred for one of the computers in a remote site. Below is the screenshot which shows the OSD error.

Task Sequence has failed with the error code 0x80070070

Task Sequence has failed with the error code 0x80070070

Upon examining the SMSTS.log file, I found the below errors in the log file.

Error There is not enough space on the disk. (Error: 80070070; Source: Windows)
Unable to apply (0x80070070)
There is not enough space on the disk. (Error: 80070070; Source: Windows). The operating system reported error 2147942512: There is not enough space on the disk.

After looking at the above lines, one can easily say that this issue is related to disk space. Here are the some of the solutions that you can try.

Solution 1 – After looking at the error “There is not enough space on the disk“, ensure that when you deploy the OS, there is enough disk space on the client computer. If the partition is too small for the build then you will surely come across this error.

Solution 2 – If the above solution is not working, you could try this one. If you get this error during a task sequence simply hit F8 to bring up a command window (make sure that command support is enabled on your boot media) and use diskpart (a tool enables you to manage disks, partitions, or volumes by using scripts or direct input at a command prompt) to clean the disk. The following commands should do it (follow the same order):

Diskpart
List disk
Sel disk X
clean
exit

If something else has fixed this issue for you, please share it in comments.

8 Comments

  1. Having the same issue
    Task Sequence has failed with the error code 0x80070070. We recently upgraded boot image to 10.0.18362.1. If I blow away the partitions and rebuild them using disk part then run the image it works. Seems with multiple models of dells that I have tested to far. Any help is appreciated.

    1. SCCM Version 2010

    2. here is a snippet from the smsts log

      Content successfully downloaded at C:_SMSTaskSequencePackagesSUN00005. TSMBootstrap 8/20/2021 12:02:55 PM 1644 (0x066C)
      Found boot image C:_SMSTaskSequencePackagesSUN00005boot.SUN00005.wim TSMBootstrap 8/20/2021 12:02:55 PM 1644 (0x066C)
      Copying boot image from ‘C:_SMSTaskSequencePackagesSUN00005boot.SUN00005.wim’ to local destination ‘C:_SMSTaskSequenceWinPEsourcesboot.wim’… TSMBootstrap 8/20/2021 12:02:55 PM 1644 (0x066C)
      ::CopyFileEx( sImageSourcePath, sImageDestPath, CopyProgressRoutine, pProgressData, &pProgressData->bCancel, 0), HRESULT=80070070 (..bootimage.cpp,850) TSMBootstrap 8/20/2021 12:02:55 PM 1644 (0x066C)
      CopyFileEx (C:_SMSTaskSequencePackagesSUN00005boot.SUN00005.wim, C:_SMSTaskSequenceWinPEsourcesboot.wim) failed. TSMBootstrap 8/20/2021 12:02:55 PM 1644 (0x066C)
      ReleaseSource() for C:_SMSTaskSequencePackagesSUN00005. TSMBootstrap 8/20/2021 12:02:55 PM 1644 (0x066C)
      reference count 1 for the source C:_SMSTaskSequencePackagesSUN00005 before releasing TSMBootstrap 8/20/2021 12:02:55 PM 1644 (0x066C)
      Released the resolved source C:_SMSTaskSequencePackagesSUN00005 TSMBootstrap 8/20/2021 12:02:55 PM 1644 (0x066C)
      StageBootImage() failed. 0x80070070. TSMBootstrap 8/20/2021 12:02:55 PM 1644 (0x066C)
      TS::Boot::BootImage::StageBootImage( pAssociatedWinPE->GetPackageID(), TsBootProgress, pv, hCancelEvent), HRESULT=80070070 (tsmediawizardcontrol.cpp,2313) TSMBootstrap 8/20/2021 12:02:55 PM 1644 (0x066C)
      Failed to stage WinPE. Code(0x80070070) TSMBootstrap 8/20/2021 12:02:55 PM 1644 (0x066C)
      Command line for extension .exe is “%1” %* TSMBootstrap 8/20/2021 12:02:55 PM 1644 (0x066C)
      Set command line: “X:smsbinx64TsProgressUI.exe” /Unregister TSMBootstrap 8/20/2021 12:02:55 PM 1644 (0x066C)
      Executing command line: “X:smsbinx64TsProgressUI.exe” /Unregister with options (0, 0) TSMBootstrap 8/20/2021 12:02:55 PM 1644 (0x066C)
      ==========[ TsProgressUI started in process 1788 ]========== TsProgressUI 8/20/2021 12:02:55 PM 1792 (0x0700)
      Command line: “X:smsbinx64TsProgressUI.exe” /Unregister TsProgressUI 8/20/2021 12:02:55 PM 1792 (0x0700)
      Unregistering COM classes TsProgressUI 8/20/2021 12:02:55 PM 1792 (0x0700)
      Unregistering class objects TsProgressUI 8/20/2021 12:02:55 PM 1792 (0x0700)
      Shutdown complete. TsProgressUI 8/20/2021 12:02:55 PM 1792 (0x0700)
      Process completed with exit code 0 TSMBootstrap 8/20/2021 12:02:55 PM 1644 (0x066C)
      Successfully unregistered Task Sequence Progress UI. TSMBootstrap 8/20/2021 12:02:55 PM 1644 (0x066C)
      ExecuteSelectedTaskSequence(fpCallbackProc,pv,hCancelEvent), HRESULT=80070070 (tsmediawizardcontrol.cpp,1653) TSMBootstrap 8/20/2021 12:02:55 PM 1644 (0x066C)
      hrReturn, HRESULT=80070070 (tsmediaresolveprogresspage.cpp,445) TSMBootstrap 8/20/2021 12:02:55 PM 1644 (0x066C)
      ThreadToResolveAndExecuteTaskSequence failed. Code(0x80070070) TSMBootstrap 8/20/2021 12:02:55 PM 1644 (0x066C)
      ThreadToResolveAndExecuteTaskSequence returned code 0x80070070 TSMBootstrap 8/20/2021 12:02:55 PM 1484 (0x05CC)

  2. Worked! Thanks

  3. Worked! many thanks

  4. Avatar photo Marvin Williams says:

    Thanks worked for me.

  5. Thank you this works

  6. Hi Prajwal, is there any way to automate this process, by adding this as a part of TS in Zero-Touch Deployment ?

Comments are closed.