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(28.799999999999997, 28.999999999999996%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
Hello,
I have 2 virtual machines running with VMWare workstation (also tried with proxmox with same issue).
VM1 = Windows Server 2025 with services DHCP, WDS & MDT
VM2 = Windows 11 Pro 24H2
I setup my Windows server 2025 VM in order to be able to deploy and capture image thru MDT.
My problem is when I'm initiating my Capture Task Sequence, once VM restart to start sysprep, I finally get this error:
IF I'm connecting a real computer thru ethernet, I'm able to get the .WIM file on the \Captures folder of my DeploymentShare folder on my server.
If I'm trying with a Windows 10 Virtual machine, (I create a new task Sequence similar to W11 one except the OS selected) and I am able to capture the .WIM from it :
I have tried many things so far BUT was not able to solve this issue.
Can someone support to get this done successfuly?
Thanks in advance
Hello,
I add the VMware drivers for the disk to winPE, now I can see my disk of 64GB BUT looks like the drive letter has changed from one partition to the other
After syprep/capture error:
And has it should be:
I have tried to re-assign C drive letter correctly after VM restart and before sysprep/WIM capture BUT now get this issue :( :(
Any Idea?
![](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(150.4, 92%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EXM%3C/text%3E%3C/svg%3E)
Hi,
Please check the setupact.log and bdd.log files for any specific errors that might give more insight into what's going wrong.
Set up a fresh Windows Server 2025 (without services DHCP, WDS & MDT) virtual machine to use as a template for capturing the image.
![](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(166.4, 66%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAM%3C/text%3E%3C/svg%3E)
Hi MinaDave,
The drive letter is dynamically assigned, that is, it only works in the current running OS. The partition is static unless if we change it. When the OS, either PE or full OS, starts, it assigns drive letter to a partition (or not). So, it's normal that the drive letter is different within different OS.
In addition, I noticed that the drive size is 63GB, however, for win11, the minimum storage requirement is 64GB. Could you resize it to, say, 100GB and try again.
If something is wrong, try uploading the log files.
Regards,
Alex
So, it's normal that the drive letter is different within different OS
The problem is not the letter assigned BUT the Partition which receive a letter
I noticed that the drive size is 63GB,
My virtual drive is 64Go / 63GB ... I'll try with 100Go one in case of...
Hi,
So, it's normal that the drive letter is different within different OS.
The problem is not that drive letter is changed...the problem is the wrong Partition receive a letter
I noticed that the drive size is 63GB
My drive is 64Go or 63Gb.
In any case, I create a new VM with 100 Go drive and exactly same error, I have to manually assign a drive letter with diskpart for the 100Go drive And same ZTi Error at hte end.
Here is the BDD.log file : BDD.log
And the other one: setupact.log
Thanks in advance for your help