Error code 0xc0000001 when installing captured Win 10 on ext. HDD

Hello everyone,

I tried to install a captured copy of a Windows 10 installation off of an external HDD. The HDD is 500GB, divided in two with one partition in FAT32 format and the other in NTFS. The latter (NTFS) partition holds the source folder with a whopping 157 GB install.wim file. On the FAT32 partition holds all the other folders and files for Windows installation including another copy of the source folder with only the boot.wim file (taken from the NTFS partition).

I attempted to install the Windows 10 capture on a clean Lenovo Flex 3-1570 laptop. (What I mean by clean is that the drive in the Flex laptop was wiped clean). I created the necessary partitions on the Flex's drive (MSR, EFI, Windows and WinRE). When attempting to install all went well until the installation process had to restart the Flex and it just stalled there endlessly (as if the laptop was off) with a blank, black screen. I shut off the laptop and tried again. This time I got a blue screen stating that the Windows startup did not work after many attempts and gave me an error code 0xc0000001. I did research on the error code and got that is has to do with booting up. So, the install never completed because it could not reboot.

Does anyone have an idea as to how I can get my external drive to boot during installation?

Thanks in advance.

Kind regards,

tecknot

P.S. I tried to Apply the captured Windows but I could get it to work.

Was this Flex 3-1570, or another identical PC, the source for this captured WIM? It's not clear whether the problem starts with the image itself or your installation steps.

One way to eliminate doubt is to copy a clean Windows install.wim in place of the captured WIM, and follow your same steps. If your steps are right, then the new install should finish installation

Assuming a clean image works, then we have to look if the captured WIM is possibly missing any required boot drivers especially if it wasn't from the same PC as you're installing to.

The right Partition structure is EFI | MSR | Windows | Recovery

Why didn't you run just a Bare Metal Recovery?

Boot into RE or PE and in cmd type

bcdedit

You should find

Windows Boot Loader
-------------------
identifier {default} or {current}

If it's default type this otherwise replace default by current in the 2 following commands

bcdedit /set {default} device partition=\Device\HarddiskVolume3
bcdedit /set {default} osdevice partition=\Device\HarddiskVolume3

garlin said:

Was this Flex 3-1570, or another identical PC, the source for this captured WIM? It's not clear whether the problem starts with the image itself or your installation steps.

One way to eliminate doubt is to copy a clean Windows install.wim in place of the captured WIM, and follow your same steps. If your steps are right, then the new install should finish installation

Assuming a clean image works, then we have to look if the captured WIM is possibly missing any required boot drivers especially if it wasn't from the same PC as you're installing to.

Hi garlin,

The captured wim was from another/different PC (a Lenovo G72). I wiped out all the drivers since I was going from one PC to a different PC. I figured the installation will pick up the needed drivers. (I guess not.) I'll try out your suggestion with the clean install.

Kind regards,

tecknot

- - - Updated - - -

Pentagon said:

The right Partition structure is EFI | MSR | Windows | Recovery

Why didn't you run just a Bare Metal Recovery?

Boot into RE or PE and in cmd type

bcdedit

You should find

Windows Boot Loader
-------------------
identifier {default} or {current}

If it's default type this otherwise replace default by current in the 2 following commands

bcdedit /set {default} device partition=\Device\HarddiskVolume3
bcdedit /set {default} osdevice partition=\Device\HarddiskVolume3

Hi Pentagon,

I did try to run a Recovery, but I got a error stating that there was no operating system.

I did not run bcdedit and the identifier was set to default. I also ran the two commands and both completed successfully. I am now trying a second go at installation.

Kind regards,

tecknot

- - - Updated - - -

Pentagon, okay, I made another attempt at installing but I still have the same result, Windows 10 installation will not reboot.

garlin, I will have to wait until I have more USB flash drives before I try to do a clean capture on the Flex 3-1570.

Kind regards,

tecknot

Did you use an USB-Disk to execute the bcdedit-commands or did you use the RE?

Pentagon said:

Did you use an USB-Disk to execute the bcdedit-commands or did you use the RE?

I used a WinPE USB flash drive.

To summarize, you're taking the normal Windows ISO and doing the split volume trick where you copy the ISO filesystem to a bootable FAT32 on the drive, and copy the oversized install WIM to a NTFS volume. Other than launching Setup.exe manually with a command-line pointing to the install WIM's path, everything is done thru Setup itself?

Or are you manually doing the diskpart, file copies to EFI & reserved, doing an /Apply-Image, and finally updating bcdedit?

Both are workable solutions, but we need to know are you responsible for those actions or is Setup doing it?

