Using the latest Clonezilla Live Stable (clonezilla-live-1.2.4-28-686.zip) on a USB key, I restored a Vista image into /dev/sda1 from /dev/sda2 (a.k.a. /dev/partimage). When done, I used fdisk to check that /dev/sda1 is NTFS and marked as active. FWIW, before using the regular version of Clonezilla, I tried the Ubuntu stable version, but it didn't work right (/dev/sda1 became /dev/sda5), so I used fdisk to delete and recreate /dev/sda1 and set its type as NTFS before trying again, with the regular version this time.
When rebooting, I get the following error:
"File: \Windows\system32\winload.exe
Status: 0xC0000225
Info: the selected entry could not be loaded because the application might be missing or corrupt."
Does someone know what to do? Should I change one of the switches before restoring the image?
Thank you for any hint.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2010-04-04
FWIW, I then ran "ntfsfix /dev/sda1" which says it succeeded… but I still get the same error when booting up.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2010-04-05
It appears that the solution is the same as for when cloning Windows7 and getting error 0xc00000e: Start Windows, edit the Registry, head for the HKLM\System\MountedDevices\ section, remove all entries except "Default", and then save this partition using CloneZilla.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The short solution described above can be dangerous to the original system.
Just clearing HKLM\System\MountedDevices\ can render the original system unbootable if your system's partitions are arranged unusually, e.g. the partition given the drive letter c: is not the first partition or not the active one.
The symptoms I got, both on the cloned system and the original, was that after starting,
(a) many drivers were not found, leading to built-in devices (keyboard, touchpad) not working. External USB mouse etc. would work though.
(b) after logging on, Windows displays a message that it's rebuilding the desktop, but never finishes.
A safer way is to /not/ modify the original disk's registry, but edit the registry hive in the system partition on the clone disk.
If the original system relied on a nonstandard drive letter ordering to boot, the cloned system will likely need an equivalent. That is, the UUID entries in HKLM\System\MountedDevices\ have to be updated to point to the cloned equivalents of the original partitions. The following steps should work but are certainly not the only way:
(1) On the original system, note the drive letters to which each of the partitions to be cloned should be assigned.
(2) Connect the cloned drive to a Windows system (I'll call it "host" below) as an USB disk, find the cloned partitions in Explorer, noting the removable drive letters they were assigned, then look at the host's HKLM\System\MountedDevices\ and for each removable drive letter, find the two matching entries
with the matching binary strings. (The contents of the binary strings are determined by drivers etc. so they vary from system to system.)
(3) Load the cloned system partition's \windows\system32\config\system hive under an arbitrary name; I'll call it \HKLM\_Clone_\ below. In \HKLM\_Clone_\System\MountedDevices, find the pairs of entries
and rename the entries of the second type replacing <OriginalUUID> with <CloneUUID>.
If you know the UUIDs of the original and clone partitions, steps (1) and (2) can be omitted.
Perhaps this could be automated, though I don't know whether there is an open source solution to editing Windows registry hives.
Recovery: if you already deleted all entries in \HKLM\System\MountedDevices and have unbootable original\clone disks, load those disks' system partitions' SYSTEM hives (as above in step 3) on another Windows machine. The partitions should have been assigned consecutive C:, D:, E: etc.. Rename the \DosDevices\<Letter>: entries with the appropriate drive letters.
BRs
Morio
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It worked for me this way on a Windows 2008 Server (SMB):
To fix the issue follow these steps.
1.Boot the windows server 2008 cd
2.Select your language
3.Select repair your computer
4.Run following commands
c:\> cd \windows\system32
> bcdedit /set {bootmgr} device boot
> bcdedit /set {default} device boot
> bcdedit /set {default} osdevice boot
5.Restart
On windows 10, with a similar error about winload.exe I ended up creating a windows recovery USB on another windows 10 PC (running Create Recovery Drive and electing not to copy system files). Then booting from that with the cloned drive in the PC and selecting Troubleshooting etc. finally running the commands given by Jens above.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello
Using the latest Clonezilla Live Stable (clonezilla-live-1.2.4-28-686.zip) on a USB key, I restored a Vista image into /dev/sda1 from /dev/sda2 (a.k.a. /dev/partimage). When done, I used fdisk to check that /dev/sda1 is NTFS and marked as active. FWIW, before using the regular version of Clonezilla, I tried the Ubuntu stable version, but it didn't work right (/dev/sda1 became /dev/sda5), so I used fdisk to delete and recreate /dev/sda1 and set its type as NTFS before trying again, with the regular version this time.
When rebooting, I get the following error:
"File: \Windows\system32\winload.exe
Status: 0xC0000225
Info: the selected entry could not be loaded because the application might be missing or corrupt."
Does someone know what to do? Should I change one of the switches before restoring the image?
Thank you for any hint.
FWIW, I then ran "ntfsfix /dev/sda1" which says it succeeded… but I still get the same error when booting up.
It appears that the solution is the same as for when cloning Windows7 and getting error 0xc00000e: Start Windows, edit the Registry, head for the HKLM\System\MountedDevices\ section, remove all entries except "Default", and then save this partition using CloneZilla.
Thanks for sharing this. We have put this in the Q&A page:
http://drbl.sourceforge.net/faq/fine-print.php?path=./2_System/94_windows_winload_err.faq#94_windows_winload_err.faq
Steven.
The short solution described above can be dangerous to the original system.
Just clearing HKLM\System\MountedDevices\ can render the original system unbootable if your system's partitions are arranged unusually, e.g. the partition given the drive letter c: is not the first partition or not the active one.
The symptoms I got, both on the cloned system and the original, was that after starting,
(a) many drivers were not found, leading to built-in devices (keyboard, touchpad) not working. External USB mouse etc. would work though.
(b) after logging on, Windows displays a message that it's rebuilding the desktop, but never finishes.
A safer way is to /not/ modify the original disk's registry, but edit the registry hive in the system partition on the clone disk.
If the original system relied on a nonstandard drive letter ordering to boot, the cloned system will likely need an equivalent. That is, the UUID entries in HKLM\System\MountedDevices\ have to be updated to point to the cloned equivalents of the original partitions. The following steps should work but are certainly not the only way:
(1) On the original system, note the drive letters to which each of the partitions to be cloned should be assigned.
(2) Connect the cloned drive to a Windows system (I'll call it "host" below) as an USB disk, find the cloned partitions in Explorer, noting the removable drive letters they were assigned, then look at the host's HKLM\System\MountedDevices\ and for each removable drive letter, find the two matching entries
\DosDevices\<RemovableDriveLetter>: = <OpaqueBinaryString>
\??\Volume{<CloneUUID>} = <OpaqueBinaryString>
with the matching binary strings. (The contents of the binary strings are determined by drivers etc. so they vary from system to system.)
(3) Load the cloned system partition's \windows\system32\config\system hive under an arbitrary name; I'll call it \HKLM\_Clone_\ below. In \HKLM\_Clone_\System\MountedDevices, find the pairs of entries
\DosDevices\<NeededDriveLetter>: = <opaque binary string>
\??\Volume{<OriginalUUID>} = <opaque binary string>
and rename the entries of the second type replacing <OriginalUUID> with <CloneUUID>.
If you know the UUIDs of the original and clone partitions, steps (1) and (2) can be omitted.
Perhaps this could be automated, though I don't know whether there is an open source solution to editing Windows registry hives.
Recovery: if you already deleted all entries in \HKLM\System\MountedDevices and have unbootable original\clone disks, load those disks' system partitions' SYSTEM hives (as above in step 3) on another Windows machine. The partitions should have been assigned consecutive C:, D:, E: etc.. Rename the \DosDevices\<Letter>: entries with the appropriate drive letters.
BRs
Morio
Morio,
Great! Thanks for sharing that.
Steven.
It worked for me this way on a Windows 2008 Server (SMB):
To fix the issue follow these steps.
1.Boot the windows server 2008 cd
2.Select your language
3.Select repair your computer
4.Run following commands
c:\> cd \windows\system32
> bcdedit /set {bootmgr} device boot
> bcdedit /set {default} device boot
> bcdedit /set {default} osdevice boot
5.Restart
Found at: http://blog.axiomdynamics.com/2010/01/windows-2008-disk-resize-fix-error.html
and worked like a charm :-)
HTH,
Jens
On windows 10, with a similar error about winload.exe I ended up creating a windows recovery USB on another windows 10 PC (running Create Recovery Drive and electing not to copy system files). Then booting from that with the cloned drive in the PC and selecting Troubleshooting etc. finally running the commands given by Jens above.
mmm, this is a very old thread...
Thanks for sharing that, anyway.
Steven