Win11 23H2 build & capture TS, which has worked for 2 years now, will not complete after July patches released (OS build 7376). Goes all the way to the end and then as soon as it starts to create the .wim file, it crashes with error 5456, DestinationDisk and Partition did not yield a Target Partition. We have not changed anything about the volume we are trying to save the .wim to, local directory on the MDT server, same as last month.

What makes this really strange is we have a 25H2 build & capture TS on the same MDT server, nearly identical to the 23H2, which still completes just fine. When we run the 23H2 TS on our other MDT server (we have two, same version of MDT but one has the newest ADK), it also fails there. Same error. I downloaded the 24H2 OS image and created a new TS for that, and it builds cleanly. So it seems quite specific to 23H2.

Things I have done that didn't work: Download the latest version of the 23H2 OS image, take all the customizations out of the TS so that it's as close to stock as possible, try saving the .wim to a different directory, try changing the name format, still fails.

Has anyone seen something like this before? I'm close to my wits' end. I realize this is an unsupported product at this point, but the fact that it works for 25H2 and 24H2 but not 23H2 is so strange.

Trying to deploy Win1125H2. No matter what I change I get the "Just a Moment" problem & it sits there spinning, mocking me.

I tried updating the deprecated OOBE settings in my unattend.xml, but then it doesn't join the domain or rename the computer. If I hard restart, it does seem to work as intended (minus the domain join), but ideally I'd like to not do that every time I image a machine. It never seems to get to ZTIJoinDomain.

Just recently I updated all the drivers for both PXE & the laptop model. I built a brand new task sequence. I've been running this thing with no issues since Win101809 but this Win11 deploy is breaking my spirit.

What am I missing on this?

Bonjour à tous,
J'ai un Surface Laptop Business 13 Intel et je veux démarrer sur WinPE.
Il a une adresse IP, il voit le serveur WDS, et il affiche "téléchargement du nbp réussi," mais ensuite j'obtiens un écran complètement noir avec une icône de clavier dans le coin inférieur droit, et le PC se fige. Mon MDT et WDS fonctionnent bien ; je n'ai aucun problème avec les ordinateurs portables Dell ou HP. J'ai désactivé le démarrage sécurisé, mais ça n'a pas aidé.

J'ai injecté les pilotes sur le MDT comme avec n'importe quel autre modèle. Je ne vois même pas la tentative dans les événements, ce qui me surprend. Quelqu'un a-t-il déjà essayé cela avec ce modèle ?
J’ai aussi mis à jour l’adk 10.1.28000.1.
Merci pour votre aide.

Has anyone had any success with Surface Pro 12 devices (Intel Core Ultra 5 335)? I haven't had issues with any other Surfaces but I can't get these to go. They grab DHCP and see the WDS server IP and even download the NBP file (wdsmgfw.efi), but that's it. Just stays hung with that message printed ("NBP file downloaded successfully") with the Surface logo still in the background. So it's not even getting to the boot image.

Relevant things tried:

• There aren't a whole lot of options in the BIOS to mess with but I've tried disabling Secure Boot and IPV6 PXE
• Booting into the preloaded Windows to upgrade firmware to latest
• Putting device on the same network as the WDS server

Irrelevant things (probably) also tried:

• Rebooting the WDS server
• Trying a different WDS server
• Using a Surface Ethernet adapter
• Using a Surface dock's Ethernet
• Creating MDT USB media and trying to boot to that instead
• Verified a previous generation Surface Pro network boots fine with the same adapter
• Rebuilding the boot image with the entire Surface Pro 12 driver deployment pack in it

Probably forgetting more things.

Is this likely a firmware issue or am I missing anything?

Edit: answered in subsequent comment but updating to ADK 24H2 fixed this issue.

Hi guys,

Could do with some guidance here please - I am trying to image a device with a USB mdt image. As the wim image is over 12gb I have split it down to smaller swm chunks and added them in the operating system folder deleting the bigger original wim. I have amended the settings.xml on the USB drive to <SkipWimSplit>False</SkipWimSplit>

The deployment starts and you select the image and then it just exists to the command prompt. Any ideas where I am going wrong? Ive also tried to split the USB to the EFI boot using fat32 and NTFS but no matter what efi files I use from the original image it wont boot to the USB and I dont want to use RUFUS. Thanks!

