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(131.20000000000002, 82%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVJ%3C/text%3E%3C/svg%3E)
Hello,
I have been trying to capture the Windows 11 (23H2) Enterprise Image using MECM Task sequence media. The capture process goes fine and i get the desired WIM image . The issue starts when we try to test the WIM image using Task sequence from MECM. Listed are the issues;
Please let me know if anymore information required.
Here are some suggestions to address the issues you're encountering with your Windows 11 (23H2) Enterprise image captured using MECM Task sequence media:
Long boot time at "Getting Ready" screen:
Driver Optimization: Ensure your captured image includes the latest drivers for all hardware components, especially storage controllers. Outdated or missing drivers can significantly slow down the initialization process.
Unnecessary Startup Services: Review the startup services in your Task sequence and disable any non-essential services that might delay boot. Use tools like Autoruns (https://video2.skills-academy.com/en-us/sysinternals/downloads/autoruns) to identify these services.
Windows Update During Deployment: Consider disabling automatic Windows Update during deployment in your Task sequence. This can eliminate delays caused by update checks and installations. Remember to re-enable updates after deployment for security reasons.
Optimize Disk Performance: In your Task sequence, you can include a step to defragment or trim the captured WIM image. This can improve boot performance on target machines.
Thanks for the suggestions Emad.. The testing i performed is still on a VM so drivers may not be a factor here. Checked each and every Startup services and disabled the ones which are of not so importance. Latest updates are already part of the image and even after disabling the updates step there is no difference. Still trying to figure out what makes it take so long.
Please suggest if you have any other recommendations.
As primary solution, I would recommend to use vanilla install.wim from .iso media and try to automate the applications or other things you manually do before capturing.
As another approach, you could search around what else actions are recommended before capturing image, like not join to domain or disable antivirus, something like this.
Thanks Pavel.. I use the Vanilla Image where we run the debloat script for removing unwanted application, scheduler tasks and services. The machine is in workgroup and not joined to the domain and neither any Antivirus installed on it. Its just the Image deployment that takes too long after it gets installed.
@Vishal Jaitly yea I did capture XP and Windows 7 of beging area image, before I basically stopped doing that. I remember there was like 10 different things which was recommended to do before starting the capture. Also there 2 different aproach, do you want do TS build and capture doing entire process for you or install manually and just launch the capture. Maybe B&C would be safer way in your case if you can automate the app installation. Also, do you see the difference in timing in your enviroment, if you would compare install.wim vs. your capture. wim?