Task Sequence has failed with error code 0x800700A1 "Use Toolkit Package"

Boopathi Subramaniam 3,281 Reputation points
2021-12-09T20:19:20.737+00:00

Hello Team,

I am getting the below message after adding a new driver package in the task sequence.
156320-capture.jpg

Kindly advise whether any specific drivers in the driver package create this issue.

Microsoft Configuration Manager Deployment
Microsoft Configuration Manager Deployment
Microsoft Configuration Manager: An integrated solution for for managing large groups of personal computers and servers.Deployment: The process of delivering, assembling, and maintaining a particular version of a software system at a site.
926 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. AllenLiu-MSFT 42,351 Reputation points Microsoft Vendor
    2021-12-10T01:48:30.203+00:00

    Hi, @Boopathi Subramaniam
    Thank you for posting in Microsoft Q&A forum.

    The error 0x800700A1 translates "The specified path is invalid."
    The reason you get this error is if the task sequence cannot find the path because the drive is RAW. In this case, it’s always recommended to format the disk partition before deploying Windows Image to help us avoid unwanted issues.

    You may try to format the disk partition follow this article:
    https://www.anoopcnair.com/sccm-task-sequence-has-failed-with-the-error-code-0x800700a1/
    (Please note: Information posted in the given link is hosted by a third party. Microsoft does not guarantee the accuracy and effectiveness of information.)


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


    1 person found this answer helpful.

  2. Chad G. Ardoff 5 Reputation points
    2023-11-07T17:03:11.5766667+00:00

    Not sure if this helps, but sometimes you cannot reach the disk due to a driver issue. Could be nothing more than a swap from RAID to AHCI. Most of the time you will find that AHCI works consistently.

    1 person found this answer helpful.