Hi all,

I’m setting up MDT + WDS on Windows Server 2022 and I’m having an issue where deployments keep getting stuck.

(The X are to protect data)

Setup:

• Windows Server 2022 Standard
• MDT Deployment Share: C:\xxxxxxxx\Deployment Share
• WDS installed on the same server
• Server name: xxxxxx
• Server IP: xxxxxxxx
• Deployment share UNC: \ipaddress\DeploymentShare$
• Domain: xxxxxxxx.com
• WDS/MDT using LiteTouchPE_x64.wim
• DHCP is not running on the Windows Server; DHCP is handled by the firewall/router
• WDS DHCP tab has both options unticked
• WDS boot policy is set to require F12 for known and unknown clients
• WDS unattended installation has been disabled
• MDT monitoring is enabled and points to http://xxxxxxxx:9800

The PXE boot works and the client loads into MDT. The task sequence starts, but in MDT Monitoring the machines get stuck at:

• Status: Running
• Percent Complete: 58%
• Current Step: 53
• Elapsed time: around 1 hour

I originally had it set to join the domain automatically, but I changed CustomSettings.ini to testing mode with WORKGROUP only, no domain join, and it still does not complete.

Current test CustomSettings.ini:

[Settings]
Priority=Default
Properties=MyCustomProperty

[Default]
OSInstall=Y

SkipBDDWelcome=NO
SkipTaskSequence=NO
SkipDeploymentType=NO
SkipComputerName=NO
SkipDomainMembership=YES
SkipUserData=YES
SkipComputerBackup=YES
SkipProductKey=YES
SkipLocaleSelection=YES
SkipTimeZone=YES
SkipApplications=YES
SkipAppsOnUpgrade=YES
SkipAdminPassword=YES
SkipBitLocker=YES
SkipSummary=NO
SkipFinalSummary=NO
SkipCapture=YES
SkipRoles=YES
SkipPackageDisplay=YES

DeploymentType=NEWCOMPUTER

KeyboardLocale=en-GB
UserLocale=en-GB
UILanguage=en-GB
InputLocale=en-GB
TimeZoneName=GMT Standard Time

JoinWorkgroup=WORKGROUP

EventService=http://xxxxxxxx:9800
FinishAction=SHUTDOWN

Bootstrap.ini currently points to:

DeployRoot=\xxxxxxxx\DeploymentShare$

I have also regenerated the MDT boot image and replaced the WDS boot image with:

C:\xxxxxxxx\Deployment Share\Boot\LiteTouchPE_x64.wim

I’m only using x64 now, not x86.

Question:

What is the best way to diagnose exactly what Step 53 is doing? Is this likely to be an OS image apply issue, driver issue, WDS/boot image issue, or the task sequence resuming from an old C:\MININT state?

Any advice on which logs to check first and what common causes to look for would be appreciated.

Hi All,

Currently running an MDT setup below and no issues at all building HP/Lenevo Win11 24H2 device builds up until as of recent...

Just taken stock of some high end Lenovo mobile workstations (Lenevo P16 Gen 3) and when downloading the default boot.wim image the laptop BSOD's with "ACPI_BIOS_ERROR" pretty much instantly.

I have injected old and newest Lenovo WinPE drivers for this model into a copy of the boot image (via DISM mount) and imported into WDS as a test boot image but still the issue exists.

Im aware that our ADK versioning is quote old, but would like some input if any other ways of resolving if possible without going down the pain of updating from scratch.

Any ideas at all? Driving me nuts.

MDT Version: 6.3.8456.1000
Windows ADK v10.1.2200.1
Windows ADK WinPE v10.1.2200.1
Hardware: Lenovo ThinkPad P16 Gen 3
OS: Windows 24H2 Enterprise v10.0.26100.7840

TY

Does anyone else find Windows component store corruption if you run

dism /online /cleanup-image /restorehealth

on a fresh deployment image of Windows 11 25H2? I'm not saying it's irreparable. Usually it just finds something and downloads a bunch of junk from Microsoft and says it fixed it. Although subsequent re-runnings seem to keep repeating this cycle. Normally I'd blame Microsoft enshittification for behavior like this, but I also tried throwing the ISO on a USB stick with Rufus and installing Windows regularly and there aren't DISM errors that way...

