1,544 questions
In the end, I had to manually mount the OS drive onto another VM and manually capture the image using DISM to a system.wim file - which I could then import into MDT
Windows MDT Capture of Windows 11 VM fails (disk partitioning issue?)
![](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(201.6, 71%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGM%3C/text%3E%3C/svg%3E)
Gary Mansell
136
Reputation points
I have a Win11 "Gold" image VM (which was originally created in Azure) that I have downloaded to on-prem Hyper-V, and I am now trying to capture using a standard Win11 System Prep Task Sequence, but it fails every time at the "Apply Windows PE" task:
It seems to fail (exception) at this point in the LTIApply.wsf script (as the "Boot Drive not found, attempting recovery option (Win8+Sysprep scenario)..." message is the last one in the bdd.log before the exception):
Which seems to be when it is trying to find the boot drive (is this the hidden EFI partition, or the Windows partition)?
Here is the disk partitioning layout of the VM - can you see any reasons why it should crash at this point?
Also, what is it trying to do at this point in the Capture sequence? As far as I can make out it is trying to find the Recovery partition so that it can extract the MDT WinPE.WIM into the Recovery partition, before rebooting into it and then doing the Dism capture of the image to the Deployment Share - is this correct?
Windows for business | Windows Client for IT Pros | Devices and deployment | Set up, install, or upgrade
{count} votes
-
Gary Mansell 136 Reputation points
2023-08-21T08:11:33.8666667+00:00 Hi, is there someone out there who can put me straight on what is going wrong with this?
Sign in to comment
3 answers
Sort by: Most helpful
-
-
AllenLiu-MSFT 49,316 Reputation points Microsoft External Staff2023-08-17T02:57:20.72+00:00 Hi, @Gary Mansell
Thank you for posting in Microsoft Q&A forum.
Based on the provided context, the issue seems to be related to the LTIApply.wsf script failing to find the boot folder on the system partition, which causes the Sysprep and Capture task sequence to fail. The disk partitioning layout seems to be correct, so the issue might be related to the script failing to find the hidden EFI partition.
You may try to edit the LTIApply.wsf script to check for the existence of the boot folder on the system partition before running the takeown.exe command to change ownership on the folder.
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 "Add comment".
-
Gary Mansell 136 Reputation points
2023-08-17T08:43:57.81+00:00 Thanks very much for getting back to me, but after making the edits to the files that you suggest - the same error still occurs.
I include the LTIApply.log in it's entirety in the hope that this might shed more light on the problem that I am encountering and would very much appreciate any further advice you could give on this issue.
-
Gary Mansell 136 Reputation points
2023-08-17T08:45:24.3366667+00:00 The screenshot I took above may not be legible, so here is a text dump of the file:
<![LOG[Property PE is now = ]LOG]!><time="09:28:56.000+000" date="08-17-2023" component="LTIApply" context="" type="1" thread="" file="LTIApply"> <![LOG[Property STAGE is now = ]LOG]!><time="09:28:56.000+000" date="08-17-2023" component="LTIApply" context="" type="1" thread="" file="LTIApply"> <![LOG[Microsoft Deployment Toolkit version: 6.3.8456.1000]LOG]!><time="09:28:56.000+000" date="08-17-2023" component="LTIApply" context="" type="1" thread="" file="LTIApply"> <![LOG[The task sequencer log is located at C:\Users\Administrator\AppData\Local\Temp\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log.]LOG]!><time="09:28:56.000+000" date="08-17-2023" component="LTIApply" context="" type="1" thread="" file="LTIApply"> <![LOG[Will boot into Windows PE architecture x64 to match OS being deployed.]LOG]!><time="09:28:56.000+000" date="08-17-2023" component="LTIApply" context="" type="1" thread="" file="LTIApply"> <![LOG[TargetOS is the current SystemDrive]LOG]!><time="09:28:56.000+000" date="08-17-2023" component="LTIApply" context="" type="1" thread="" file="LTIApply"> <![LOG[Get the Boot Drive.]LOG]!><time="09:28:56.000+000" date="08-17-2023" component="LTIApply" context="" type="1" thread="" file="LTIApply"> <![LOG[The current autorun setting is - ]LOG]!><time="09:28:56.000+000" date="08-17-2023" component="LTIApply" context="" type="1" thread="" file="LTIApply"> <![LOG[Disabling Autorun]LOG]!><time="09:28:56.000+000" date="08-17-2023" component="LTIApply" context="" type="1" thread="" file="LTIApply"> <![LOG[Find the boot drive (if any) [True] [10.0.22621] [False]]LOG]!><time="09:28:56.000+000" date="08-17-2023" component="LTIApply" context="" type="1" thread="" file="LTIApply"> <![LOG[New ZTIDisk : \\CADPC-WIN11\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="09:28:56.000+000" date="08-17-2023" component="LTIApply" context="" type="1" thread="" file="LTIApply"> <![LOG[DISKPART + Select Disk 0]LOG]!><time="09:28:56.000+000" date="08-17-2023" component="LTIApply" context="" type="1" thread="" file="LTIApply"> <![LOG[DISKPART + Select Partition 2]LOG]!><time="09:28:56.000+000" date="08-17-2023" component="LTIApply" context="" type="1" thread="" file="LTIApply"> <![LOG[DISKPART + Assign]LOG]!><time="09:28:56.000+000" date="08-17-2023" component="LTIApply" context="" type="1" thread="" file="LTIApply"> <![LOG[DISKPART + Exit]LOG]!><time="09:28:56.000+000" date="08-17-2023" component="LTIApply" context="" type="1" thread="" file="LTIApply"> <![LOG[About to run command: cscript.exe //nologo "\\STC-MDT13\DeploymentShare$\Scripts\ztiRunCommandHidden.wsf" "DiskPart.exe /s C:\Users\ADMINI~1.CAD\AppData\Local\Temp\rad47652.tmp"]LOG]!><time="09:28:56.000+000" date="08-17-2023" component="LTIApply" context="" type="1" thread="" file="LTIApply"> <![LOG[Command has returned: 0]LOG]!><time="09:28:58.000+000" date="08-17-2023" component="LTIApply" context="" type="1" thread="" file="LTIApply"> <![LOG[No boot drives found. None.]LOG]!><time="09:30:00.000+000" date="08-17-2023" component="LTIApply" context="" type="1" thread="" file="LTIApply"> <![LOG[Reverting autorun setting to - 0]LOG]!><time="09:30:00.000+000" date="08-17-2023" component="LTIApply" context="" type="1" thread="" file="LTIApply"> <![LOG[Boot Drive not found, attempting recovery option (Win8+Sysprep scenario)...]LOG]!><time="09:30:00.000+000" date="08-17-2023" component="LTIApply" context="" type="1" thread="" file="LTIApply"> <![LOG[Found Recovery option: GPT 0 3 1 EFI 99 \\?\Volume{dc694235-27c5-19ee-97a8-000d3a481dc3} 63]LOG]!><time="09:30:00.000+000" date="08-17-2023" component="LTIApply" context="" type="1" thread="" file="LTIApply"> <![LOG[ZTI ERROR - Unhandled error returned by LTIApply: Invalid procedure call or argument (5)]LOG]!><time="09:30:00.000+000" date="08-17-2023" component="LTIApply" context="" type="3" thread="" file="LTIApply"> <![LOG[Unexpected response from web service: 400 Bad Request <?xml version="1.0" encoding="utf-8"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <title>Request Error</title> <style>BODY { color: #000000; background-color: white; font-family: Verdana; margin-left: 0px; margin-top: 0px; } #content { margin-left: 30px; font-size: .70em; padding-bottom: 2em; } A:link { color: #336699; font-weight: bold; text-decoration: underline; } A:visited { color: #6699cc; font-weight: bold; text-decoration: underline; } A:active { color: #336699; font-weight: bold; text-decoration: underline; } .heading1 { background-color: #003366; border-bottom: #336699 6px solid; color: #ffffff; font-family: Tahoma; font-size: 26px; font-weight: normal;margin: 0em 0em 10px -20px; padding-bottom: 8px; padding-left: 30px;padding-top: 16px;} pre { font-size:small; background-color: #e5e5cc; padding: 5px; font-family: Courier New; margin-top: 0px; border: 1px #f0f0e0 solid; white-space: pre-wrap; white-space: -pre-wrap; word-wrap: break-word; } table { border-collapse: collapse; border-spacing: 0px; font-family: Verdana;} table th { border-right: 2px white solid; border-bottom: 2px white solid; font-weight: bold; background-color: #cecf9c;} table td { border-right: 2px white solid; border-bottom: 2px white solid; background-color: #e5e5cc;}</style> </head> <body> <div id="content"> <p class="heading1">Request Error</p> <p>The server encountered an error processing the request. The exception message is 'The type initializer for 'ExtentPlaceholderCreator' threw an exception.'. See server logs for more details. The exception stack trace is: </p> <p> at System.Data.Mapping.Update.Internal.Propagator.ExtentPlaceholderCreator.GetPropagatorResultForPrimitiveType(PrimitiveType primitiveType, PropagatorResult& result) at System.Data.Mapping.Update.Internal.Propagator.ExtentPlaceholderCreator.Visit(EdmMember node) at System.Data.Mapping.Update.Internal.Propagator.ExtentPlaceholderCreator.CreateEntitySetPlaceholder(EntitySet entitySet) at System.Data.Mapping.Update.Internal.Propagator.Visit(DbScanExpression node) at System.Data.Mapping.Update.Internal.Propagator.Visit(DbProjectExpression node) at System.Data.Mapping.Update.Internal.UpdateTranslator.<ProduceDynamicCommands>d__44.MoveNext() at System.Linq.Enumerable.<ConcatIterator>d__59`1.MoveNext() at System.Data.Mapping.Update.Internal.UpdateCommandOrderer..ctor(IEnumerable`1 commands, UpdateTranslator translator) at System.Data.Mapping.Update.Internal.UpdateTranslator.ProduceCommands() at System.Data.Mapping.Update.Internal.UpdateTranslator.Update(IEntityStateManager stateManager, IEntityAdapter adapter) at System.Data.Objects.ObjectContext.SaveChanges(SaveOptions options) at Microsoft.BDD.MonitorService.MonitorEventService.NextID(MDT_MonitorEntities monitorEntities) at Microsoft.BDD.MonitorService.MonitorEventService.PostEvent(String uniqueId, String computerName, String messageId, String severity, String stepName, Int16 currentStep, Int16 totalSteps, String id, String message, String dartIP, String dartPort, String dartTicket, String vmHost, String vmName) at SyncInvokePostEvent(Object , Object[] , Object[] ) at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs) at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc) at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc) at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage11(MessageRpc& rpc) at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)</p> </div> </body> </html>]LOG]!><time="09:30:00.000+000" date="08-17-2023" component="LTIApply" context="" type="1" thread="" file="LTIApply"> <![LOG[Event 41002 sent: ZTI ERROR - Unhandled error returned by LTIApply: Invalid procedure call or argument (5)]LOG]!><time="09:30:00.000+000" date="08-17-2023" component="LTIApply" context="" type="1" thread="" file="LTIApply"> -
AllenLiu-MSFT 49,316 Reputation points Microsoft External Staff
2023-08-21T08:56:56.2233333+00:00 Have we tried to capture a Windows 10 image? MDT is not supported with Windows 11.
https://learn.microsoft.com/en-us/mem/configmgr/mdt/release-notes#supported-platforms
-
Gary Mansell 136 Reputation points
2023-08-21T09:06:32.1666667+00:00 Hi thanks for getting back to me - it is this specific image that I am having trouble with (one that originated in Azure and I want to use on-prem as it has a lot of applications installed and configured in it).
I can capture other Win10 and Win11 images successfully (and deploy them using my MDT System) - so it's not a general issue.
Sign in to comment -
-
Gary Mansell 136 Reputation points
2023-08-24T07:20:37.1866667+00:00 Still really keen to get some help on this... does anyone have any other suggestions they could help me with?
I can confirm that I can both deploy and capture other Win10 and Win11 images to/from my Hyper-V environment using my MDT System. It just seems to be an issue with this Win11 master image VM (that originated from Azure).
In my experimenting, I did come across a problem trying to deploy to a Hyper-V VM with vTPM enabled in Hyper-V, but I don't have this enabled in the problem VM now (I did before as it had v-TPM enabled in Azure). I don't think that this, or Secure Boot can be the issue - as other VMs deploy and capture OK with these same settings.
As AllenLiu-MSFT seems to suggest, it is failing trying to find the boot partition (I think, to install Win-PE into - is this correct)? So, are there labels, or flags, attribs etc that need to be set on the hidden EFI partition, maybe? Or, are there folders/files that the LTIApply script is looking for that are not there?
Am a bit stuck, as need to use the same Master image in Azure and on-prem and need to find a way to exchange back and forth. I don't want to have to try and maintain two identical images manually (one in Azure and one on-prem) - this would be a nightmare as my images are very complex.
Any help, ideas (or even suggestions as to what I can try next) would be appreciated.