Computer going to automatic repair after enabling bitlocker (sysprepped machine)

Question

I am using hyper V to create the template image (basically just os + updates) then use sysprep with the below command

@echo off
cd c:\windows\system32\sysprep
sysprep.exe /generalize /oobe /shutdown /unattend:C:\Sysprep\unattend.xml

after the computer is switched off I am using FOG to capture the image.

Then I will have to disable secure boot from the computer to be able to boot from the network, I would then rename the computer and join to domain (using scripts) and login with a domain user, then reboot the computer and re enable the secure boot (to be able to run the bitlocker)

However after loggin into the domain user and I enable the bitlocker, after it is completed and reboot the laptop I am getting the computer to boot into the automatic repair

• I have tried putting the unattend.xml on a usb and installed os using the pendrive, renamed computer and joined to the domain it worked ok. So something in the sysprep is causing all this.

I have been on this for 3 days and havent found a solution yet and am out of ideas :/

Answer 1

Partition is there however its in an unknown format :S

Answer 2

Also I am trying to check the log however the folder isnt there.

managed only to get to system32\logfiles\

Answer 3

Issue seems to be the below, before encryption partition is visible however after the bitlocker and a reboot the partition is not there anymore.

Not sure its not visible because its encrypted :S

Answer 4

Good morning,

I have the exact same problem.
After running sysprep, the computer restarts.
I enable bitlocker and I get an error message: "The path specified in the Boot Configuration Data (BCD) for an application protected by BitLocker Drive Encryption Integrity is incorrect. Check and fix your BCD settings, then try again"

I restart my computer to activate secure boot.

I launch bitlocker activation.
Activation result: Ok 

I restart my computer and at that moment, I have automatic repair running in a loop.
It is no longer possible to start the system.

This happens every time I activate my secureboot to be able to launch bitlocker after sysprep.

Without sysprep everything works fine.

Does anyone have a solution to this problem?

Answer 5

Issue seems to be related to sysprep because even if I use sysprep (without any scripts) I am still getting same issue.