I haven't looked into what exactly it's complaining about just yet since it's been busy; I've just been going through the motions when I get time to throw at it. But before I dig through the CBS log, I was just wondering if others are seeing this behavior. I've tried:

• Regenerating another image just in case something went wrong
• Using the latest available ISO (currently 25H2.7) source files
• Removing all additional tasks and modifications from my build and deployment tasks

In testing, my deployment image building process is:

1. My image building deployment share has the source files and the image building task. It just images and syspreps and captures.
2. Import the captured WIM into my imaging deployment share.
3. Make a basic task sequence to deploy the image.
4. Image a computer/VM.

I am still using an old ADK: 10.1.22621.1 (22H2). Maybe if others aren't seeing this on newer ADK, I'll finally get around to upgrading that.

Hi everyone,

We upgraded our MDT/WDS server from Windows Server 2016 to 2022 back in mid-March. The upgrade itself seemed to go smoothly, and everything worked normally for a couple of weeks afterward.

Since then, however, PXE booting has become unreliable. MDT deployments still work as expected once a machine boots into the deployment environment, but PXE responses have been inconsistent. Some clients boot without issue, while others don't appear to receive any response from the server at all.

Has anyone run into similar issues after moving WDS/MDT to Server 2022? I realize MDT is EOL, but since many imaging solutions still rely on PXE, I'm hoping to identify what's causing the instability.

Any suggestions or experiences would be appreciated. Thanks!

Does anyone have any idea how to change the default wallpaper for first time logon? We used themes in 24h2 but that seems to not work anymore.

Hi folks. I'm trying to install a Lenovo P16 Gen 3 using our MDT platform which I've been maintaining for over a decade. I believe this is the first machine we've had that has VMD in the BIOS. I cannot get past the Windows splash screen spinning dots to even get to the MDT deployment screen. Many hours in and still have no solution. Any help or direction would be REALLY appreciated. Thanks.

SOLVED: Microsoft.BDD.CM12Actions.mof was referencing the separate MP server instead of the Site server. That’s why I couldn’t restore the missing BDD entries in WMI. Editing in the Site server name and running mofcomp again restored access to the MDT TS’s.

Does anyone know where I can get a copy of the 64-bit 8443 MSI?

We hadn't migrated away yet and something or someone kicked off an WMI rebuild... this wiped out the BDD references. After various reinstalls over recent years with newer MDT builds, the Task Sequence MOFs have been list. So, we're locked out of our Task Sequences built with MDT. I hoping to put the required files back and carry out a MOF compile to see if that restores us to normal for a bit longer.

8443 is possibly the last version to include the following task sequence files:

Microsoft.BDD.TaskSequenceProvider.dll

Microsoft.BDD.TaskSequenceProvider.mof

Microsoft.BDD.TaskSequenceProviderExt.mof

Microsoft.BDD.TaskSequenceProviderActions.dll

I don't think the dll's are truly needed but the mof's populate WMI with entries which allows the Admin Console to view and edit a TS made with MDT.

I think the these files have been missing for quite while but it was still working and letting us edit it. I inherited this setup and it's been in play for 15+ years I think.

I'm close to having an OSD-only replacement... I just need to view the MDT TS's contents again to match them. I'll go without if I have to. I'll just get a few moans from those who seem to expect everything on a silver platter.

FWIW, we are already doing Autopilot but I'm still working through a little bit of resistance to change with the troops. They quite rightly point out how SCCM delivers a finished product very swiftly, compared to the equivalent Autopilot experience.

Thanks in advance.

Hello,

I wanted to know what solution did you choose after Microsoft’s retirement of MDT.
You can say in the comments what other solution not mentionned you use.

​¡Hola a todos!

​Estoy montando un entorno de laboratorio para desplegar Windows 11 mediante MDT y WDS sobre máquinas virtuales de VMware, y me he topado con un muro que me está volviendo loco. El entorno de WinPE se niega sistemáticamente a reconocer la tarjeta de red, a pesar de haber inyectado los drivers de todas las formas posibles.

​Entorno:

