After deploying a Windows 7 SP1 image through a deploy image task (using Sysprep and with or without Deployanywhere) the system boots into production and fails with the error, "Windows failed to load

book

Article ID: 156457

calendar_today

Updated On:

Products

Deployment Solution

Issue/Introduction

After deploying a Windows 7 SP1 image through a deploy image task (using Sysprep and with or without Deployanywhere selected) the system boots into production and fails with the error, "Windows failed to load because the system registry file is missing, or corrupt"

Windows failed to load because the system registry file is missing or corrupt

Cause

A normal installation of Windows 7 places two partitions on the hard disk: System Reserved and the Windows Boot partition (c:\). However, Windows 7 installation may not have the System Reserved Partition (SRP) and may also have additional partitions upon which the Windows Boot Partition is installed.

Because DS 7.1 doesn't know which partition actually contains the '.\windows\panther' directory, the Deploy Image task copies the tokenized unattend.xml to all
partitions using the firm command 'firm copy d1p*'. NOTE: The asterisk instructs FIRM to copy the unattend file to all partitions. Because of a bug in the FIRM executable when the 'unattend.xml' is copied to the Windows Drive (c:\), it is sometimes left in an invalid state. E.g. locked, not correct number of bytes, etc. When Sysprep attempts to read the bad 'unattend.xml' file it fails with the error noted in the problem description.

Resolution

To resolve this issue please copy the file '<>' that is attached to the KB to the root of the partition/drive where Windows is installed- in most instances this will be 'c:\'- and capture an image.

When the image is deployed on another system, the Deploy Image task will search for the presence of the file and will copy the 'unattend.xml' only to the partition where Windows is installed.

 

 


Applies To

DS 7.1 sp2 build 2316

Attachments

bcdosdevice.cfg get_app