Win 7 0xc0000225 boot failure Acer travelmate P245-M
-
So far I am unable to properly image my Acer Travelmate P245-M laptops using fog. The image is uploaded and downloaded successfully, however upon reboot after imaging, I get the 0xc0000225 error regarding boot failure and missing devices. The repair feature on the Win 7 x64 DVD does not help. I have run fogprep as well as sysprep with and without the generalized option selected when creating the image with the same results. The system is Windows 7 x64, boot is Legacy, and the hardware between machines is identical. I have not had issues imaging any other Windows machines, just these laptops. The bios is not terribly robust, but Legacy is selected properly. If I am missing some information that might help, please let me know and I will provide it ASAP.
-
Try seeing if your ide mode is set for ide or ahci if it boots after changing this setting you can either leave it on the new setting ot enable the correct driver in windows and switch it back.
-
Or maybe ‘secure boot’ related issue, see here: [url]http://fogproject.org/forum/threads/windows-8-1-fog-1-2-0.12528/[/url]
-
The bios is not terribly robust on this particular Acer model. I only have two options for boot mode, Legacy and UEFI. I do not have an option for IDE mode. I have tried creating the image with and without sysprep, with and without fogrep and every combination therein, but always with Windows 7 64 bit OS. I don’t use sysprep on any of the other images I deal with, and I would prefer not to use it on this image as well. The only lingering doubt in my mind is my current version of fogprep. Is there a specific version of Fogprep for Win 7 64?
-
@NCMikeD said:
I don’t use sysprep on any of the other images I deal with, and I would prefer not to use it on this image as well. The only lingering doubt in my mind is my current version of fogprep. Is there a specific version of Fogprep for Win 7 64?
You don’t have to use FOGPrep. I don’t. It’s not necessary at all.
In fact, I believe it’s somehow become obsolete/legacy. I don’t remember the specifics.
-
Our current version of Fog is 1.1.2. Every other fog image I use works, however they are all 32bit OS’s. This is the first 64 bit OS I have tried and it is acting like the 100mb partition windows creates for boot purposes simply doesn’t exist. I have removed the hard drive from the computer, and scanned it with another computer to verify that the partitions are present and they certainly are. My bios does not allow for me to make any IDE or AHCI modifications; I have dealt with issues relating to that before with our Optiplex 330’s. This Acer Travelmate is the only computer giving me an issue and unfortunately I have an entire pile of these that need Win 7 x64 images on them.
-
Would you be willing to upgrade to 1.2.0 and see if that works?
-
Yes, in fact my System Admin is doing the upgrade as we speak. Is there much of a difference between the two versions of FOG in regards to imaging 64 bit OS’s?
-
I wouldn’t think so,
But I know that when your sys-admin runs the 1.2.0 installer, it’ll pull down the latest kernels and inits, and that will likely help out a lot.
-
Ok, back to the boards. Since I last posted, we have upgraded our fog server to the most current version with the same results. I have tried to create a Windows 7 x86 image at the request of my system admin to see if there is/was a difference and the answer is still no. Same 0xc0000225 error or missing operating system error. I have checked the bios again and it is set to legacy mode and not UEFI. There are no bios updates for my computer. I have modified the image type to resizable, etc and cannot seem to make a difference or any progress. Any other thoughts or avenues I could explore?
-
If the error occurs after you image the machine I really suspect you are having an issue with the hard drive partition table. When I ran into a similar issue we ran the windows repair on the newly imaged pc and then uploaded the fixed image which seemed to solve future issues from then on.
-
Well, I have figured something out today. The laptops which we are using contain one of two 500gb hard disks. One is WD and one is a seagate. Both of which have Advanced Drive Formatting. After doing some research, I am finding out that many cloning tools have issues with the advanced drive formatting. I have just begun the process of dealing with this, so does anyone have any suggestions on how to deal with this and create and image that can be deployed?
-
That’s a question for the Developers.
Only thing I can tell you is to figure out a way to turn it off or undo it.
-
To add a bit more to this equation… If I go the RAW image route with fog, the image clones just fine. Any other option results in failure. The trade off to it working is 3.75hrs of download time with the RAW option. I am dealing with two 500gb hard drives, WD and Seagate, both with advanced formatting and 4k drive sectors. The imagine fails going from identical WD to WD, identical Seagate to Seagate, or WD to Seagate/Seagate to WD. The 4k sector info might seem obvious at this point, but those drives are very new tech compared to the 512 drive sector size we are normally using. I have been able to clone the drives just fine using Reflect, but that is not a viable option for deploying the image as quickly as fog can.
-
@NCMikeD Have you tried to build an image from scratch, yet? See if that works?
You could very quickly install Win7 all by itself with no updates, no apps, no nothing, and just quickly upload and download as resizeable and see if it works or not… if it does, make a full blown image and go that route.
-
fog works fine with 4k drives. what is the partition structure like on the drives you’re trying to image?
-
@Wayne-Workman Yes, I have built an image from scratch several times. The current image I am dealing with is from scratch; Windows 7 64 bit. I have tried 32 and 64 bit thinking there might be a difference, but no luck.
-
@NCMikeD said:
we have upgraded our fog server to the most current version with the same results.
do you mean the latest official version (1.2.0) or the latest svn version, and if the svn version, what exact revision are you at?
-
@Junkhacker We are running latest stable, 1.2.0
-
you may have better luck if you upgrade to trunk