Windows 10 BootCamp - 0xC000001-

Question

richhill1974 Author

Level 1

9 points

Windows 10 BootCamp - 0xC000001-

Good Evening,

I've let Windows 10 perform an update on Bootcamp, it now displays a blue screen with the above message (Image below)

I've tried booting in to the help menu (F8 on start up) but none of the options help. I think that the MBR is corrupted but I cannot be sure.

My issue seems similar to this post -: Windows 10 Boot Camp Error code 0xc0000001 after unsuccessful partition

Some output from the computer -:

1. Running 'diskutil list && diskutil cs list' gives -:

And GPT -:

Can anyone help me restore the operation system please? 😢

Richard.

MacBook Air, Windows 10, Bootcamp

Posted on Feb 10, 2018 12:05 PM

Reply

Answer 1

richhill1974 Author

Level 1

9 points

Feb 11, 2018 1:40 AM in response to Loner T

Hello @Loner T and thank you for your reply.

Please see the image below - it is from the 'About this Mac' window -:

I'd like to add that I have had Bootcamp running with Windows 8 and Windows 10 on this machine for quite some time (4-5 years). So this update is the real root of the problem.... grrrr!

Look forward to your reply.

regards

Richard

Reply

Answer 2

richhill1974 Author

Level 1

9 points

Feb 11, 2018 10:45 AM in response to Loner T

Hi,

Thanks for your on-going help with this. I put the computer into Recovery mode on start up and kicked off a terminal in there. This is what it came up with -:

GPT -:

FDISK -:

How do I create an installer with Bootcamp? I started this Bootcamp and transitioned to win10.... I do not have the installer any more..

regards

Richard

Reply

Answer 3

Loner T

Level 9

59,526 points

Feb 22, 2018 3:08 AM in response to richhill1974

You can download the original driver from Apple using

In the downloaded package, check Bootcamp.xml (use Textedit or vi) which will provide the version supplied originally. The Driver is also included in the package, which can be re-installed.

Reply

Answer 4

Loner T

Level 9

59,526 points

Feb 11, 2018 6:40 AM in response to richhill1974

Disable SIP and post the output of

sudo gpt -vv -r show /dev/disk0

sudo fdisk /dev/disk0

BCD corruption can be addressed by using the installer created by BC Assistant. Do you have any Windows System Restore points that can be used for a rollback?

Reply

Answer 5

Loner T

Level 9

59,526 points

Feb 11, 2018 11:51 AM in response to richhill1974

Use the first two tasks/options in BC Assistant - Create and Download - you can recreate a USB installer. Please use a USB2 (480 Mbps) flash drive of 8+ GB. USB3 flash drives (5Gbps) do not work with the standard Windows installation media.

Reply

Answer 6

richhill1974 Author

Level 1

9 points

Feb 13, 2018 6:04 AM in response to Loner T

Hi,

I created the USB installer and loaded up from it. Went through a few of the options and none of them has resolved it.

I can go into a command prompt and I can see the drive and look through the drive in quite a bit of detail.

The only thing I can think now is to end up blasting another copy of Windows over the top of what is there and potentially loosing quite a bit...

Any other ideas before i do that?

Rich

Reply

Answer 7

richhill1974 Author

Level 1

9 points

Feb 21, 2018 11:53 AM in response to Loner T

Hi,

Thanks for that suggestion. How best can I start Win10 up so that I can see that. When I start up there is nothing to show whats causing the problem...

I'm pretty familiar with Windows (software developer 20+ years) but I cannot see any option in the Win 10 start up that will allow me to step through the start up and see where it is falling over....

Reply

Answer 8

Loner T

Level 9

59,526 points

Feb 21, 2018 11:58 AM in response to richhill1974

There should be a boot logging option and a debug option. Another option to consider is to use a trial version of VMware Fusion and importing the BC partition and removing the driver(s) using pnputil and DISM.

Reply

Answer 9

richhill1974 Author

Level 1

9 points

Mar 2, 2018 2:46 AM in response to richhill1974

I've pretty much given up on this now. I can't see how any of this is resolving the issue and I just think that the update has broken boot camp which is a massive shame as it was working brilliantly....