MDT and Windows 11 - MDT capture fails that there is not enough space

Ray, Rick 11 Reputation points
2022-01-06T13:19:55.547+00:00

I built my golden image in hyper-v as I have been doing for years. Logged into the VM, went to the deploymentshare\scripts\litescript.vbs. It runs and reboots and starts to capture and then fails that there is not enough space. There is 500GB of space on the server it's being captured to and there is 120GB of hard drive space on the VM image.

MDT: 6.3.8456.1000
ADK: 10.1.22000.1

Any Ideas?

Microsoft Deployment Toolkit
Microsoft Deployment Toolkit
A collection of Microsoft tools and documentation for automating desktop and server deployment. Previously known as Microsoft Solution Accelerator for Business Desktop Deployment (BDD).
832 questions
Windows 11
Windows 11
A Microsoft operating system designed for productivity, creativity, and ease of use.
8,276 questions
0 comments No comments
{count} votes

8 answers

Sort by: Most helpful
  1. Amandayou-MSFT 11,046 Reputation points
    2022-01-07T08:18:51.13+00:00

    Hi @Ray, Rick ,

    Please check if there is 500GB in the destination by using checking disk, meanwhile, check if the capture is 120GB on the computer.

    If there is no missing, we could check the logs to see if any error in it, for example, bdd.log, smsts.log by pressing F8.


    If the response is helpful, please click "Accept Answer" and upvote it.
    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.

    0 comments No comments

  2. Ray, Rick 11 Reputation points
    2022-01-07T16:26:37.91+00:00

    163281-bdd.log163208-smsts.log

    BDD Log: Target Partition not big enough: \MININT-6SD5G7N\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #2" LiteTouch 1/7/2022 4:01:22 PM 0 (0x0000)

    SMSTS.Log: Failed to save environment to (80070057)
    Failed to save the current environment block. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
    The parameter is incorrect. (Error: 80070057; Source: Windows)
    Failed to persist execution state. Error 0x(80070057)
    Failed to save execution state and environment to local hard disk

    Failed to run the action: Apply Windows PE.
    There is not enough space on the disk. (Error: 80070070; Source: Windows)
    The execution of the group (Capture Image) has failed and the execution has been aborted. An action failed.
    Operation aborted (Error: 80004004; Source: Windows)
    Failed to run the last action: Apply Windows PE. Execution of task sequence failed.
    There is not enough space on the disk. (Error: 80070070; Source: Windows)
    Task Sequence Engine failed! Code: enExecutionFail
    Task sequence execution failed with error code 80004005

    Thanks for trying to help out, really appreciated.

    0 comments No comments

  3. Amandayou-MSFT 11,046 Reputation points
    2022-01-11T07:10:26.77+00:00

    Hi,

    The cause of this issue could that MDT copies the LiteTouchPE.wim from the deployment share to the first partition (which has a drive letter assigned) in the hard drive to complete the sysprep and capture task sequence. In the above example, the drive letter was assigned as E:\ for 'System Reserved' partition.

    To resolve this particular issue, follow the below steps:

    Do not assign any drive letter to the 'System Reserved' partition, so that MDT can copy to next partition that has the drive letter.
    This issue can also occur if you do not have free space in the C drive, wherein C drive is the first partition.

    Here is the article we could refer to:
    https://learn.microsoft.com/en-us/troubleshoot/windows-server/deployment/sysprep-capture-task-sequence-fails-0x80070070


    If the answer is the right solution, 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.


  4. Ray, Rick 11 Reputation points
    2022-01-18T18:44:43.44+00:00

    Any other ideas?

    0 comments No comments

  5. Ray, Rick 11 Reputation points
    2022-01-19T13:06:02.72+00:00

    That is a screenshot of disk mgmt in the Windows 11 image.

    Here is the screenshot of the capture server. It captures to the C drive:

    166431-image.png

    I would also point out that I have a windows 10 image on the same server in hyper-V that I can capture without issues, doing it the exact same way I am trying to capture the windows 11 image.