Windows 10 error code 0xc00000 bootcamp partition

karofromgöteborg wrote:

I did that and managed to create the empty space partition. I was going to boot back into windows to run the Partition Wizard and lucky me I discovered this limitless issue.

The moment you created the Free Space, C: was no longer valid. Here is an example of the BCD and Diskpart. This is a legacy BIOS installation so the BCD is on C:\Boot.

Gparted is not user freely. Just using Disk Utility to create the partition and making sure it's Fat32 is the first step. Then while in Windows I found it easier to use a 3rd party application that didn't require advance knowledge of Dos, UNIX or anything found to get you to point B. Grant they work for people that have a background in allocation. My person experience with Terminal command caused me to damage the allocating information on my Western Digital hard drive. I was only trying to clone a 2TB hard drive to my 4TB hard drive. Taking the cheap way out instead of purchasing something like Drive Cloner or any other brand with a price tag. Well my 4TB hard drive became 800 MB mess. So when the Western Digital application didn't fix the hard drive size issue. I was told Gparted was the best way to fix the issue from an IT professional. I nearly had to take a class to understand it. So I never grasped the setup at all to use Gparted. In the end I found what I needed from forums and I had to go back to Terminal. And the Terminal commands I've found fix my issue and restored my hard drive to it's 4TB size as it was. Then I used Disk Utility to clone the 2TB hard drive, which I should've done in the first place but I wasn't sure since Apple keep changing Disk Utility construct. I'm more comfortable using Terminal now then anything. And if I must change something uniquely to the drive(s) then what I can find to be done in Disk Utility. Terminal then becomes my 2nd goto application of choice.

Drive cloning is much simpler with CloneZilla - an open source project. Cloning is not the issue at hand, it is manipulating partitions on disk which have your data. Non-OS disks do not care about boot sectors, BCDs, etc..

Without knowing how the EFI vs BIOS installations work, and how to manage the pieces that are hidden from the user (for example EFI), caveat emptor.

You have allot of knowledge in the allocation subject. Please understand if it's a Windows machine your information is highly regarded. But since we're talking only about Bootcamp and how it works by default. There is no need to know the constructs related to the EFI or BIOS. As basic users of Apple devices that support Bootcamp, there would be no need to alter the EFI. And of course Mac's don't have BIOS, so there's no setting for it. And I do agree that most 3rd party applications can clone your hard drive at ease, but most if not all have a price. And if someone is on a budget regardless to them investing in a Mac in the first place. Cutting corners can come at a cost (no point intended). So know what you're getting into and know you risky. If that's the point of your discussion then I agree 100%.

Were you able to get your partition issue resolve? Loner T had allot of information. I”m familiar with the terminal commands but it’s a bit complex and it’s not for the faint of heart. You could seriously damaged the entire allocation to the hard drive. You must have all the detailed specifications for your hard drive and the partition you plan to fix before jumping it to make changes.. If anything you might find it easier to use Disk Recovery and format the entire hard drive if it’s beyond a simple adjustments. Messing with command line and using software to correct allications to the hard drive can be dangerous if you’re not familiar with advance partitioning .

We should have looked at the partitions, before you started the re-installation.

Did macOS install correctly, and does it boot properly?

Can you post the output of

diskutil list

from macOS Terminal?