Boot problem after MDT deployment Windows 10 1803 Enterprise: 0xc0000001 and 0xc0000098
Hi,
We have a case where we need to capture Windows 10 Enterprise from a bare-metal system / physical machine (Dell OptiPlex 5050) and redistribute it with MDT to other OptiPlex 5050 machines. Normally we do this with a VM, but in this case it is impossible, because there are specific drivers and settings done on this machine for very specific hardware peripherals that are connected in a production environment.
The system was initially a Windows 10 1609 build with all the hard- and software requirements needed for the production environment. We would like to refresh the image now and redeploy it to dozens of other machines. The reference computer was upgraded to 1803 and some software components where upgraded (webbrowsers, ...)
The capture worked with MDT and the image was successfully saved to e WIM file on the deployment share in a folder Captures.
The standard procedure was to import the WIM file as a custom Operating System build. There is a specific task sequence created to redistribute this custom image.
The deployment on the target machine (Optiplex 5050) works just fine, but after the action 'Install Operating System' completes, the system reboots twice and displays the message:
Recovery
Your PC couldn't start properly
After multiple tries, the operating system on your PC failed to start, so it needs to be repaired.
Error code: 0xc0000001
Pressing F1 reboots the system and presents the following message:
Revovery
The boot configuration data file doesn't contain valid information for an operating system.
File: \BCD
Error code: 0xc0000098
At first we thought it was a different BIOS version, so that was updated. Secondly we disabled Secure boot in the BIOS.
We also tries several fixes to recreate the boot record by starting restore and using the commands from a startup Windows 10 1709 DVD:
BOOTREC /FIXMBR
BOOTREC /FIXBOOT (access denied)
BOOTREC /REBUILDBCD (total identified Windows installations: 0)
BOOTREC /SCANOS (total identified Windows installations: 0)
At last we entered the Windows PE environment on the destination computer and cleared the disk:
DISKPART> select disk 0
Disk 0 is now the selected disk.
DISKPART> clean
DISKPART> exit
Both systems have a UEFI bios set and secure boot disabled.
Also tried chkdsk and other options, but nothing helps.
Is there any other option we have to try fix this?
Attched you can find the log files.
C3083.zip
TargetComputerLogs.zip
We have a case where we need to capture Windows 10 Enterprise from a bare-metal system / physical machine (Dell OptiPlex 5050) and redistribute it with MDT to other OptiPlex 5050 machines. Normally we do this with a VM, but in this case it is impossible, because there are specific drivers and settings done on this machine for very specific hardware peripherals that are connected in a production environment.
The system was initially a Windows 10 1609 build with all the hard- and software requirements needed for the production environment. We would like to refresh the image now and redeploy it to dozens of other machines. The reference computer was upgraded to 1803 and some software components where upgraded (webbrowsers, ...)
The capture worked with MDT and the image was successfully saved to e WIM file on the deployment share in a folder Captures.
The standard procedure was to import the WIM file as a custom Operating System build. There is a specific task sequence created to redistribute this custom image.
The deployment on the target machine (Optiplex 5050) works just fine, but after the action 'Install Operating System' completes, the system reboots twice and displays the message:
Recovery
Your PC couldn't start properly
After multiple tries, the operating system on your PC failed to start, so it needs to be repaired.
Error code: 0xc0000001
Pressing F1 reboots the system and presents the following message:
Revovery
The boot configuration data file doesn't contain valid information for an operating system.
File: \BCD
Error code: 0xc0000098
At first we thought it was a different BIOS version, so that was updated. Secondly we disabled Secure boot in the BIOS.
We also tries several fixes to recreate the boot record by starting restore and using the commands from a startup Windows 10 1709 DVD:
BOOTREC /FIXMBR
BOOTREC /FIXBOOT (access denied)
BOOTREC /REBUILDBCD (total identified Windows installations: 0)
BOOTREC /SCANOS (total identified Windows installations: 0)
At last we entered the Windows PE environment on the destination computer and cleared the disk:
DISKPART> select disk 0
Disk 0 is now the selected disk.
DISKPART> clean
DISKPART> exit
Both systems have a UEFI bios set and secure boot disabled.
Also tried chkdsk and other options, but nothing helps.
Is there any other option we have to try fix this?
Attched you can find the log files.
C3083.zip
TargetComputerLogs.zip
David Johnson, CD
did you update ADK to the latest version and rebuild your mdt share?
ASKER
Hi David
I updated to the latest ADK and also updated the Deployment share.
Recreating a new deployment share is my last option...
I updated to the latest ADK and also updated the Deployment share.
Recreating a new deployment share is my last option...
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you for the help. The sysprep log entry helped me on the way. After fixing some more issues on Windows Apps that failed the sysprep and editing the unattend.xml from my task sequence (to set the keyboard locale etc), I was finally able to capture the image.
Many thanks getting me on track.
Many thanks getting me on track.