I'm using SysPrep for years, currently with Windows 10 22H2 19045.4529 and Windows 11 23H2 22631.3737 I have no problems at all. Today I've tried to prepare deploy image using Windows 11 24H2 26100.1150. Steps: Start fresh install of Windows 11 24H2 26100.1150. then enter in audit mode (CTRL+SHIFT+F3) do things (Firefox, Thunderbird, some tweaking etc) run sysprep /oobe /generalize /shutdown capture the image, deploy to test device System boots ok, WU works well (updates and drivers), then I've enable BitLocker then reboot and Windows was unable to boot (system repair starts) I've tried the same steps 1-4 using Windows 11 23H2 22631.3737 iso image and after enabling BitLocker I did restart and everything works fine (Windows boot normally) Next I went back to fresh instance Windows 11 24H2 26100.1150 and after audit I did 1-4 steps, but in 3rd step sysprep without "/generalize" (sysprep /oobe /shutdown) and I repeated test (enabling BitLocker in deployed image) and this time Windows 11 24H2 boots normally, but SID of this instance remains unchanged (lack of /generalize step). I think that there is a bug in sysprep generalize step in 24H2 26100.1150 regards bitlocker subsystem (the /generalize step did something that render bitlocker unusable) Regards Chris

Found the same issue but I have a workaround. There is an issue with the BCD configuration. After the Sysprep, I've added these 3 lines in the script WINDIR%\Setup\Scripts\SetupComplete.cmd : bcdedit -set {current} osdevice partition=C: bcdedit -set {current} device partition=C: bcdedit -set {memdiag} device partition=\Device\HarddiskVolume1 Of course, the lines can be a bit different depending on your disk configuration. This leaves me with a strong impression that this version of Win 11 has not been tested properly.

Windows 11 24H2 26100.1150 SysPrep /generalize breaks BitLocker functionality

Accepted answer

BARRAT Christophe 95 Reputation points

2024-07-30T10:46:11+00:00
Found the same issue but I have a workaround. There is an issue with the BCD configuration.

After the Sysprep, I've added these 3 lines in the script WINDIR%\Setup\Scripts\SetupComplete.cmd :

bcdedit -set {current} osdevice partition=C:

bcdedit -set {current} device partition=C:

bcdedit -set {memdiag} device partition=\Device\HarddiskVolume1

Of course, the lines can be a bit different depending on your disk configuration.

This leaves me with a strong impression that this version of Win 11 has not been tested properly.
Please sign in to rate this answer.

4 people found this answer helpful.
Krzysztof Gajda 50 Reputation points

2024-07-30T18:15:57.2833333+00:00

Ok. I will try Your solution, using the "RunSynchronousCommand" in unattended.xml, but I share Your point of view, that this version of W11 has some weird bugs, that QC team didn't catch (or they didn't aware).

Krzysztof Gajda 50 Reputation points

2024-08-02T21:28:12.0966667+00:00

It works!

Only these two are needed:

bcdedit -set {current} osdevice partition=C:

bcdedit -set {current} device partition=C:

The "after sysprep" bad settings are:

device locate=\WINDOWS\system32\winload.efi

osdevice locate=\WINDOWS

which should be both pointing to "partition=C:"

device partition=C:

osdevice partition=C:

Paul Cormier 0 Reputation points

2024-10-10T20:12:00.2866667+00:00

I just wanted to thank you for this post. I have wasted several days trying to get to the bottom of why any machine I apply this latest image to ends up in recovery mode the first reboot after enabling BitLocker. I owe you the proverbial beer. Thanks so much for posting.

Jeroen Houben 0 Reputation points

2024-10-17T08:28:40.7+00:00

This is a life saver. Thanks so much!!!!!!!

Juan Carlos Linares 0 Reputation points

2024-10-18T03:31:44.2966667+00:00

could you help me how to build the file "SetupComplete.cmd" with only the two lines:
bcdedit -set {current} osdevice partition=C:

bcdedit -set {current} device partition=C:

and make it run after "sysprep" ??

Krzysztof Gajda 50 Reputation points

2024-10-18T05:23:08.14+00:00

IMHO better is to edit unattend.xml, then go to "specialize" section and insert
"RunSynchronous" like this:

`<settings pass="specialize"> <component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <RunSynchronous> <RunSynchronousCommand wcm:action="add"> <Description>BCD fix 1</Description> <Order>1</Order> <Path>bcdedit -set {current} osdevice partition=C:</Path> </RunSynchronousCommand> <RunSynchronousCommand wcm:action="add"> <Description>BCD fix 2</Description> <Order>2</Order> <Path>bcdedit -set {current} device partition=C:</Path> </RunSynchronousCommand> </RunSynchronous> </settings>`
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Windows 11 24H2 26100.1150 SysPrep /generalize breaks BitLocker functionality

0 additional answers

Your answer