I get a mixed error message when booting up a virtual clone copy of my current still working desktop workstation that runs Win2K3 and Win7 in a dual boot setup.
Windows Boot Manager
--------------------
identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device partition=C:
description Windows Boot Manager
locale en-US
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default {10ed88c4-4181-11e0-8359-e101122eda78}
resumeobject {10ed88c9-4181-11e0-8359-e101122eda78}
displayorder {10ed88c4-4181-11e0-8359-e101122eda78}
toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout 30
displaybootmenu Yes
Real-mode Boot Sector
---------------------
identifier {10ed88c4-4181-11e0-8359-e101122eda78}
device partition=\Device\HarddiskVolume3
path \NST\ntldr
description Windows Server 2003
locale en-US
Disk Partition Information:
------------------------------------
Disk 0
D: Win2K3 (300GB) First Partition.
C: System Reserved
G: Removable USB flash drive.
The remaining partitions all show up in disk management but they do not show up anywhere else as Win2K3 cannot see the files located in these locations.
1162.92GB = Windows 7 Partition / 198.22GB = Storage Partition / 201.78GB = Second Storage Partition
Error when I try to start the virtual clone of the still working machine: nst\ntdlr 0xc0000225
I see there is a troubleshooting guide for NT based systems that are missing the ntdlr but that is for systems not using a BCD.
The second troubleshooting KB I see is for Windows 7 and Windows 8 systems that are getting a 0xc0000225 error code upon bootup.
My current system and virtual clone system no longer fall completely into one article or the other so I figure it's best to go the route of making the process easier for myself by restoring the boot process to the operating systems's default boot up process. I believe by setting it back to the default, if I attempt a new virtual clone it'll work as oppose to all the previous attempts that have failed so far with various error messages.
What is the best way for me to restore the boot loader back to the original default on the original physical boot system?
Windows Boot Manager
--------------------
identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device partition=C:
description Windows Boot Manager
locale en-US
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default {10ed88c4-4181-11e0-8359-e101122eda78}
resumeobject {10ed88c9-4181-11e0-8359-e101122eda78}
displayorder {10ed88c4-4181-11e0-8359-e101122eda78}
toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout 30
displaybootmenu Yes
Real-mode Boot Sector
---------------------
identifier {10ed88c4-4181-11e0-8359-e101122eda78}
device partition=\Device\HarddiskVolume3
path \NST\ntldr
description Windows Server 2003
locale en-US
Disk Partition Information:
------------------------------------
Disk 0
D: Win2K3 (300GB) First Partition.
C: System Reserved
G: Removable USB flash drive.
The remaining partitions all show up in disk management but they do not show up anywhere else as Win2K3 cannot see the files located in these locations.
1162.92GB = Windows 7 Partition / 198.22GB = Storage Partition / 201.78GB = Second Storage Partition
Error when I try to start the virtual clone of the still working machine: nst\ntdlr 0xc0000225
I see there is a troubleshooting guide for NT based systems that are missing the ntdlr but that is for systems not using a BCD.
The second troubleshooting KB I see is for Windows 7 and Windows 8 systems that are getting a 0xc0000225 error code upon bootup.
My current system and virtual clone system no longer fall completely into one article or the other so I figure it's best to go the route of making the process easier for myself by restoring the boot process to the operating systems's default boot up process. I believe by setting it back to the default, if I attempt a new virtual clone it'll work as oppose to all the previous attempts that have failed so far with various error messages.
What is the best way for me to restore the boot loader back to the original default on the original physical boot system?
