Win 7 0xc0000225 boot failure Acer travelmate P245-M
-
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
-
-
Hi, I’m having the same issue but with Windows 8.1 (UEFI)
Windows 7 images (without UEFI) upload and download fine, but with UEFI after imaging with any error my Windows 8.1 show this:
Recovery
Your PC needs to be repaired
A required device isn’t connected or can´t be accessed.
Error Code: 0xc0000225I have the SVN 3603
Thanks! -
Can you update SVN?
Is SecureBoot turned off?
-
@Tom-Elliott I can’t turn off Secure Boot. I can see the option in ASUS BIOS, but it is Gray.
I called ASUS support and they tell me if it is gray and I have no visible button to change it, that means in this model I can’t do that. -
@Bruno-Nogueira Secure Boot is a UEFI thing. See if you can turn off UEFI, then this option shouldn’t be greyed out anymore.
-
@Wayne-Workman I don’t would like to turn off UEFI, there has to be another solution
-
@Bruno-Nogueira Did you even check to see if turning it off allows you to turn off Secure Boot?
-
You should not have to turn off UEFI, but you should (for the time being) be able to disable secure boot.
There’s almost always a way. It’s not that you’re turning off secure boot for the rest of time, but rather for the duration of the imaging process (whether up or down).
Once the imaging process is complete turn Secure boot back on and all should work fine.
If you can’t do this, then I don’t know how to be of any type of help.
You can create the image, and you can deploy the image. You would need to repair every system for things to work though, which I think is what you’re trying NOT to do.
Maybe there’s a hack to fix it, but I don’t know of it yet.
-
@Tom-Elliott Thanks for your help.
I’ve search on the internet and read the user manual but I can’t find the solution.
I will call ASUS support again… -
This particular acer bios does not have a way to disable UEFI. What is does have is an option to try legacy first then default back to UEFI. I know that these were designed with 8.1 in mind and we had them downgraded to 7 from the factory.
@Wayne-Workman I will look at that article.
@Junkhacker What is the difference between the normal upgrade process to 1.2.0 vs upgrading to trunk? Actually I may be asking that question incorrectly due to a lack of install knowledge with fog, but my sysadmin will certainly understand. Why would you assume upgrading to trunk would help? -
https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk
the trunk is the “work in progress” next version of fog. many upgrades and bug fixes are in the new code.