garlin said:

To summarize, you're taking the normal Windows ISO and doing the split volume trick where you copy the ISO filesystem to a bootable FAT32 on the drive, and copy the oversized install WIM to a NTFS volume. Other than launching Setup.exe manually with a command-line pointing to the install WIM's path, everything is done thru Setup itself?

Or are you manually doing the diskpart, file copies to EFI & reserved, doing an /Apply-Image, and finally updating bcdedit?

Both are workable solutions, but we need to know are you responsible for those actions or is Setup doing it?

Hi garlin,

Well, I am relying on the Setup itself. I wouldn't consider this a "normal" Windows ISO since it has a number of installed apps (that's why the wim is so big). I did do the split. I tried to Apply-Image but I didn't know about the bcdedit. I haven't tried using the Setup.exe and don't know about doing it manually with a command-line pointing to the install.wim path. I am just going by what I have gleaned from Apply Windows Image using DISM Instead of Clean Install and by the seat of my pants (that's mainly using the manual boot from the HDD and Windows setup).

Kind regards,

tecknot

If we presume you're following Kari's tutorial:

1. You managed to boot into a HDD, holding the ISO distribution.
2. You followed Setup to allow it to create your partitions.
3. You opened a CMD shell, and started DISM /Apply-Image.
4. You finished with the bcdboot command.

Are these the exact steps you followed? Right now it's not the time to be vague, but very clear in your executed steps.

A. Did the install disk have any pre-existing partitions when you first ran Setup? If the previous instance left partitions behind, you're best served to delete all of them, until everything falls into Unallocated Space. At this point, click on the New button and allow Setup to auto-partition for you.

B. After the DISM /Apply-Image, did you check if there's extracted data as you expected?

C. Do the source & target PC's share the same boot mode (UEFI or legacy MBR)? Which one doesn't matter, as long as they both match.

D. To confirm if the capture WIM/ESD is at fault, copy the sources\install.wim from a normal Windows ISO to your NTFS partition. This is an unedited (clean) test file. Use this file for DISM /Apply-Image, and check if you ended with a bootable PC.

Writing down the exact commands you entered makes it faster to debug.

garlin said:

If we presume you're following Kari's tutorial:

1. You managed to boot into a HDD, holding the ISO distribution.
2. You followed Setup to allow it to create your partitions.
3. You opened a CMD shell, and started DISM /Apply-Image.
4. You finished with the bcdboot command.

Are these the exact steps you followed? Right now it's not the time to be vague, but very clear in your executed steps.

A. Did the install disk have any pre-existing partitions when you first ran Setup? If the previous instance left partitions behind, you're best served to delete all of them, until everything falls into Unallocated Space. At this point, click on the New button and allow Setup to auto-partition for you.

B. After the DISM /Apply-Image, did you check if there's extracted data as you expected?

C. Do the source & target PC's share the same boot mode (UEFI or legacy MBR)? Which one doesn't matter, as long as they both match.

D. To confirm if the capture WIM/ESD is at fault, copy the sources\install.wim from a normal Windows ISO to your NTFS partition. This is an unedited (clean) test file. Use this file for DISM /Apply-Image, and check if you ended with a bootable PC.

Writing down the exact commands you entered makes it faster to debug.

I did follow Kari's instructions, but Apply-Image failed at 66%. Got an error to the effect that a function was incorrect or something to do with a function not working. So, I did complete steps 1-3, but didn't get to 4.

A. The install disk (C:) did have the necessary partitions when I ran Setup. Okay, I will wipe the entire disk.

B. Didn't get that far.

C. Both PCs are UEFI boot mode.

D. I will try a clean ISO to capture and apply that image soon (after I get more USB flash drives).

I did try the usual commands to fix Windows (including a Repair install, but it found no operating system):

sfc /scannow

DISM /Online /Cleanup-Image /CheckHealth
dism.exe /online /cleanup-image /scanhealth
dism.exe /online /cleanup-image /restorehealth
dism.exe /online /cleanup-image /startcomponentcleanup
Repair-WindowsImage -Online -CheckHealth
Repair-WindowsImage -Online -ScanHealth
Repair-WindowsImage -Online -RestoreHealth
Dism.exe /online /Cleanup-Image /StartComponentCleanup
Dism.exe /online /Cleanup-Image /StartComponentCleanup /ResetBase
chkdsk /scan
chkdsk /f /r /x
bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd

Not that I understand what all of the above does. I will write down all the steps I take to Apply the second (clean) image.

Kind regards,

tecknot