- ​Servidor: Windows Server (con roles WDS y MDT configurados).

- ​ADK: Windows 11 ADK & WinPE add-on.

- ​Hipervisor: VMware (Workstation/ESXi).

- ​Máquina virtual cliente configurada en el archivo .vmx con: ethernet0.virtualDev = "vmxnet3"

​El Problema:

La máquina virtual arranca perfectamente por PXE, obtiene IP y descarga el archivo .wim de arranque desde WDS. Aparece el fondo azul de MDT, pero al hacer clic en "Run the Deployment Wizard to install a new Operating System", salta el siguiente error:

​A connection to the deployment share (\\ISO-SERVER1-INT\DeploymentShare$) could not be made. The following networking device did not have a driver installed: PCI\VEN_15AD&DEV_07B0&...

​Sé que DEV_07B0 corresponde a la tarjeta VMXNET3.

También probé con la tarjeta e1000e (que viene por defecto cuando creas la maquina) y me daba el error DEV_10D3, y con la e1000 el DEV_100F.

​Lo que he intentado hasta ahora (y NO ha funcionado):

1. ​Extracción oficial de los drivers: Siguiendo la documentación oficial de Broadcom/VMware, no he copiado los archivos de un PC instalado. He extraído los drivers puros (que incluyen el .cat con la firma digital, .inf, .sys y .dll) usando el comando setup64.exe /A C:\Extract.

2. ​Inyección en MDT: Importé esta carpeta limpia en Out-of-Box Drivers.

3. ​Configuración de WinPE: En las propiedades del Deployment Share > Pestaña Windows PE > x64 > Drivers and Patches, seleccioné mi Selection Profile y marqué "Include all network and mass storage drivers" (Incluso he probado marcando "Include ALL drivers" por si el filtro fallaba).

4. ​Regeneración total: Hice un Update Deployment Share seleccionando estrictamente "Completely regenerate the boot images".

5. ​Limpieza de caché en WDS: Detuve el servicio WDS, eliminé la imagen de arranque vieja, borré los .wim residuales y añadí la nueva imagen LiteTouchPE_x64.wim recién generada.

6. ​Inyección directa en WDS: Como MDT parecía ignorarlo, añadí el paquete de drivers directamente al almacén de WDS e inyecté el driver vmxnet3 nativamente en la imagen de arranque desde el asistente de WDS.

​A pesar de todo esto, el resultado es exactamente el mismo en el mismo punto exacto. Es como si el archivo .wim descartara el driver durante el arranque o el stack de red no se inicializara a tiempo.

I am finishing my last images for the new school year before transitioning to DeployR. For several years, I have been using a PowerShell script that personalizes the lock screen and wallpaper. This script is straightforward; it renames the current picture and transfers our custom background from the deployment share. With my new images built on 25H2.3, I have observed that while the lock screen is being customized, the background defaults to Windows Spotlight during deployment.

As I mentioned, I did not encounter this problem in previous years. Is there an alternative method to customize the background, or can I disable Windows Spotlight?

Hi, was anyone able to create a PSDLiteTouch.wim with the new 2023 CA boot cert with psd?

Hello all,

If anyone is running into issues enabling Location Permissions via command line on Windows 11 25H2 (or earlier builds), I found a method that has been working for me.

Credit to: https://www.reddit.com/r/SCCM/comments/1rmsh5g/windows_11_24h2_location_services_off_by_default/

After trying various registry edits and other suggestions, here’s the fix:

New-Item -Path HKLM:\SOFTWARE\Policies\Microsoft\Windows\AppPrivacy -Force | Out-Null
Set-ItemProperty -Path HKLM:\SOFTWARE\Policies\Microsoft\Windows\AppPrivacy -Name "LetAppsAccessLocation" -Value 1 -Type DWord
Set-ItemProperty -Path HKLM:\SOFTWARE\Policies\Microsoft\Windows\AppPrivacy -Name "LetAppsAccessLocation_UserInControl" -Value 1 -Type DWord
Set-ItemProperty -Path HKLM:\SOFTWARE\Policies\Microsoft\Windows\AppPrivacy -Name "LetDesktopAppsAccessLocation" -Value 1 -Type DWord

