This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(3.2, 0%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGD%3C/text%3E%3C/svg%3E)
Hi,
I am looking for some help troubleshooting the below issue I am encountering when attempting to capture a custom 21H2 image using a MECM Task Sequence, quick recap of my setup...
MECM: 2111 (5.00.9068.1000)
ADK & WinPE: 10.1.22000.1
Base Image: Windows 10 21H2 Enterprise Feb 2022 release (10.0.19044.1526 according to MECM)
If I attempt to capture the image on a VM using EFI partition (Gen1) I get the below error, there is only 1 partition and it has plenty of space available (100GB). This is my standard setup when capturing an image which has worked without any issue for all previous versions of MECM/SCCM and Windows 10 versions since 1809. I have tried both VMWare and Hyper-V VMs, I experience the same error on both.
I am able to successfully capture the image if I use a VM using UEFI partition (Gen2), but, when I import the image into SCCM the OS version is incorrect so I won't be able to Offline Service the image. I am not quite sure where its getting the version from, initially I suspected the WinPE boot image but that's running 10.0.22000.1. Found the below URLs online which are likely related and could still be an existing issue not yet fixed?
https://www.anoopcnair.com/windows-10-21h1-os-version-appears-wrong-sccm/
https://twitter.com/bytenerd/status/1395071115072966656
Thank you for your help!
Hi,
Thanks for posting in Microsoft MECM Q&A forum.
1,The error 0x00000070 means "There is not enough space on the disk". Could you help check the setuperr.log and setupact.log to see if there is any useful information?
2,If possible, could you please try to use the default install.wim file extracted for the ISO image? For more detailed steps, please refer to:
Easy Steps to Deploy Windows 10 21H2 using SCCM | ConfigMgr
Note: This is non-Microsoft link, just for your reference.
Thanks for your time.
Best regards,
Simon
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.
I am using the default install.wim straight from the 21H2 Feb 2022 ISO. Normally prior to performing capture I remove all indexes except enterprise, mount the WIM and DISM language pack files into the image. Just to ensure this process wasn't impacting the capture I tried both the default and the modified WIM, both experience the same issue.
Interestingly, the modified base WIM shows the correct version 10.0.19044.1526 once imported into SCCM, but if I import the base WIM straight from the ISO, select Enterprise index during import, the version reports as 10.0.19041.1526.
I checked both setuperr.log and setupact.log in C:\Windows\Panther\UnattendGC and there was nothing in these logs that stood out, the only entry in the error log was the language pack was missing when using the default wim.
The smsts.log on the other hand is full of "failed to copy" errors during this process, plenty of disk space available but I noted that it is consuming much more disk space than normal. Looking at the path its seem to be stuck in a loop copying the same content? Previously I have been able to capture an image with a 60GB partition without any issue, during my last test run (before I called it and shutdown the VM) it had used 130GB of disk space!
Copy of the smsts.log file attached.
Hi,
Thanks very much for your reply.
From the screenshoot, the size of captured Windows 10 Enterprise image using UEFI partition (Gen2) is 102398 MB, almost 100 GB. If possible, could you use a more large disk to have a try? Thanks again for your time.
Best regards,
Simon
Hi Simon,
That's just the disk configuration at time of capture (VM was configured with 100GB dynamic virtual disk), the size of the actual image is much smaller, the resultant WIM size is exactly 7.2GB. I could work with this capture but as mentioned in my original post the OS version is wrong so Offline Servicing wont work.
The last test I performed I actually bumped it up to 200GB just to see what happened and it just kept consuming disk space, which is where I grabbed the smsts.log file from in my previous post. When you have a moment have a look at the paths in the log file, I am confident it is stuck in some kind of loop that eventually eats up the disk space which result in this error, seems like a bug.
In addition to the above, I thought it would be a good to swap out the WIM with our existing 20H2 base WIM which was used for our last build and capture, this should indicate if the issue is isolated to the WIM or MECM, the exact same issue occurs. A process is backing the disk up to C:_SMSTaskSequence\backup-EFI and it continually loops...
Hi,
Thanks very much for your reply and information.
Yes, as the _SMSTaskSequence\backup-EFI path continually loops in the destination path, it cause that the maximum path length of the destination folder is more than the commonly 255 characters and then fails.
1,Have you checked the "Automatically build mass storage driver list" option in the prepare OS task sequence? If possible, we could select the opposite option to have a try.
2,If possible, we could install the latest hotfix for MECM 2111 to have a try. And you could also submit a new uservoice in Microsoft Endpoint Configuration Manager Feedback:
https://feedbackportal.microsoft.com/feedback/forum/4669adfc-ee1b-ec11-b6e7-0022481f8472
Thanks for your time.
Best regards,
Simon
Hi Simon,
Is this Backup-EFI looping problem a known issue? Is there a workaround or fix?
Hi,
During my research, there is no known issue about this question till now. And I totally understand your caution about the production environment.
As this is a complicated issue, we forum have limited resource. It’s recommended to submit a support case with Microsoft to get better support:
https://support.microsoft.com/en-us/topic/global-customer-service-phone-numbers-c0389ade-5640-e588-8b0e-28de8afeb3f2
I will also keep an eye on this issue, if I find anything useful, I will keep you on posted. Thanks for your kindly understanding.
Best regards,
Simon