Jump to content

Recommended Posts

Posted (edited)

when I attempt to boot up a newly deployed PC I get a message that says:

Windows could not start because of a computer disk hardware configuration problem.

could not read from the selected boot disk. Check boot path and disk hardware.

Please check the windows documentation about hardware disk configuration and your hardware reference manuals for additional information

Edited by Tripredacus
split from http://www.msfn.org/board/index.php?showtopic=101383&st=100

Posted

You need to provide some additional information. Based upon the actual issue, this thread may yet be moved into a separate forum if this isn't an issue with Windows PE.

Since you posted this as a reply to IcemanND's stickied thread, I am to presume that you followed his guide to create your PE for imaging. I need the following information:

1. What method of booting the WinPE are you using? PXE, UFD, CD?

2. Which Win PE version are you using and which architecture?

3. Did you use the WAIK, OPK or a third party tool (such as BartPE) to create your boot image?

4. Which operating system are you attempting to deploy?

5. What components were installed into your PE, such as WMI, Vista Offline Servicing 1.1, etc?

6. How much memory in the client (MININT) pc, also note if the client uses RAID or AHCI.

Posted

You forgot a question: How are you partitioning and formatting the destination drive? If you are using diskpart post your script/ steps you use with it.

Posted

solved my own problem... I had an issue with my boot.ini file. That has been fixed but now it is constantly rebooting in a cycle. It just barely displays the Windows XP splashscreen before rebooting...

I was under the impression that this process allowed you to take hardware independent backups... is that not true?

Posted

If you followed my guide, all it does is great an image of a system you have built. It has nothing to do with making an image hardware independent. It is just a way to make a "ghost" image of a system so I can be deployed to another system compatible system.

Posted

In order to troubleshoot your issue, you need to invoke the F8 at startup. Then choose "disable automatic restart on system failure" and then it should stop at a BSOD.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...