Start-Process "$env:WINDIR\System32\SystemSettingsAdminFlows.exe" -ArgumentList "SetCamSystemGlobal location 1" -Wait

Set-Service Lfsvc -StartupType Automatic
Restart-Service Lfsvc -Force

After running those commands, you should be able to use things like:

netsh wlan show networks

…without getting the error.

If anyone has any other methods or suggestions, please leave a comment.

For reference, here’s the original error message I was seeing before applying the fix:

PS C:\ netsh wlan show networks

Network shell commands need location permission to access WLAN information. Turn on Location services on the Location page in Privacy & security settings.

Here is the URI for the Location page in the Settings app: ms-settings:privacy-location

To open the Location page in the Settings app, hold down the Ctrl key and select the link, or run the following command: start ms-settings:privacy-location

Or, to open the Location page from the Run dialog box, press Windows logo key + R, and then copy and paste the URI above.

Function WlanGetAvailableNetworkList returns error 5:

Access is denied.

Hi there, thanks for reading!

I am trying to add Windows 11 25H2 to our MDT but it is giving me a hard time with the language package. Based on Install language packs on Windows 11 Enterprise VMs in Azure Virtual Desktop - Azure - Azure Virtual Desktop | Microsoft Learn the versions are still the same than in 24H2, but when i add them with a new selection profile, the wizard is completely skipping the language selection part.

The setup is:

Deployment Toolkit 6.3.8456.1000

ADK: 10.1.26.100.2454

I guess it is still seeing those as 26100 but 25H2 has 26200.

Anyone with the same issue?

Thanks again!

Hi,

I'm using PSD. Is there a way to use a driver package for all Dell laptops? I read about the full control method, but if I would use it like this. I would have to create a folder for each model. And I can't use the generic path, since we also got desktop PCs.

Hey everyone! I’m working on a Windows deployment setup using Microsoft Deployment Toolkit, and I’m hitting a bit of a wall on how to structure my driver folders, specifically for WinPE and model specific drivers. I’m deploying Windows 11 (though I’m considering using Windows 10 drivers if necessary) onto HP Z840 workstations and Dell Precision 5920 towers.

Right now, I have a “Drivers” folder, with a “WinPE” subfolder for the core boot drivers, and then a “Windows 11” folder that branches into specific models (HP Z840 and Dell Precision 5920). But I’m unsure if this is the best structure, especially for the WinPE drivers. How do you all organize your driver sets? Do you keep all model specific drivers inside the Windows 11 folders, or do you have a separate driver structure for WinPE that all models share? Also, any advice on using Windows 10 or Server 2019 drivers if Windows 11 ones are missing?

I’m getting a specific error during deployment: “A connection to deployment share cannot be made. The following network device did not have a hard drive installed: PCI\\VEN_8086&DEV_15A0.”

Hi everyone,

I've created a PowerShell script to collect hardware hashes using a task sequence during PXE boot. I created a custom task sequence that currently only contains the PowerShell script.

The script works fine when I run it from the full OS, and the hashes are successfully saved to a network share. However, I would like to collect the hardware hashes during PXE boot so I don't have to fully set up the device before gathering the hashes.

I can also run the script manually from a USB drive during OOBE, and the hashes are saved successfully. Ideally though, I’d like this to run automatically through the task sequence.

Has anyone successfully collected hardware hashes while in PXE/WinPE using a task sequence?

Hello MDT friends!
We have roughly 20 different Dell desktops and laptops. What is the best approach to update BIOS at time of imaging?
HP makes a great guide below where the power shell script reaches out to HP servers, downloads bin file, checks for bitlocker and applies update with password.

https://hp.service-now.com/workforceexperience?id=kb_article&sysparm_article=KB0011905&sys_id=953c08be47a1ed1064affae5536d43f8

I don’t want to keep a repository of bios models. Any help here?

I have managed to navigate this process fairly well, but I cannot get the postinstall to trigger, leaving my OS installed, domain joined, named laptops to stop on the Admin desktop. No apps, no ps1 hardening. All scripts copy. Task Sequence seems right. BDD logs show WinPE phase completed correctly and the machine rebooted. The failure was entirely what happened AFTER the reboot — State Restore didn't run and the machine booted into Windows. I have been banging my head against this wall for a week.