Windows 10: Is there anything wrong with the wim capture for Windows 11 24H2? Is it supported?

Hello there,We typically use a captured WIM for our environment based on Windows 11 23H2 and have done this many times without any issues. However, since the 24H2 update, we've observed some strange behavior. After running sysprep and booting into WinPE to capture the WIM, the letter C: because we pass /capturedir:C:\ is assigned to a different partition. When we checked the partitioning with diskpart, there was no letter assigned to the actual C: drive where Windows was installed!Later, I assigned a different letter G: to that partition and successfully captured the WIM using the command:di

:)

 

Factory reset Windows 11 24H2 (build 26100.863)

Hi, I am Dave, I will help you with this.

There are no currently listed problems resetting version 24H2 of Windows 11 and no specific steps you need to perform, are you experiencing any problems with that insider build that is causing you to perform a Windows reset?

 

MDT Skips .wim creation step during capture

Hi All,

As mentioned in the title;

During the MDT Capture wizard every steps works as intended (OS installation, apps, sysprep), however it skips the "Create wim" step completely and continues with a shutdown. Any idea how to fix this?

I have logs available if needed.

MDT is being done within Hyper-V.

W10 22H2.iso

 

Is it possible to sysprep a wim file after it is captured?

I know what I am supposed to do: Run sysprep and then capture the image.

I know that you can do a lot of offline work on a WIM file using DISM. I know you can mount, edit, and unmount a WIM.

Is there some creative way to perform the sysprep steps on a WIM file that was captured from a production system?

I've looked far and wide but I've only seen people talking about the Microsoft way of doing things.