For years and years have used ghost 7.5 or 11 to do standard disk to disk copies of our custom image to build pcs with. Our customer has recently updated the build to now use windows PE. After doing a disk to disk clone we get 0xc000000f "The boot selection failed because a required device is inaccessible."

I have not had much luck in finding any support in regards to this and was hoping someone here could shine a light on what we are missing.

The way you have presented the information--it's hard to know if *you* are the one doing the cloning--or if it's the *customer* is doing the cloning. You state:

Quote:

For years and years have used ghost 7.5 or 11 to do standard disk to disk copies of our custom image to build pcs with.

That sounds like *you* are doing the cloning.

The reason I ask--are you the one who is *in control* of what's being done--or is the customer the one who gets to *tinker* with their system, and controls what occurs when doing cloning?

Having been answering questions on this forum for years--I have noted that it is very hard to understand what an individual is *actually* doing--they *assume* we here know exactly all the things they have done (or not done) as if we have been watching over their shoulder all along. And, when someone is reporting issues from a *third* party, the information becomes even harder to follow!

Okay--off the *soap box*--

Quote:

After doing a disk to disk clone we get 0xc000000f "The boot selection failed because a required device is inaccessible."

What OS are you cloning?

Depending on what OS you are cloning--have you *generalized* the boot information so the OS does not look for a specific HDD ID before it will boot? Ghost 7.5 probably will not understand the newer boot information that is now used on Vista and Win7. Ghost 11.?? probably is *aware* of the newer boot information--but may not handle things correctly if you have created a *custom* setup.

Have you done a *boot repair* on the newly cloned HDD using the (I'm assuming) Windows installation CD?

Are you using *SysPrep* to create a master image that is then cloned to a new system?

The way you have presented the information--it's hard to know if *you* are the one doing the cloning--or if it's the *customer* is doing the cloning. You state:

Quote:

For years and years have used ghost 7.5 or 11 to do standard disk to disk copies of our custom image to build pcs with.

That sounds like *you* are doing the cloning.

The reason I ask--are you the one who is *in control* of what's being done--or is the customer the one who gets to *tinker* with their system, and controls what occurs when doing cloning?

Having been answering questions on this forum for years--I have noted that it is very hard to understand what an individual is *actually* doing--they *assume* we here know exactly all the things they have done (or not done) as if we have been watching over their shoulder all along. And, when someone is reporting issues from a *third* party, the information becomes even harder to follow!

Okay--off the *soap box*--

Quote:

After doing a disk to disk clone we get 0xc000000f "The boot selection failed because a required device is inaccessible."

What OS are you cloning?

Depending on what OS you are cloning--have you *generalized* the boot information so the OS does not look for a specific HDD ID before it will boot? Ghost 7.5 probably will not understand the newer boot information that is now used on Vista and Win7. Ghost 11.?? probably is *aware* of the newer boot information--but may not handle things correctly if you have created a *custom* setup.

Have you done a *boot repair* on the newly cloned HDD using the (I'm assuming) Windows installation CD?

Are you using *SysPrep* to create a master image that is then cloned to a new system?

To answer your question. We clone the image, but it is updated by our client. So we control the cloning, but the image is tinkered on by the customer. The image loads windows PE and then dowloads the OS and installs updates. This is for windows XP and windows 7. Really this is irrelevant as I am only attempting to clone the windows PE image that installs XP or 7. If you have a version of Ghost that would accomplish this I am all ears. 7.5 is what we were using, and the 11 version is one my colleague used to see if that would correct the issue. So far no luck.

Really this is irrelevant as I am only attempting to clone the windows PE image that installs XP or 7

I looked at that statement and said *What?!*. This does not resemble anything you said in your first post-----------(wait for it!)---------until-------- I read the thread title very slowly:

Quote:

Using ghost 11 to clone disk to disk window PE image..

If you do a Google search on the error you mention in the first post--it's all about Win7 boot errors. And, in your first post--all you talk about is doing *disk to disk copies of our custom image to build pcs*. It sure sounded like you were talking about a boot error after the image of the OS had been transferred to your client's system!

But, that's not what we're talking about at all--changes everything-----

Quote:

If you have a version of Ghost that would accomplish this I am all ears.

I don't think we're talking about a Ghost issue here--I'm more suspicious that's it's a WinPE syntax error--either in how it was built or how it's being loaded!

So, I'm going to try to *pull more teeth*:

Quote:

Our customer has recently updated the build to now use windows PE

Did *you* create the WinPE--or did your *customer* create it?

Does the *source* WinPE boot and work without errors?

If *Yes*, so you are now trying to transfer (*After doing a disk to disk clone*) that working WinPE to another system, and then boot that system with that good working WinPE and you get that boot error when trying to load WinPE?

How exactly are you attempting to use WinPE? Is it being placed on the system's HDD and booted from there? Or, is it on a bootable optical disc and booted from there? Or, are you booting from an *ISO* image of a WinPE optical disc--I think you use some sort of Linux based program that allows the loading and booting from *ISO* images. Or, are you using Ghost Console to remotely boot the system?

Customer created the image, It is loaded to the source via USB key using windows PE. WinPE is loaded on the HDD boots and loads the OS from there. Source functions ok, but after disk to disk copy, destination gives error when attempting to boot. it takes much longer to load via USB or DVD so had used this in the past till they updated to windows PE.

The last link seems like it might be relevant. I am in the field so its hard for me to work on stuff like this. I will forward it to some of my colleagues and see if it makes a difference.

WinPE is loaded on the HDD boots and loads the OS from there. Source functions ok, but after disk to disk copy, destination gives error when attempting to boot.

How is WinPE created and *loaded on the HDD*? I suspect the problem lies here. I don't use WinPE booted from the HDD--so no expert, but....

Is WinPE created in such a way that it is part of a multi-partitioned HDD? And, WinPE has its own partition and the image is being loaded to a separate OS partition?

Which version of WinPE is being used? On the *source* system that boots correctly, is there a *boot loader* that takes place where you select to either boot to WinPE's partition, or to the Windows OS partition?

What version of Windows is being used on the *source* system that boots correctly where WinPE is located (this information may hold clues as to what boot loader is involved)?

So, where am I going with this? If WinPE is sharing a HDD with other partitions and can be selected during the boot process--if the boot loader is based on Win7, for instance--the default behavior of Win7 is to create a boot loader that points to specific HDD ID's for the various partitions. If you try to *clone* an image of a Win7 system to another HDD--the new HDD's partition(s) will not have the unique ID of the souce HDD--and booting will fail--and the *same* or similar boot failure message which you have been getting will occur saying the boot device was not found.

The boot information can be *generalized* so the boot process does not look for a specific unique partition ID, and then the boot loader can be cloned to other HDDs and booting will proceed successfully.

There might be two things.The port of disk is changed from ide to the latest port.The PE based Windows is different.Or common disk clone APP will settle the problem easily.Have a look...http://www.pcdisktools.com/pcdiskclone.htm