ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Windows failed to start message when trying to boot to .wim file delivered by iPXE

book

Article ID: 173166

calendar_today

Updated On:

Products

Ghost Solution Suite

Issue/Introduction

While trying to boot to a boot.wim file delivered by iPXE a Windows Boot Manager error is given on the screen and the machine fails to load to WinPE.

Windows failed to start. A recent hardware or software change might be the cause. To fix the problem:

1. Insert your Windows installation disc and restart your computer.

2. Choose your language settings, and then click "Next."

3. Click "Repair your computer."

If you do not have this disc, contact your system administrator or computer manufacturer for assistance.

Status: 0x000000f

Info: An unexpected error has occurred.

Cause

Unknown

Environment

Ghost Solution Suite 3.3

iPXE installed

Resolution

Workaround at this time is to boot to .wim file delivered by iPXE with the secure boot option disabled.

-------
Symantec has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned in this article. Symantec is committed to product quality and satisfied customers.

There are currently no plans to address this issue by way of a patch or hotfix in the current or previous versions of the software at the present time. This issue may be resolved in a future major revision of the software at a later time. However, this particular issue is not currently scheduled for any release.  If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Symantec Sales representative or the Symantec Sales group to discuss these concerns.  For information on how to contact Symantec Sales, please refer to the following Web site:

http://www.symantec.com/business/index.jsp

Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.

Attachments