Task sequence has failed with the error code 0x800700A1

I see lots of administrators struggling with this error especially when they replace an HDD on a machine and then try to re-image it. Task sequence has failed with the error code 0x800700A1 is an error that also come up when you’re imagining a brand new Virtual Machine.

What does the error mean? 0x800700A1 means BAD_PATHNAME. The reason why you get this error, most of the times, is due the fact that the task sequence isn’t able to find the path because the drive is RAW.


In order to fix this you will have to initialize and format that Hard Drive. If you are in the SCCM’s WinPE environment, simply press F8 to get to the command prompt and type the following:

Be careful when selecting the DISK number. Generally the main HDD is the disk #0, however sometimes that’s not what you want (that’s why I also added an extra step and I’m actually listing all the disks with list disk).



20 thoughts on “Task sequence has failed with the error code 0x800700A1

    1. I think you’re misunderstanding the article? This is an error you get when launching a Task Sequence in SCCM. So before you even install the OS.
      Please expand your issue at least I can understand if it’s linked or not (I think it’s not).

  1. Hi! Wonder is this work for windows 10 installation? i faced the same issues and after i followed all the command and re-run the imaging process and it is still giving me the same error.

    Please advice.

    1. Hi, yep, same steps apply. Did you check the boot method you’re choosing (bios/uefi)? That might lead to these sort of issues.

  2. Trying to create partition primary, I receive an error that reads “DiskPart has encountered an error: The request could not be performed because of an I/O device error. See the system event log for more information.”
    Any Ideas?

    1. Are you sure Disk 0, in your case, is the drive you want to image with SCCM? It seems like you may be targeting the wrong drive. Are you having this error on multiple machines?

    1. Try downloading Windows 10’s latest ISO and see if, when booting up with it, it’s recognized. You may want to try to rebuild your boot image with the latest drivers/WinPE environment.

  3. I am struggling to get a Windows 10 image to load even after doing this. Any ideas on what options to check in the bios to maybe make this successful?

    1. Hi, what about an actual Win 10 ISO to check if that boots up at all? If it does, I’d suggest rebuilding your boot image and make sure the boot method is correct (legacy/uefi).

Leave a Reply

Your email address will not be published. Required fields are marked *