Failing full client restore (CD or USB key), RestoreCDInit.exe - Application Error, 0xc0000025 at location 0xff43b477
30 września 2011 04:03
you'll find a description of my issue, re-capped below.
Here's the exact error message:
RestoreCDInit.exe - Application Error
The exception Cannot Continue
Windows cannot continue from this exception.
(0xc0000025) occured in the application at location 0xff43b477.
Click on OK to terminate the program
Using USB key created from the server itself from the Dashboard, Computers and backup tab, selecting "additional client computer backup tasks", "tools" and then creating a recover USB key.
Same error for the PC restore CDs made from:
The system with the issue is a ThinkPad W520, with the BIOS 1.30 at factory defaults (AHCI SATA internal drive). This same boot media works fine on other systems in my home.
30 września 2011 10:21Update BIOS?
30 września 2011 19:38
Try disabling the wifi adapter - maybe the restore CD is getting confused by seeing two NICs?
8 października 2011 20:59Same error with me, mine is a desktop pc - no wifi and latest BIOS. Interestingly though i have AHCI configured SSD and ive noticed other people also AHCI configured disks.......wondering if there is a connection. Will continue hunting and i currently have no HTPC with backups that are useless.
9 października 2011 11:39
Cracked it. I found it to be boot related. I tested the USB stick in another PC and it worked perfectly. When i boot from USB pen im given 2 options.
1 is USB...<my usb pen name>
2 is UEFI USB <my usb pen name>
Booting from UEFI fixed the problem and the program ran ok. Loaded my NIC drivers and hey presto the restore kicked off.
Very strange but at least its a solution. Hope it helps everybody out there.
- Zaproponowany jako odpowiedź przez richsmif 10 października 2011 02:24
4 stycznia 2012 01:54
This thread was about the only solution that came up when I ran into this problem this morning restoring after an SSD upgrade. Hopefully someone else might find it helpful.
The USB drive I had worked fine on 3 other machines, but not this new desktop (ASUS motherboard, Z68 chipset). I tried the UEFI and normal USB boot modes, same error on both. Only way I could get it to restore was to download and and burn a CD with the restore ISO. Booting from that CD worked fine, no errors.
So it looks like there is some problem between UEFI USB booting and the WHS restore software...Or maybe it's just this particular motherboard or BIOS? (it's a brand new board, and there's no newer BIOS available)
4 stycznia 2012 02:48ModeratorWindows Home Server 2011 doesn't support UEFI boot computers. (It's in the documentation...)
I'm not on the WHS team, I just post a lot. :)
1 kwietnia 2012 13:14
Same exact error with me.
I have AHCI configured SSD as OS disk but have used the USB restore twice in the last month with no problem to restore until now.
- I needed to use my USB restore because my BIOS did not see the SSD (Vertex ll 240GB) which has been working faultlessly for 6 Months.
- The USB restore gave me the error as reported above "exactly" with the same hex addresses.
- When I restarted using 32 bit instead of 64 bit it worked and I restored my boot drive to an old Maxtor HHD.
- When I made a new USB restore using a new USB using the tools on the server and tried it, I got the exact same error.
- When I used the original USB in a different Computer, it worked fine in 64bit mode
- I then removed the SSD, looked at it on a USB cradle, it was fine, replaced it and it booted?
Something going on but I don't know what, suspect it must something that has been loaded recently!!!!!!!!!
Mine is 3 year old asus MB so no UEFI involved.
Have since tried the CD and boots straight into both 32 and 64 WHS restore
Peter R Ferguson
- Zmodyfikowany przez Poppapete 1 kwietnia 2012 21:03
5 kwietnia 2012 16:00
Is there any solution to this? I have tried to restore a laptop (Windows 7 x64) that has just got a replacement disk (old one failed). I have tried using a bootable USB disk created today. I have also tried using the bootable restore CD that came with the product. In both cases, the restore continues for about 50 minutes and then 5 minutes from when it says it will complte - bang! ClientRestoreWizard_Fresh.exe fails with 0xC0000025 at address 0xff6fd66d.
My WHS 2011 system is fully up to date with Microsoft fixes. The network is fine as it wouldn't have restored data for the first 50 or so minutes.
Can anyone give me a solution (that doesn't depend on removing the disk drive, buying some enclosure and restoring from another PC)?
How can WHS 2011 be of any use if all it can do is backup but can not restore? In the UK, it would fail the Trade Description Act as not being fit for purpose.
BTW - Someone has mentioned that booting from the USB and using the UEFI USB boot worked for them. However, this laptop has no options to set (UEFI or not UEFI) and it wouldn't apply to the bootable CD.
Thanks in advance.
11 czerwca 2012 00:50Bump this. I have tried everything mentioned in this thread, and nothing works. This is a seriously bad problem.
11 czerwca 2012 02:06
OK, so here is the fix I am trying. I have a friend with an older PC. I pulled his HDD and put mine in. I am restoring my system using the old PC, and I will put the HDD back in the new PC when the restore is done.
I hope that works, but seriously, this is such a serious flaw, MS should have to disclose it on the software's box that "this product will not allow system restores for many newer PCs." Anything less smells like a lawsuit to me.
11 czerwca 2012 15:19
That may be fine for you, my problem was with a laptop. Not sure I could have installed that disk in another laptop (of a different make) or a desktop and still be able to restore it.
Please let us know if it worked.
6 lipca 2012 16:16
Sorry for the tardy reply. Yes, putting the HDD into an older PC worked just fine on the first try. The problem is definitely that MS does not support UEFI PCs, which is an extremely serious flaw/bug in the software.
Frankly, I can't image how MS can get away with selling this product, to me this is a strong indication that WHS is dead.
6 lipca 2012 18:10
Not a bug if it's stated in the documentation as mentioned by Ken above. UEFI was not available when WHS2011 was built (it's based on Server 2008 R2 code).
Yes, WHS is indeed dead as announced by Microsoft regarding Server 2012
Phil P.S. If you find my comment helpful or if it answers your question, please mark it as such.